W3C home > Mailing lists > Public > www-style@w3.org > April 2011

Re: Unicode normalization in CSS

From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
Date: Tue, 12 Apr 2011 03:59:46 +0200
To: Daniel Glazman <daniel.glazman@disruptive-innovations.com>
Cc: fantasai <fantasai.lists@inkedblade.net>, Chris Lilley <chris@w3.org>, Henri Sivonen <hsivonen@iki.fi>, public-i18n-core@w3.org, www-style@w3.org
Message-ID: <20110412035946681679.c3d64c60@xn--mlform-iua.no>
Leif Halvard Silli, Mon, 11 Apr 2011 17:57:04 +0200:
> Leif Halvard Silli, Mon, 11 Apr 2011 17:03:03 +0200:
>> Daniel Glazman, Mon, 11 Apr 2011 16:23:14 +0200:
>>> Le 11/04/11 16:11, Leif Halvard Silli a écrit :
> 
>> Fantasai said she was in lack of conclusion. Since she is a spec 
>> editor, I offer the conclusion that we could document the issues. And 
>> by, "issues", I mean summarize/list the affected letters. And also to 
>> describe *when* it is likely to be an issue, such as when linking to 
>> files - which for instance affect a:visited{}.
> 
> There is a file at www.UNICODE.org which I believe lists the affected 
> characters. [1] Expressing the essence of that list, in light of CSS, 
> with some humanly readable words, would be a good start. (And perhaps 
> creating a tool by which the author can check if his/her letters are 
> affected.) 
 
  [...] 

> [1] http://unicode.org/Public/UNIDATA/DerivedNormalizationProps.txt


I should have pointed to the Normalization Charts instead: 
http://unicode.org/charts/normalization


"The Normalization Charts provide charts of the characters in Unicode 
that differ from at least one of their normalization forms (C, D, KC, 
KD)."
-- 
leif halvard silli
Received on Tuesday, 12 April 2011 02:00:18 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:39 GMT