Hmm, I find that disconcerting. I’d prefer a real Unicode character with special weights if that concept’s needed. And I guess that goes a long ways to explaining the interchange problem since clearly the code editor’s going to need these ☹
From: Markus Scherer [mailto:[email protected]] Sent: Monday, June 2, 2014 10:17 AM To: Shawn Steele Cc: Asmus Freytag; Doug Ewell; Mark Davis ☕️; Unicode Mailing List Subject: Re: Corrigendum #9 On Mon, Jun 2, 2014 at 10:00 AM, Shawn Steele <[email protected]<mailto:[email protected]>> wrote: To further my understanding, can someone provide examples of how these are used in actual practice? CLDR collation data defines special contraction mappings that start with a noncharacter, for http://www.unicode.org/reports/tr35/tr35-collation.html#CJK_Index_Markers In CLDR 23 and before (when we were still using XML collation syntax), these were raw noncharacters in the .xml files. As I said earlier: it should be ok to include noncharacters in CLDR data files for processing by CLDR implementations, and it should be possible to edit and diff and version-control and web-view those files etc. markus
_______________________________________________ Unicode mailing list [email protected] http://unicode.org/mailman/listinfo/unicode
