Re: [whatwg] Steps for finding one or two numbers in a string
On Sat, 9 Jun 2007, Kristof Zelechovski wrote: On Fri, 14 Apr 2006, Henri Sivonen wrote: I think i18n political correctness has no place in attributes. I think they should be ASCII only with the XML notion of whitespace. I agree and believe the spec already requires this. That statement was not precise enough. It applies to attribute names, not to attributes as such. I don't understand, could you elaborate? -- Ian Hickson U+1047E)\._.,--,'``.fL http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Re: [whatwg] Steps for finding one or two numbers in a string
Attribute names are limited to ASCII, attribute values are not. Chris -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ian Hickson Sent: Tuesday, June 12, 2007 9:54 PM To: Kristof Zelechovski Cc: 'Henri Sivonen'; 'whatwg List' Subject: Re: [whatwg] Steps for finding one or two numbers in a string On Sat, 9 Jun 2007, Kristof Zelechovski wrote: On Fri, 14 Apr 2006, Henri Sivonen wrote: I think i18n political correctness has no place in attributes. I think they should be ASCII only with the XML notion of whitespace. I agree and believe the spec already requires this. That statement was not precise enough. It applies to attribute names, not to attributes as such. I don't understand, could you elaborate? -- Ian Hickson U+1047E)\._.,--,'``.fL http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Re: [whatwg] Steps for finding one or two numbers in a string
On Tue, 12 Jun 2007, Kristof Zelechovski wrote: Attribute names are limited to ASCII, attribute values are not. Neither are limited to ASCII. I don't understand. The discussion was concerning the numeric search algorithms for progress bars, not attribute names. What exactly are you requesting should change? -- Ian Hickson U+1047E)\._.,--,'``.fL http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Re: [whatwg] Steps for finding one or two numbers in a string
Attribute names are not and cannot be localized because they are for the software and not for the human reader. That means they are limited to ASCII whether the standard is specific about that or not. Chris -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ian Hickson Sent: Tuesday, June 12, 2007 10:09 PM To: Kristof Zelechovski Cc: 'Henri Sivonen'; 'whatwg List' Subject: Re: [whatwg] Steps for finding one or two numbers in a string On Tue, 12 Jun 2007, Kristof Zelechovski wrote: Attribute names are limited to ASCII, attribute values are not. Neither are limited to ASCII. I don't understand. The discussion was concerning the numeric search algorithms for progress bars, not attribute names. What exactly are you requesting should change? -- Ian Hickson U+1047E)\._.,--,'``.fL http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Re: [whatwg] Steps for finding one or two numbers in a string
On Tue, 12 Jun 2007, Kristof Zelechovski wrote: Attribute names are not and cannot be localized because they are for the software and not for the human reader. That means they are limited to ASCII whether the standard is specific about that or not. Ok... So the spec doesn't have to change? -- Ian Hickson U+1047E)\._.,--,'``.fL http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Re: [whatwg] Steps for finding one or two numbers in a string
The specification enumerates all accepted element attributes. Neither of them transgresses ASCII boundaries. Since it can be directly inferred from the text, the explicit statement about that http://www.whatwg.org/specs/web-apps/current-work/#attributes0 technically is not needed, although it does no harm either. Chris -Original Message- From: Ian Hickson [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 12, 2007 10:20 PM To: Kristof Zelechovski Cc: 'whatwg List' Subject: RE: [whatwg] Steps for finding one or two numbers in a string On Tue, 12 Jun 2007, Kristof Zelechovski wrote: Attribute names are not and cannot be localized because they are for the software and not for the human reader. That means they are limited to ASCII whether the standard is specific about that or not. Ok... So the spec doesn't have to change? -- Ian Hickson U+1047E)\._.,--,'``.fL http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Re: [whatwg] Steps for finding one or two numbers in a string
On Tue, 12 Jun 2007, Kristof Zelechovski wrote: The specification enumerates all accepted element attributes. Neither of them transgresses ASCII boundaries. Since it can be directly inferred from the text, the explicit statement about that http://www.whatwg.org/specs/web-apps/current-work/#attributes0 technically is not needed, although it does no harm either. Ok. Since it does no harm and might help some readers, I'll leave it. -- Ian Hickson U+1047E)\._.,--,'``.fL http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
[whatwg] Steps for finding one or two numbers in a string
The part of the spec about numbers at http://whatwg.org/specs/web-apps/current-work/#numbers talks about skipping characters in the class Zs. Also, it talks about characters like U+066A ARABIC PERCENT SIGN, U+FE6A SMALL PERCENT SIGN and U+FF05 FULLWIDTH PERCENT SIGN. On the other hand, when the spec talks about digits, it talks about U +0030 DIGIT ZERO to U+0039 DIGIT NINE and not about character class Nd. Referring to character classes instead of particular characters is problematic, because what constitutes a conforming number changes when Unicode introduces ANCIENT BRUTOPIAN QUARTER CUBIT SPACE or SYLDAVIAN VULGAR DIGIT FIVE. I think i18n political correctness has no place in attributes. I think they should be ASCII only with the XML notion of whitespace. However, the human-readable fallback content of the progress and meter elements is not so clear-cut. Still, I doubt whether it is worthwhile to have an unstable but universal number format for content that is displayed to end users only as fallback. -- Henri Sivonen [EMAIL PROTECTED] http://hsivonen.iki.fi/
