I wonder why it doesn't happen with nvda or jaws, I just read those words in an
email and it read them just fine using nvda
----- Original Message -----
From: Tom Fairhurst
To: [email protected]
Sent: Thursday, November 01, 2012 11:07 AM
Subject: Re: Lacking pronunciation
Furthermore, some of us only have access to Anna withWindows 7. Will we
ever get the other Sapi voices back, or will we need to upgrade toWindows 8 to
see if this bug is fixed?
From: Bill Scherer
Sent: Thursday, November 01, 2012 10:49 AM
To: Window-Eyes discussion list
Subject: Re: Lacking pronunciation
I agree,
I haven't found one that is as natural sounding and yet responsive.
Bill
----- Original Message -----
From: Josh Rivera
To: [email protected]
Cc: [email protected] ; [email protected] ; [email protected]
Sent: Wednesday, October 31, 2012 12:59 PM
Subject: Re: Lacking pronunciation
What a shame they aren't keeping up with updating Eloquence. In my
estimation, it is the most clear, and human sounding synth out there. If it is
left to die, it will be a very sad day indeed!
On Wed, 31 Oct 2012 13:47:53 -0400 Doug Geoffray <[email protected]>
writes:
Eloquence has certain combinations of letters that will cause it to blow
up. This is obviously bad because it takes Window-Eyes with it. As we have
Window-Eyes upgrades we incorporate those problem combinations into Window-Eyes
itself so it doesn't surprise me that shutting down the Eloquence fix app made
no difference and in fact, the app was probably already stopped because it
realized the version of Window-Eyes running has the fix built into it.
Note Nuance is not willing to put any resources into fixing Eloquence so
we are left trying to block anything that could potentially make your system
unstable.
Doug
On 10/31/2012 1:13 PM, David wrote:
Thanks, then I know, it is none of my problem. Smile.
GW, could you please investigate? Would this happen to have anything to
do with your incorporation of the Eloquence Fix in the 7.5 series? I just
wonder, since it did not happen in older versions of WE, but I can't remember
exactly when I noticed it first time. So, I wonder if it could be something the
staff accidentialy changed in one of the newer versions of WE.
----- Original Message -----
From: Tom Fairhurst
To: [email protected]
Sent: Wednesday, October 31, 2012 5:43 PM
Subject: Re: Lacking pronunciation
I tried your examples in MS Word 2010 and confirm this behavior.
From: David
Sent: Wednesday, October 31, 2012 11:07 AM
To: WE English mailing list
Subject: Lacking pronunciation
I have noticed a lacking pronunciation, with my Eloquence
synthesizer. This persist even with all apps turned off. Wonder if this is
something others can confirm.
The problem arises when a word ends in an H, followed by the
apostrophe and an S. Like:
Isaiah's,
Jeremiah's
and so forth.
In those cases, the ending S is not pronounced. Only the main part of
the word.
How does the Eloquence with other users do with these cases? Just
wondered if this is only on my system, although it happens on both machines
here, or if this would be a bug in WE.
Running XP, WE7.5.4.1.
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.2221 / Virus Database: 2441/5365 - Release Date: 10/31/12
____________________________________________________________
Woman is 53 But Looks 25
Mom reveals 1 simple wrinkle trick that has angered doctors...
ConsumerLifestyleMag.com
If you reply to this message it will be delivered to the original sender only.
If your reply would benefit others on the list and your message is related to
GW Micro, then please consider sending your message to [email protected] so
the entire list will receive it.
GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can manage
your list subscription at http://www.gwmicro.com/listserv.
