Kent Karlsson wrote:
Crap. Yes, Ken and BabelPad are right. Some ideographs do have
singleton mappings and can thus be different between NFD and NFC.
No, both NFD and NFC will map U+FA47 to U+6F22; singleton canonical
mappings are not "reversed" in the composition phase of transforming
to
On 11/15/2010 5:43 PM, Kenneth Whistler wrote:
Perhaps someone would like to make a detailed proposal to
the UTC for how to fix the text and charts?;-)
Ken,
having shown yourself the master of detail in your reply, I think you've
appointed yourself.
A round of applause for Ken!
See how eas
Asmus replied:
> On 11/15/2010 2:24 PM, Kenneth Whistler wrote:
> >> FA47 is a "compatibility character", and would have a
> >> compatibility mapping.
> > Faulty syllogism.
>
> Formally correct answer but only because of something of a design flaw
> in Unicode. When the type of mapping was deci
Den 2010-11-15 23:53, skrev "Doug Ewell" :
>> When I type the ideograph 漢 (U+FA47) into BabelPad, highlight it, and
>> then click the button labeled "Normalize to NFC", the character
>> becomes 漢 (U+6F22). Does BabelPad not conform to the Unicode Standard
>> in this case? Is this not truly Unicod
On 11/15/2010 2:24 PM, Kenneth Whistler wrote:
FA47 is a "compatibility character", and would have a compatibility mapping.
Faulty syllogism.
Formally correct answer but only because of something of a design flaw
in Unicode. When the type of mapping was decided on, people didn't fully
expect
Jim Monty wrote:
> How cool is it to post an inquiry to the Unicode mailing list and have
> Unicode luminaries like Mark Davis, Asmus Freytag, Markus Scherer,
> Martin Dürst and Doug Ewell ALL reply?
Don't count me among the luminaries. I'm just a student too, studying
Unicode for 19 years now,
> FA47 is a "compatibility character", and would have a compatibility mapping.
Faulty syllogism.
FA47 is a CJK Compatibility character, which means it was encoded
for compatibility purposes -- in this case to cover the round-trip
mapping needed for JIS X 0213.
However, it has a *canonical* deco
FA47 is a "compatibility character", and would have a compatibility mapping.
-Original Message-
From: unicode-bou...@unicode.org [mailto:unicode-bou...@unicode.org] On Behalf
Of Jim Monty
Sent: Monday, November 15, 2010 1:02 PM
To: unicode@unicode.org
Subject: Re: Application that display
Jim, behaviour will depend on fonts being used. It could also depend on the
version of software you are using. Windows 7 has pretty good support (fonts and
Uniscribe) for all of this.
Peter
-Original Message-
From: unicode-bou...@unicode.org [mailto:unicode-bou...@unicode.org] On Beha
Another point:
> Aren't the two versions of the same Unicode text supposed to be
> rendered the same? They're not, at least not in any of the
> applications in which I've viewed them: Microsoft Internet Explorer,
> Microsoft Notepad, Vim, BabelPad and SC Unipad.
SC UniPad uses its own built-in fo
Doug Ewell wrote:
> And no, I did not intend to make this big a deal out of it, and I
> apologize for doing so.
Nor did I.
I'm a genuine student of Unicode, here to learn. It seems many of the regular
contributors to the Unicode and Unicore mailing lists are the Unicode experts
themselves, many
On Windows, strings will display correctly in either NFC or NFD provided an
appropriate font is used--that choice being different for Japanese and for
Korean. Windows 7 and earlier do not ship with fonts that support Old Hangul,
but Old Hangul fonts are available from other sources; e.g. there's
12 matches
Mail list logo
