Hi guys,
why does finding a number in text [1] insist on . as a decimal
seperator, when , is also very commonly used?
[1] http://www.whatwg.org/specs/web-apps/current-work/#steps
cheers
Chaals
--
Charles McCathieNevile, Opera Software: Standards Group
hablo español - je parle
On Dec 12, 2006, at 14:11, Charles McCathieNevile 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
On Tue, 12 Dec 2006 14:31:23 +0100, Henri Sivonen [EMAIL PROTECTED] 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
The theme for XTech 2007 (15-18 May 2007 in Paris) is The
Ubiquitous Web, and proposals are due by December 15 (this
Friday).
http://xtech.expectnation.com/event/1/public/cfp/1
A list of the tracks and suggested topics is here:
http://xtech.expectnation.com/event/1/public/content/tracks
Hi,
Section 2.1 Documenet has a note:
This specification requires that implementations also
implement some version of the Window object
specification, so all HTMLDocument objects also
implement the DocumentWindow object and thus
the DocumentView object.
I think the last two object should
I don't see why comments have to be processed as if they were in body.
They should just be appended to the current node.
--
Anne van Kesteren
http://annevankesteren.nl/
http://www.opera.com/
Le 11 déc. 2006 à 21:25, Ian Hickson a écrit :
On Mon, 11 Dec 2006, Michel Fortin wrote:
div profile=http://microformats.org/wiki/hcard-profile;
class=vcard
a class=url fn href=http://tantek.com/;Tantek Çelik/a
div class=orgTechnorati/div
/div
Given that nobody does the
On Tue, 12 Dec 2006, Karl Dubost wrote:
I think it would help to have a rationale behind each decision or at
least showing the different solution which have been proposed. A bit
like wikipedia when an article is put online, there is an equilibrium
showing the two points of view or more if
Mike Schinkel wrote:
But you are assuming there is a downside to them for calling it foo-name
vs. just name. There isn't; developers use conventions all the time. And
if you read my proposal clearly, the prefix is only needed on a top-level
element or to disambiguate.
I'm not sure if you
On Dec 12, 2006, at 15:36, Anne van Kesteren wrote:
On Tue, 12 Dec 2006 14:31:23 +0100, Henri Sivonen [EMAIL PROTECTED]
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
On Dec 11, 2006, at 23:42, James Graham wrote:
Those people who really are just using class names as site-specific
style hooks must face the possibility that someone will register
their opaque classname with some unexpected semantics or
restrictions on its use and, suddenly, find their
Hi,
From: Ian Hickson [EMAIL PROTECTED]
I agree that it would be interesting. I don't have the time to set
something like this up, sadly. However, if you are willing to help, I
would definitely be open to chatting on IRC to explain various design
decisions which you could then document on the
On Wed, 13 Dec 2006, Simon Pieters wrote:
Here's another suggestion: in the future, when you make desicions and
have the reasons for the desicions at hand (e.g., in IRC), then you
could paste them as comments in the spec.
I already do this for things where the explanations are brief
On 11-Dec-06, at 8:02 PM, Ian Hickson wrote:
Your use of the term microformat seems very loose. A microformat
isn't
just anything that uses keywords in HTML's extension attributes; a
microformat is a format that has gone through the very rigorous
process of
research, design, and public
On Wed, 13 Dec 2006 01:51:32 +0530, Henri Sivonen [EMAIL PROTECTED] wrote:
On Dec 12, 2006, at 15:36, Anne van Kesteren wrote:
On Tue, 12 Dec 2006 14:31:23 +0100, Henri Sivonen [EMAIL PROTECTED]
wrote:
why does finding a number in text [1] insist on . as a decimal
seperator, when , is also
On Dec 13, 2006, at 08:32, Charles McCathieNevile wrote:
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?
It can't. But why bother making a standard that so clearly fails to
work in
16 matches
Mail list logo
