Re: [gtk-i18n-list] Unicode PUA supporting issue in gtk+/pango

[mpsuzuki hiroshima-u ac jp]

On Sat, 31 Dec 2005 09:53:44 +0800
Zhe Su <james su gmail com> wrote:
>  IMO, it's unfair.

Excuse me, am I accused as unfair?

PRC (or anybody else) had proposed precomposed Tibetan glyphs
to Unicode official inclusion? I could not find any mentions
about such in "proposed new character"
	http://www.unicode.org/alloc/Pipeline.html
nor in "proposed new scripts"
	http://www.unicode.org/pending/pending.html
Oops, I think these pages are not maintained actively.

If the precomposed Tibetan glyphs are proposed to Unicode
already, I didn't know the fact, and I cancell my classification
of precomposed Tibetan glyph into case B.

>There are lots of pre-composed glyphs already included into
>Unicode BMP. So why Tibetan chars can't in it? Compose
>engine for Tibetan is far from perfect, the compose result is
>unacceptable at all.

Good, I've expected so (although it's sad comment for
the developers of Tibetan module in Pango). Please don't
say as if I were against the official Unicode inclusion
of precomposed Tibetan glyphs.

>  So for now, we really need support PUA, because
>such kind of real world problems.

Due to real world problem, Pango's Tibetan module should
support PUA?

Regards,
mpsuzuki

>On 12/31/05, mpsuzuki hiroshima-u ac jp <mpsuzuki hiroshima-u ac jp> wrote:
>> On Fri, 30 Dec 2005 10:01:15 -0500
>> Matthias Clasen <matthias clasen gmail com> wrote:
>>
>> >On 12/30/05, Christopher Fynn <cfynn gmx net> wrote:
>> >>
>> >> PRC are also now using PUA as a "standard" encoding (in GB1300 (? &
>> >> GB18030 ?))  for pre-composed Tibetan "characters".
>> >
>> >standardizing the private use area ?
>> >sounds a bit oxymoromic to me ....
>>
>> Aha, "standardize" of precomposed Tibetan characters
>> is prepared (or finished?) in PRC's national standard.
>> I never heard PRC is pushing them into International
>> standards.
>>
>> PRC government know it's difficult to force computer
>> vendors to use GB18030 as "internal" character encoding,
>> so, to use GB18030 (as external character encoding)
>> in the system whose internal character encoding is
>> UTF-16, PRC government maps their natinally-standardized
>> characters to PUA codepoints, if the characters are
>> not available in Unicode.
>>
>> There are 2 different situation in "unavailability".
>>
>> A. The character is already proposed to Unicode,
>>    but new version of Unicode is not published yet.
>>
>> B. The character won't be included in Unicode,
>>    because it violates Unicode character inclusion
>>    policy.
>>
>> The extra Hanzi charset for Hong Kong is A.
>> The precomposed Tibetan charset is B.
>>
>> Arne G and Chia-I Wu told that there are similar
>> issues (A & B) in Taiwanese standard CNS11643.
>>
>> Regards,
>> mpsuzuki
>> _______________________________________________
>> gtk-i18n-list mailing list
>> gtk-i18n-list gnome org
>> http://mail.gnome.org/mailman/listinfo/gtk-i18n-list
>>