W3C home > Mailing lists > Public > public-i18n-core@w3.org > April to June 2011

RE: Unicode Normalization: request for TAG discussion and a finding

From: Paul Cotton <Paul.Cotton@microsoft.com>
Date: Wed, 29 Jun 2011 16:27:43 +0000
To: "Phillips, Addison" <addison@lab126.com>
CC: "public-i18n-core@w3.org" <public-i18n-core@w3.org>, "www-tag@w3.org" <www-tag@w3.org>, "Sam Ruby (rubys@intertwingly.net)" <rubys@intertwingly.net>, "Maciej Stachowiak (mjs@apple.com)" <mjs@apple.com>
Message-ID: <E3EACD022300B94D88613639CF4E25F8279763A4@TK5EX14MBXC136.redmond.corp.microsoft.com>
> In the meantime, documents such as CSS3 Selectors and HTML5 depend on or could be impacted by Unicode Normalization.

Can you please outline how HTML5 is impacted by Unicode Normalization and what the HTML-specific issues might be?

Given that most of the HTML5 specs are in Last Call I would also strongly suggest you file Last Call comments before the deadline (Aug 4) to ensure that the issues you refer to are recorded during the Last Call period.  Can you please do that?

/paulc
HTML WG co-chair

Paul Cotton, Microsoft Canada
17 Eleanor Drive, Ottawa, Ontario K2E 6A3
Tel: (425) 705-9596 Fax: (425) 936-7329


-----Original Message-----
From: www-tag-request@w3.org [mailto:www-tag-request@w3.org] On Behalf Of Phillips, Addison
Sent: Wednesday, June 29, 2011 12:01 PM
To: www-tag@w3.org
Cc: public-i18n-core@w3.org
Subject: Unicode Normalization: request for TAG discussion and a finding

Dear TAG,

The Internationalization WG has recently been asked to look at our recommendations regarding Unicode Normalization in W3C Specs. The current embodiment of our recommendations is Character Model for the WWW: Normalization [1], which was last published as a Working Draft in 2006. That draft was an attempt to remove Early Uniform Normalization as a requirement, since the WG felt it was no longer a reasonable requirement. 

The current Internationalization Core WG has recently considered and discussed the problem of Unicode Normalization, in part because we feel the existing guidelines cannot be reasonably implemented by specs. We resolved to replace CharModNorm with a document that better describes the recommendations and best practices in this area and have started working on revised guidelines [2] based on our current WG consensus. 

In the meantime, documents such as CSS3 Selectors and HTML5 depend on or could be impacted by Unicode Normalization. In a discussion with Peter Linss, co-chair of CSS, and others [4], it was felt that the best course of action was to allow some or all existing specs to make progress while seeking a TAG finding to clarify the direction for normalization going forwards. Some members of our WG feel that closure on the issue of normalization is important for future interoperability.

Therefore, we would like to request that TAG schedule time in about four weeks to review I18N WG's proposed recommendations concerning Unicode Normalization. We would like to have some time so that we can prepare materials for TAG including the options available.

Thanks,

Addison

[1] http://www.w3.org/TR/charmod-norm/ 
[2] http://www.w3.org/International/wiki/CharmodNormSummary 
[3] http://www.w3.org/2011/06/17-cssns-minutes.html


Addison Phillips
Globalization Architect (Lab126)
Chair (W3C I18N WG)

Internationalization is not a feature.
It is an architecture.


Received on Wednesday, 29 June 2011 16:28:13 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 29 June 2011 16:28:14 GMT