W3C home > Mailing lists > Public > whatwg@whatwg.org > December 2006

[whatwg] finding a number...

From: Henri Sivonen <hsivonen@iki.fi>
Date: Tue, 12 Dec 2006 22:21:32 +0200
Message-ID: <DCB2255B-01FB-411A-B7EF-DA215C0D1E66@iki.fi>
On Dec 12, 2006, at 15:36, Anne van Kesteren wrote:

> On Tue, 12 Dec 2006 14:31:23 +0100, Henri Sivonen <hsivonen at iki.fi>  
> wrote:
>>> why does finding a number in text [1] insist on "." as a decimal  
>>> seperator, when , is also very commonly used?
>> I think the format should be kept simple (and potentially  
>> politically incorrect), because the human-readability is only a  
>> legacy fallback issue. That is, users aren't exposed to the number  
>> formatting in UAs that actually implement progress bars and gauges.
> You might also want to use this algorithm for the proposed  
> class="price". In that case you really want to take into account  
> "," as well.

What would 2,500 mean? Would it mean two and a half or two-thousand- 

How can this be dealt with without making the parsing dependent on  
lang and requiring the UAs to implement all-encompassing CLDR-aware  
number parsing?

Henri Sivonen
hsivonen at iki.fi
Received on Tuesday, 12 December 2006 12:21:32 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:51 UTC