In article <#XS9rUEQJHA.3820@TK2MSFTNGP03.phx.gbl>, zachd [MSFT]
<zachd@nomailplz.online.microsoft.com> wrote:

> So what's a specific and valid scenario where this is causing you pain?

I thought you would never ask. ;-)

As you know, the value of any speech recognition app' is directly
proportional to how fast it will convert speech into acceptable
text. For example, if you were trying to hire a secretary
for your upscale business, and that secretary submitted
a resume to you that looked like this, after mentioning
proudly to you that she created the resume by using
Windows Speech Recognition, which is included
with Vista:

My name
Is Suzy, I
Have all
Sorts of
Experience
Using Word
Which is a
Very good
Processor
Of documents.


....you would likely be a little hesitant about hiring suzy,
because she apparently does not know how to properly
capitalize words in a column.

She could explain to you until she was blue in the face
that WSR had a bug in it that insisted that the beginning
word in each line would be capitalized, whether Suzy
wanted it to be capitalized or not.


Now the app' "Microsoft Word" can no doubt be set to
avoid this sort of bug when writing columns, but that
does not help Suzy any when the bug re-surfaces in
her Speech Recognition program.

The bug is in the "NewLine" commands behavior.

A competitive speech program for the Mac has the
same "NewLine" command, but it is not buggy, it acts
as it should, realizing that most beginning words in
a column are NOT capitalized.

With "MacSpeech Dictate 1.2" Suzy dictates
like this:

My name NewLine is Suzy Comma I NewLine have all NewLine
sorts of NewLine experience NewLine using Cap-Word Newline
which is a NewLine very good Newline processor NewLine of
documents Period NewParagraph


With buggy WSR, Suzy would be required to dictate like below,
to achieve the same identical results:

My name NewLine is LowerCaseThat Suzy Comma I NewLine
have LowerCaseThat all NewLine sorts LowerCaseThat of
NewLine experience LowerCaseThat NewLine using Cap-Word
Newline which LowerCaseThat is a NewLine very LowerCaseThat
good Newline processor NewLine of LowerCaseThat documents
Period NewParagraph


There were 7 unnecessary insertions of the command
"LowerCaseThat",needed just to get the buggy WSR to act
like MacSpeech, which is NOT buggy.


Wadda ya want, the world to be populated by Mac lovers, just to
"justify" the weird buggy way that WSR presently acts?

Not for me. I prefer to fix the damn bug.

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

Mark-