Re: Update on I18n-ISSUE-2: Why not using xml:lang?

Thank you for your consideration of this comment. The i18n working group 
is not unanimously agreed that xml:lang will serve better than another 
attribute for indicating localization choices, but we will accept that 
you have given this thought and will not object to your moving forward 
as described in your response.

On behalf of the i18n WG,

PS: One personal comment: I noticed just now that when you hover over

"The text elements MAY be given a lang attribute in the XML namespace 

the highlighting covers only

"The text elements MAY be given a lang attribute"

I think it may lead to fewer mistakes on the part of the reader if you 
highlight the whole sentence, since the XML namespace part is crucial.

On 01/06/2011 14:35, Chris Lilley wrote:
> Hello public-i18n-core,
> Just to update you on this issue, your proposal to use @xml:lang
> instead of @lang was accepted. We allowed old content to use @lang and
> require new content to use @xml:lang.
> The editors draft has been updated as has the RelaxNG:
>    Several elements store their data in text child elements; this is to
>    support localization. The text elements MAY be given a lang
>    attribute in the XML namespace [XML]. For backwards compatibility,
>    lang attributes in the default namepsace are also accepted in older
>    content, and SHOULD be treated the same as xml:lang. New content
>    SHOULD instead use xml:lang.
> It would be great if you could send an email message to www-font
> acknowledging that this responds to your comment (for our last call
> tracking purposes). We are now under some time pressure to close out
> last call.

Richard Ishida
Internationalization Activity Lead
W3C (World Wide Web Consortium)

Received on Thursday, 2 June 2011 07:28:34 UTC