• From: "Tony Graham" <tgraham@m...>
• To: xml-dev@l...
• Date: Sat, 2 Feb 2013 23:57:34 -0000 (GMT)

On Sat, February 2, 2013 10:46 pm, Michael Kay wrote:
> Roger, stop reinventing the wheel. This is all known territory you are
> exploring. Read
>
> http://www.w3.org/TR/charmod-norm/
>
> and if you think it's wrong, tell us why.

At present even the WD thinks the WD is wrong:

   This version of this document was published to indicate the
   Internationalization Core Working Group's intention to
   substantially alter or replace the recommendations found here
   with very different recommendations in the near future.

('Near' being a relative term.)

The best indication of the likely changes for the WD is from an unofficial
response to Roger's question on the Unicode list [1]:

| The current consensus is that early uniform normalization is not
| required for the generation of content, that "late
| normalization" (when comparing strings) is also not required, and
| that both of these cases are ingrained in the fabric of Web
| technologies in a way that makes it difficult to change
| them. Thus, content authors and users are cautioned to use a
| *consistent* character sequences in their content, with NFC being
| generally recommended as one way to ensure this.

So, no one, true way, but consistency is good.

Regards,


Tony Graham                                   tgraham@m...
Consultant                                 http://www.mentea.net
Mentea       13 Kelly's Bay Beach, Skerries, Co. Dublin, Ireland
 --  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --
    XML, XSL-FO and XSLT consulting, training and programming

[1] http://www.unicode.org/mail-arch/unicode-ml/y2013-m02/0007.html

• References:
  • Best Practice for designing XML vocabularies containing accentedcharacters -- allow both composed and decomposed forms
    • From: "Costello, Roger L." <costello@m...>
  • Re: Best Practice for designing XML vocabularies containingaccented characters -- allow both composed and decomposed forms
    • From: Michael Kay <mike@s...>