W3C home > Mailing lists > Public > public-i18n-core@w3.org > January to March 2006

Re: I18n comment: prefix binding mechanism

From: Felix Sasaki <fsasaki@w3.org>
Date: Mon, 23 Jan 2006 23:39:08 +0900
To: www-style@w3.org, public-i18n-core@w3.org
Message-ID: <op.s3t5nia2x1753t@ibm-60d333fc0ec>

On Sat, 21 Jan 2006 19:37:39 +0900, <ishida@w3.org> wrote:

>
> Comment from the i18n review of:
> http://www.w3.org/TR/2005/WD-css3-selectors-20051215/
>
> Comment 6
> At http://www.w3.org/International/reviews/0601-css3-selectors/
> Editorial/substantive: S
> Location in reviewed document:
> Sec. 6.1.1  
> [http://www.w3.org/TR/2005/WD-css3-selectors-20051215/#typenmsp]
>
> Comment:
> In 6.1.1, it should be made clear that the styling language (e.g. CSS)  
> must provide a prefix binding mechanism. It is also unclear what effect,  
> if any, namespace declarations in the document being styled have on  
> prefixes used in the stylesheet.
>
>
>
>> From: Bjoern Hoehrmann [mailto:derhoermi@gmx.net]
>> Sent: 20 January 2006 15:22
>
>> Regarding #6, I'm a bit lost here, the draft notes precisely
>> this three times already and points out, three times, where
>> additional information can be found at some point. What's the
>> problem here exactly?
>
>
>
>> From: Daniel Glazman
>> [mailto:daniel.glazman@disruptive-innovations.com]
>> Sent: 20 January 2006 16:00
>
>> #6 "A type selector containing a namespace prefix that has
>> not been previously
>>      declared is an invalid selector. The mechanism for
>> declaring a namespace
>>      prefix is left up to the language implementing
>> Selectors. In CSS, such a
>>      mechanism is defined in the General Syntax module."
>
>

again: do you depend on css or not?
Received on Monday, 23 January 2006 14:39:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 1 October 2008 10:18:50 GMT