David,
It still speaks the dates in the 2+2 format in your second examples.
Best regards from Ohio, U.S.A.,
Vic
E-mail: vic.beckl...@gmail.com
-----Original Message-----
From: David [mailto:eleph...@tele2.no]
Sent: Wednesday, May 23, 2012 9:49 PM
To: gw-scripting@gwmicro.com
Subject: Re: To all Natively English speaking users - I need some
feedback:
Not to be nagging, but might I ask those of you who do happen to have
Eloquence speak out the 2+2 year format, the following. OK, so I get it,
that Eloquence will handle the dates:
4/12/1987
and
5/24/2012
pretty well. You will hear the years spoken as 19 87, and 20 12. Is that
correct?
Now, what if you recieve a text - from any of the Scandinavian countries -
where the dates are written in the Scandinavian format. The two dates
above,
would then be written like this:
12.04.1987
and
24.05.2012
. As you can see, a couple of differences from the American format. First
of
all, we - I guess like most Europeans - do put the day ahead of the month.
Secondly, each section, the day, month and year, are all separated by a
period instead of a slash. I now am quite curios as to whether your
English
Eloquence still speak the years in 2+2 format, or if this "strange" format
will cause it to read out four digit years as one big number.
Why is this so important? Well, even you could happen to receive an
English
text, written in Scandinavia, and where the dates might happen to be in
the
Scandinavian way. Or, in any other non-American way. Smile. And even if a
local synthesizer might handle the sscandinavian format wel enough, I do
promise you that they don't handle the American format anything good.
Smile.
The American/Scandinavian example is but to illustrate the problem, there
would be many other formats to handle. Since better date handling has been
a
user request found on the GW lists, and the fact that the app can handle a
good deal of this matter simply by user entries, I wanted to include
entries
that handles a number of date formats. The user then would be given quite
an
idea, for further tayloring. And yes, that is right, the app itself does
do
nothing to the date - like hook on to any locale setting of the computer.
All of this, is being handled by the user entries, which can be editted
directly in Notepad.
And so, in my endeavors to make such a set of entries for date handling, I
realized that I could not get my Eloquence to speak out the 2+2 year
numbers, in WE natively. Therefore, I wanted to take care of that in the
same token, hence my general question for the community. Without asking a
storm of messages, I still would be happy to know, how well Eloquence
handles the years in the above given examples.
Thanks again, everyone.
----- Original Message -----
From: "Chip Orange" <lists3...@comcast.net>
To: <gw-scripting@gwmicro.com>
Sent: Thursday, May 24, 2012 1:06 AM
Subject: RE: To all Natively English speaking users - I need some
feedback:
I think it's a well made and thoughtful point you've got there Mike, and
thanks go to David for trying to do this difficult bit of programming for
us!
Chip
-----Original Message-----
From: Mike Pietruk [mailto:piet...@panix.com]
Sent: Wednesday, May 23, 2012 11:40 AM
To: gw-scripting@gwmicro.com
Subject: Re: To all Natively English speaking users - I need
some feedback:
David
When WE was initially released in foreign versions, what
GWMicro did made sense. However, the introduction of
scripting capabilities in 7.0 changes the landscape in this regard.
Because of this, I hope that Doug and Dan revisit this
approach and come up with some sort of toggle that will
benefit guys like yourself who aren't native English speakers
but seek to do work for those of us who are.
\
Every experience God gives us, every person He puts in our
lives, is the perfect preparation for the future that only he can see.
Corrie ten Boom
