From: Gregory Nowak <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Some number problems in eSpeak
Date: Wed, 26 Apr 2006 12:06:21 -0700 [thread overview]
Message-ID: <20060426190620.GA17611@localhost.localdomain> (raw)
In-Reply-To: <20060426144125.GB2961@lnx3.holmesgrown.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
If I may add one more opinion to the mix, I personally like Steve's
preference myself, pronounce the numbers as whole words, the way the
doubletalk and the bns do. So, for example, 1234567 would be spoken as
one-million two-hundred-thirty-four-thousand
five-hundred-sixty-seven, without the dashes of course, which I only
put in for clarity.
Greg
On Wed, Apr 26, 2006 at 07:41:26AM -0700, Steve Holmes wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
>
> I actually like the numbers to be spoken as whole words even when the
> commas are missing. That's where the Accent synth drives me nuts when I
> display free space or do a 'du' on my box and those numbers are not
> punctuated. I find it harder to quickly parse a 6 or 7 digit number as
> a string of digits when I'm interested in knowing how much space is
> being used on my machine.
>
- --
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
iD8DBQFET8Ss7s9z/XlyUyARAsr1AJ9QjAyt2GVfwc6DKxlAhKGJiBy6SwCg20F7
p53TwoTlxZIC2/9D8FRAhXg=
=rgkC
-----END PGP SIGNATURE-----
prev parent reply other threads:[~ UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
Lorenzo Taylor
` Jonathan Duddington
` Lorenzo Taylor
` Willem van der Walt
` jim grimsby jr.
` Steve Holmes
` Gregory Nowak [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060426190620.GA17611@localhost.localdomain \
--to=greg@romuald.net.eu.org \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).