Hi, I'm replying to Olga's message on the list, and cc'ing it to HJ, since they need to be aware of this. I'd been meaning to write them for a while about this myself anyway. Actually, this problem has existed since the new Eloquence was released. It only happens if you have the number mode set to "say digits". It seems to be an Eloquence problem, since Eloquence is too smart for its own good and tries to read dates in context. If Eloquence gets a phrase like "on March 16" or "on May 27" it sees the "on (month-name) number" and reads the number as an ordinal number for dates. I.e. it reads the above strings as "on March first six" and "on May second seven" when reading by line or in say-all (reading by words works correctly though.) Since JFW only passes one digit at a time to Eloquence (when "say digits" is set), Eloquence reads the first number (e.g. a 1 or 2) as "first" or "second" respectively, and then tacks on the next digit. This is really irritating, and I hope HJ can find a work-around. I, personally, prefer to have numbers spoken as single digits, but the date problem with Eloquence does cause confusion. --Robert englebretson - Visit the jfw ml web page: http://jfw.cjb.net
