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

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.

 Chris Lilley   Technical Director, Interaction Domain                 
 W3C Graphics Activity Lead, Fonts Activity Lead
 Co-Chair, W3C Hypertext CG
 Member, CSS, WebFonts, SVG Working Groups

Received on Wednesday, 1 June 2011 13:40:51 UTC