Stanley Haupt
lehighton, PA.
Stanley
At 01:47 PM 10/31/2012, Doug Geoffray wrote:
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.
