- From: Garth Wallace <gwalla@sfgate.com>
- Date: Thu, 12 Aug 1999 11:34:47 -0700
- To: "'www-style@w3c.org'" <www-style@w3.org>
I think it would be a good idea to at least address this issue in the spec. The problem is that some punctuation is very dependent on context. For example, the dollar sign would normally force a period to be interpreted as currency: $14.32 as "fourteen dollars and thirty two cents". But there are cases where that doesn't have the correct results: "$14.32 million" should be read as "fourteen point thirty-two million dollars" rather than "fourteen dollars and thirty-two cents million". I can't really think of any good solution to this. A value for speak-pronunciation that forces a decimal rather than currency context might work, but it seems like a kludge, and generated content would be necessary to add the word "dollars". > -----Original Message----- > From: www-style-request@w3.org [SMTP:www-style-request@w3.org] > Sent: Wednesday, August 11, 1999 7:52 PM > To: Garth Wallace; 'www-style@w3c.org' > Subject: Re: Speak-Punctuation > > ... > >Also, with speak-punctuation set to code, would > >"14.32" be read as "fourteen point thirty-two" or > >"fourteen period thirty-two"? > > Surely that is a browser implementation issue? I can imagine browsers > having sets of "languages" such as: > + 'US English', 'UK English', ... > + 'mathematical', 'formal', 'informal', ... > > Jonathan O'Donnell > Director of Information Technology > Art, Design and Communication > RMIT City campus 6.3.12 > > Telephone: +61 3 992 52903 > mailto:doit@art.rmit.edu.au > http://purl.nla.gov.au/net/jonathan >
Received on Thursday, 12 August 1999 14:40:54 UTC