Good Morning,
There is a new version of the relevant document (still in draft) out since
yesterday. You may want to check it:
http://www.w3.org/TR/charmod/
It is stated there under 4.3:
>[S] [I] A text-processing component that receives suspect text MUST NOT
>perform any normalization-sensitive operations unless it has first
>successfully validated the text for normalization, and MUST NOT normalize
>the suspect text.
At 17:55 20.02.2002 +0100, Marco Cimarosti wrote:
-------------------------
>What (canonical or compatibility) *composition* normalization does is
>converting a sequence to a precomposed character, *if* one exist. What W3C
>says when they mandate composition is that a sequence like "a" + combining
>tilde has to be converted to the single code point "a with tilde".
Yes. And since there is a precomposed character for "A WITH CIRCUMFLEX", a
web browser obviously should reject a combination of "A" "COMBINING
CIRCUMFLEX", and not try to normalize it to NFC like IE5.5 does.
>Why? Isn't that what W3C asked? The only risk is that the normalization is a
>waste of time, because it has already been made by the server.
According to my understanding the server should NOT do any normalization,
but the authoring tools should do it.
>BTW, are you sure that it is NFKC? My understanding is that it was NFC +
>some extra passages. For instance, would superscript numbers like "²" be
>turned to "2"? I hope not, as that would break lots of web pages.
Correct. Webcontent is NFC..., IDNs will be NFKC. Sorry, I mixed that.
>The renderer is a DLL called Uniscribe, which is not shipped by default with
>all MS operating systems. I think that 95, 98 and ME only receive by
>installing IE support for some languages.
Thank you. Good hint. I will check that.
> > Anybody experiences with other OSs / other characters?
>
>To my experience, most Windows NT apps behave like your description: things
>are better only inside IE. But Windows 2000 seems to work fine out of the
>box, in most applications.
It is planned, that by mid 2002, Unicode (actually a national standard,
which is based on Unicode) will be compulsory standard in all State Offices
in Vietnam. If all users had to upgrade to an unknown OS (Win2k) and maybe
even purchase new equipment, because their existing one is too slow for the
new OS, then we will make no friends with the introduction of Unicode....
Cheers,
Stefan
This archive was generated by hypermail 2.1.2 : Wed Feb 20 2002 - 21:58:01 EST