"Mark Conrad" wrote:

Now stop beating around the bush and tell me how to submit
a formal bug report to Microsoft, PLEASE.

Register for the MSSpeech-Forum at:
http://www.msspeech-forum.com

Several macro programming experts hang out there. Among these is Brad Trott,
the author of, the $9.99 "WSRMacros: The User’s Guide." Also some of the
people from the Microsoft Speech work group monitor the forum. I'm guessing a
simple macro will solve your problem so post what is happening and see if you
receive a solution?

Marty Markoe, eMicrophones, Inc.
See us at: http://www.mymmsspeech.com
New to Windowsâ„¢ Speech Recognition?
See, Getting Started with Windows® Speech Recognition at:
http://www.mymsspeech.com/download/WSRGetStarted.pdf

"Marty Markoe - eMicrophones, Inc."
. com wrote in message
...

SPAM

"B. Smith" wrote:

SPAM

Hmmm???? Considering the WSRToolkit was designed with suggestions and help
from people in the Microsoft Speech work group I

would think this is good information.

Prior to the release of Vista and WSR, I was invited with a select group of
other speech recognition professionals to Redmond. We

previewed WSR and mad suggestions. I was also asked to develop products to
support WSR.

If this be SPAM to you, please feel free to ignore it. If you look at the
products you may actually see their value (at $15.99 or less). Also, we

make the WSRToolkit FREE to people with disabilities.

Kindly rethink your initial reaction to our postings.

Sincerely,
Martin Markoe, eMicrophones, Inc.

In article , Marty
Markoe - eMicrophones, Inc.
. com wrote:

Mark Conrad posted nasty stuff to a poor unsuspecting MVP -
Now stop beating around the bush and tell me how to submit
a formal bug report to Microsoft, PLEASE.

I'm guessing a simple macro will solve your problem so
post what is happening and see if you
receive a solution?

Hi Marty, nice hearing from you.

Not as easy as that, I do not communicate well with MVPs or
anyone else spouting the $MS party line.g

I was just using that NewLine issue to vent my frustration,
mainly with Microsoft, but also with Nuance.

If I got into http://www.msspeech-forum.com it would just
result in a big fight, because someone there would invariably
defend Microsofts approach and that would set me off.

You know what I mean, MS has the decided tendency to make the
rest of the world do stuff the MS way, rather than leave the
choices to the user.

Take paragraphs for example, there are at least 3 ways to
handle them:

My dog has fleas,
and so do I.
My wife beats me, (indentation, very popular)
but only on weekends.


My dog has fleas,
and so do I.
(separate by a line)
My wife beats me,
but only on weekends.


1) My dog has fleas. (number the paragraphs,
and so do I. as in scientific journals)
2) My wife beats me,
but only on weekends.


Now Microsoft, in its infinite wisdom, has decreed that the
"separate by line" method will be imposed on the world by
almighty Microsoft.

It is this general tendency to take control out of the hands
of the user that I resent. Apple does it a little, but not
nearly as much as Microsoft does.


Then the darn MVP had the gall to tell me that everything
would be taken care of because $MS had further decreed
that all document apps will have automatic word-wrap!

Not so, as anyone can tell you when they run into those
weird browsers that have several long lines, and the poor
viewer ts required to scroll horizontally to read the lines.

So what to do about Microsoft's overly aggressive attitude of
"do it my way, or no way at all".

Sure, I could make macros, lots of different macros for 43
different medical specialties who do things differently from
each other.

All I have to do is learn 3 different variants of Visual Basic,
the WinWrap Basic V6 still favored by Dragon,
the Microsoft VB Script 5,
and Microsoft VBA 6. grr, grrr

A year of hard application should put me in the business of
selling macros.g

Heck, I might as well learn C, because variants of Visual
Basic have little use on the Mac platform.

Of course, everyone pats $MS on the back for their foresight
in taking choice out of the hands of the users, because that
spawns a whole new industry of people who can sell macros
to users, macros that would not be needed if the user had
more choices.

End of Rant ;-)

Mark-

--
As you can see, I am an opinionated hard-headed old geezer,
who is probably dead wrong in a lot of my assumptions.

Whoops, I made a mistake in my first example of how
paragraphs are commonly handled, it should be:

My dog has fleas, (indentated line)
and so do I.
My wife beats me, (indentation again)
but only on weekends.


I forgot to indent the first paragraph in my following tirade,
down near the end.

Mark-


In article , Mark
Conrad wrote:

Not as easy as that, I do not communicate well with MVPs or
anyone else spouting the $MS party line.g

I was just using that NewLine issue to vent my frustration,
mainly with Microsoft, but also with Nuance.

If I got into http://www.msspeech-forum.com it would just
result in a big fight, because someone there would invariably
defend Microsofts approach and that would set me off.

You know what I mean, MS has the decided tendency to make the
rest of the world do stuff the MS way, rather than leave the
choices to the user.

Take paragraphs for example, there are at least 3 ways to
handle them:

My dog has fleas, === I should have indented this line
and so do I.
My wife beats me, (indentation, very popular)
but only on weekends.

"Mark Conrad" wrote:

I was just using that NewLine issue to vent my frustration,
mainly with Microsoft, but also with Nuance.

There is nothing wrong to ask for perfection. The big difference I've found
between Nuance and Microsoft is you actually hear from people at Microsoft.

Marty

PS. I'm probably an older codger than you.

In article , Marty
Markoe - eMicrophones, Inc.
. com wrote:

I was just using that NewLine issue to vent my frustration,
mainly with Microsoft, but also with Nuance.

There is nothing wrong to ask for perfection. The big difference I've found
between Nuance and Microsoft is you actually hear from people at Microsoft.

Yeah, Nuance is more "distant", not at all like ScanSoft or L&H who
were the prior owners of Dragon.

On the Mac side, "MacSpeech" is even more "distant", and they
do not have any excuse because they are a small outfit with
only about ten programmers. (Mac only)

Mark-


Expanded signature remarks, only to be read
if you are a speech recognition addict.
--
It is _very_ _hard_ to drum up interest in speech recognition
in personal computing, because of several factors, the main factor
being that 99% of what a user does with SR can be done by using
the keyboard and mouse.

Another limiting factor is the fact that using speech often causes
unwanted interference to others, like cellphones do.



Continuing with factors that limit use of SR...
-----------------------------

The "text correction" bug-a-boo, I can stamp out a 200 word
email using speech in 2 minutes, but then waste ten minutes
correcting residual mistakes.

This varies wildly, with simple text I often get 100% accuracy,
no correction needed.

With technical text, I could easily waste 20 minutes correcting,
reducing my "average" speed to ten words per minute!

Now in theory, according to speech programmers, none of this
should happen, because "training" the speech program to
recognize all your possible personal phonemes should prepare
the speech program to recognize any new word you might say,
_provided_ that word is in the computer's speech vocabulary.

It just plain does not work that simplistic way, the allophones,
phonemes, vowels, consonents, and assorted hissing, trilling,
clicking, "rolling" of Rs, and other "Gerald Mc Boing Boing"
type noises made by the lips, mouth, larynx, throat can not
be represented by a simplistic bunch of phonemes.

The computer's speech vocabulary is a limited size, I think
the Dragon vocabulary is 160,000 words.

If the word is not in the computer's vocabulary, no way in heck
can the program recognize that word.

If you add a new word, some other word gets "squeezed out"
instead of the vocabulary growing to 160,001 words - at
least that is my thought, I might be incorrect.

All that is further exacerbated by microphone distortion,
sound card distortion, electrical "noise", reflection of
speech from nearby walls, etc., etc., etc.

Adjacent word association has limited use. Sure, I can
train Dragon to recognize this quoted list every time:

"to 2 too two tutu"

....by speaking: OpenQuote 2 2 2 2 2 2 CloseQuote

But if I re-arrange the list, all bets are off.

In general, adjacent word association improves speech
recognition, but it is not the magic bullet that some
users think it is.


So is there anything GOOD to say about SR
as far as it relates to personal computing?
***************************

I think there is. With simplistic non-technical words,
my recognition accuracy is very close to 100%,
usually about 99%

That 1% error is a killer, just to CHECK the text, I have
to read it, which takes about a minute for 100 words.

Checking the text alone means that my average speed gets
reduced from 100wpm to 50wpm, EVEN IF THERE ARE NO
TEXT MISTAKES.

ANYTHING that speeds up correction of text can radically
expand the use of SR for average users.


IMO, the real value of speech recognition is that transient
speech can be _captured_ , such that people do not have to
rely on memory of what was said.

A further advantage is that text can be readily searched,
unlike an audio recording.

"Spirit" wrote in message
...
Give the dog a new name! oh and a flea bath.

LOL! At Spirit,

Forgive him Spirit, all it has in his life is his dog and his DNS medical to
talk to. Just let him post everywhere in Microsoft as this it is only
hobby.

Perhaps if he gave his dog a wash and then himself and then take himself and
his dog for a walk in the OUTSIDE WORLD, perhaps the fleas and the parasites
would not persist.


"Mark Conrad" wrote in message
...

Great, do you happen to know where I can
post the bug report?

What is the bug with WSR

When I speak the command "NewLine" to drop down
a line in the middle of a sentence, WSR wrongly
capitalizes the first word on the new line.

In other words, if I speak this sentence:

"My dog NewLine has fleas Period"

...then the text appears like this:

My dog
Has fleas.


Notice that "Has" is wrongly capitalized.

BTW, my $1,600 full version of Dragon medical 10.0
has the same bug.

I submitted a formal bug report to Nuance, they
thanked me, hopefully they will fix it by the next update.

About the only modern speech app that does it right is
that new one for Macs, "MacSpeech Dictate 1.2"

My dog
has fleas.

...but that app has many other problems.

Mark-


--
In article , Peter Foldes
wrote:

Yes. What is the bug with WSR