Have annoying bug which only occurs with WSR.

Is there any section of Microsoft that accepts bug reports?

Mark-

Yes. What is the bug with WSR

--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"Mark Conrad" wrote in message ...

Have annoying bug which only occurs with WSR.

Is there any section of Microsoft that accepts bug reports?

Mark-

That appears to be a design question as opposed to Bug report. There's a
stylistic difference between the two operations, but I'm not aware that one
is fundamentally superior to the other. What's a real world instance where
this is of significance?

If I recall correctly, the 'newline equals new sentence' logic is mirrored
throughout all autocorrecting Microsoft software that I can think of, so I'd
think this is by design as it stands and you would need to force lower-case
if that's what you explicitly wanted. =\

--
Speaking for myself only.
See http://zachd.com/pss/pss.html for some helpful WMP info.
This posting is provided "AS IS" with no warranties, and confers no rights.
--
"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

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

Give the dog a new name! oh and a flea bath.

"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

If I recall correctly, the 'newline equals new sentence' logic is mirrored
throughout all autocorrecting Microsoft software that I can think of......

But surely this is nothing to do with autocorrection. We are in text entry
mode, not autocorrection mode.

It's exactly like typing "My dog shift+enter has fleas" in Word.

And when you do that, you get a lower case 'h'.

So, designed in or not, I think it's faulty functionality and would support
the OP's thought that it should go in as a bug report.

So how is that done?

SteveT

In article , zachd
[MSFT] wrote:

If I recall correctly, the 'newline equals new sentence' logic
is mirrored throughout all autocorrecting
Microsoft software that I can think of...

I do not think so in this case, because there is a
seperate command named "NewParagraph" specifically
designed for the purpose you mentioned.

My awkward workaround to get rid of the unwanted
capitilization is:

"My dog NewLine still LowerCaseThat has fleas Period"

My dog
still has fleas.


....but needing to apply "LowerCaseThat" to every line
in my document really slows down the speech app'.

Mark-

I was going by regular enter as opposed to shift-enter. =\
Auto-correction as in "guess what you're trying to do" - as in any
non-"smart" editor you would have had to explicitly upper case any leading
letters.

--
Speaking for myself only.
See http://zachd.com/pss/pss.html for some helpful WMP info.
This posting is provided "AS IS" with no warranties, and confers no rights.
--
"Steve Thackery" wrote in message
...
If I recall correctly, the 'newline equals new sentence' logic is
mirrored throughout all autocorrecting Microsoft software that I can
think of......

But surely this is nothing to do with autocorrection. We are in text
entry mode, not autocorrection mode.

It's exactly like typing "My dog shift+enter has fleas" in Word.

And when you do that, you get a lower case 'h'.

So, designed in or not, I think it's faulty functionality and would
support the OP's thought that it should go in as a bug report.

So how is that done?

SteveT

So what's a specific and valid scenario where this is causing you pain? The
more real world any given scenario is, the easier it is to push for a given
notion. =) As a poetry fan, the current behavior makes sense to me. ;-)

--
Speaking for myself only.
See http://zachd.com/pss/pss.html for some helpful WMP info.
This posting is provided "AS IS" with no warranties, and confers no rights.
--
"Mark Conrad" wrote in message
...
In article , zachd
[MSFT] wrote:

If I recall correctly, the 'newline equals new sentence' logic
is mirrored throughout all autocorrecting
Microsoft software that I can think of...

I do not think so in this case, because there is a
seperate command named "NewParagraph" specifically
designed for the purpose you mentioned.

My awkward workaround to get rid of the unwanted
capitilization is:

"My dog NewLine still LowerCaseThat has fleas Period"

My dog
still has fleas.


...but needing to apply "LowerCaseThat" to every line
in my document really slows down the speech app'.

Mark-

In article , zachd [MSFT]
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-