W3C home > Mailing lists > Public > public-html@w3.org > August 2009

Re: <progress> element and attributes vs. content

From: Jonas Sicking <jonas@sicking.cc>
Date: Fri, 14 Aug 2009 15:56:27 -0700
Message-ID: <63df84f0908141556q28bebd45k7cab96e9f1ab2a0a@mail.gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: Lachlan Hunt <lachlan.hunt@lachy.id.au>, Adrian Bateman <adrianba@microsoft.com>, "public-html@w3.org" <public-html@w3.org>
On Fri, Aug 14, 2009 at 3:25 PM, Tab Atkins Jr.<jackalmage@gmail.com> wrote:
> On Fri, Aug 14, 2009 at 5:20 PM, Jonas Sicking<jonas@sicking.cc> wrote:
>> On Fri, Aug 14, 2009 at 3:00 PM, Tab Atkins Jr.<jackalmage@gmail.com> wrote:
>>> On Fri, Aug 14, 2009 at 4:49 PM, Jonas Sicking<jonas@sicking.cc> wrote:
>>>> On Fri, Aug 14, 2009 at 1:25 PM, Lachlan Hunt<lachlan.hunt@lachy.id.au> wrote:
>>>>> Adrian Bateman wrote:
>>>>>>
>>>>>> On Friday, August 14, 2009 10:46 AM, Tab Atkins Jr. wrote:
>>>>>>>
>>>>>>> On Fri, Aug 14, 2009 at 12:29 PM, Adrian Bateman<adrianba@microsoft.com>
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> I'm also concerned about how fragile the content parsing rules may turn
>>>>>>>> out to be in practice.
>>>>>>
>>>>>>> This is anecdotal, but to me it appears that they're rather robust, at
>>>>>>> least for English.
>>>>>>
>>>>>> I think this is my specific concern - how well does this work
>>>>>> internationally?
>>>>>
>>>>> The parsing algorithm only supports using the full stop as the decimal
>>>>> separator.  People from regions that normally use the comma as the decimal
>>>>> separator, and who wish to use that notation for fallback, need to provide
>>>>> the value in the attributes.
>>>>>
>>>>> So to represent the value 75,3%, they would have to use:
>>>>>
>>>>> <progress value="0.753">75,3%</progress>
>>>>
>>>> Then there is the thousands-separator issue, in Swedish it's common to write
>>>>
>>>> <progress>203'321 byte av totalt 1'048'576<progress>
>>>
>>> I'm wondering if it's possible to revise the algorithm to ignore
>>> grouping glyphs commonly used internationally.  Even using the , as a
>>> thousands separator, as is common in English, would break parsing.
>>
>> Actually, i noticed that "75 out of 100" is not a problem. The
>> algorithm says that the maximum number is the higher of the two, and
>> the current value is the lower.
>>
>> However that makes something like this fun:
>>
>> <progress>200 av 1,024</progress>
>>
>> Is that 20% (comma interpreted as thousand separator) or is that 0.5%
>> (comma interpreted as decimal separator)?
>
> Indeed.  ;_;  I hate the ./, swap between various continental languages.
>
> I would be inclined to take the English tradition (, as thousands
> separator, . as decimal separator) as the default, as it is more
> common on the web than the other.  Otherwise, there is *literally* no
> way to resolve the ambiguity.

By that logic I would say that we should use Mandorin or Hindi/Urdu
tradition as those are more commonly[1] spoken languages than English,
thus I think it's a good guess that eventually they will be more
common on the web.

[1] http://en.wikipedia.org/wiki/List_of_languages_by_number_of_native_speakers

/ Jonas
Received on Friday, 14 August 2009 22:57:31 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:06 UTC