On 7/14/2009 3:07 PM, Chip Orange wrote:
Hi David,
Well, the observation re eloquence, so far, is just my own. the true
source of the problem, if there is indeed one, may be with the
eloquence-specific script I also run when I'm running eloquence, and so
it may not be with the speech engine itself. ironically, this script is
supposed to help manage issues which otherwise are known to cause
eloquence to crash, and thus take down window eyes along with it.
Chip and others,
For script authors' sake, we need more usable information. Saying that
someone has X number of running scripts and speculating on what is
causing the problem frankly isn't enough for any of us to work with.
Regarding the Eloquence Fix script, it only examines what the
synthesizer is about to speak. If any harmful strings inside the
script's dictionary are discovered, they are replaced with phonemic
equivalents which won't cause Eloquence to blow up. Is Eloquence Fix to
blame? Maybe, but maybe not. Is Eloquence Fix in combination with other
similar-acting scripts to blame? Again, maybe. Those of you with
stability issues are strongly encouraged to provide as much specific
information as possible. Otherwise, we developers simply won't have
enough data to use to help solve the problem. The "Show All Scripts"
package at
https://www.gwmicro.com/Script_Central/Scripts/Script_Details/?scriptid=1080
is a good start to helping us find out what's happening.
Regards,
Steve
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.
All GW-Info messages are archived at http://www.gwmicro.com/gwinfo, and can be
searched through and sorted using the search
form at the bottom of the page.
If you wish to unsubscribe from this list, send a message to
[email protected] and include leave gw-info in the body
of the message.
