-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 Well given the fact that Eloquence has had this bug for several years, It's high time that a vendor did something about it. Hum, hey maybe that creep did us a favor afterall. He brought this problem up to such a high profile that it got formally addressed. You will notice something else. Scansoft hasn't done a thing about it; it took Freedom Scientific to modify Jaws or one of its dictionaries to "plug up" the problem. I think GW Micro got around this one by sticking to an earlier version of Eloquence and actually stopped using it as their default synth. From what I've heard in the past, Scansoft has not been willing to fix their own bugs and would charge other providers to report them. Anyway, there is a public fix that all JFW users can apply now. On Thu, Mar 30, 2006 at 09:21:32AM -0800, John Gassman wrote: > Hi, > I am not a JAWS Beta tester but I know several who are. > Freedom Scientific did release a message today with a fix for this > Eloquence problem. > The idiot has been claiming that it is a hoax. > The page is legitimate with an original fix in May of 2005 and an > update to that fix yesterday March 2006. > My hunch would be that this fix will be built into a Beta 7.1 update > coming soon. > > John > > > John Gassman > mailto:jjgassman@xxxxxxxxxxxxx > Recognition Of The Problem is 51% Of The Solution > > > > - -- HolmesGrown Solutions The best solutions for the best price! http://ld.net/?holmesgrown -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.7 (GNU/Linux) iD8DBQFELBfyWSjv55S0LfERA1YdAJ94eyrvlbWckgHKf7iKz/nzx4uy2wCgq8E4 cAF0+HYdhSYTuMMjh79O6+s= =ut7f -----END PGP SIGNATURE-----