Re: [Mlterm-dev-en] About some Trad-Chinese characters.

[Araki K. <j00...@ip...>]

	Hi,

	Subject: Re: [Mlterm-dev-en] About some Trad-Chinese characters.
	From: "Edward G.J. Lee" <ed...@ms...>
	Message-ID: <200...@da...>
	Date: Wed, 9 Jan 2002 22:56:30 +0800

>>         Well , big5 to ucs mapping table of mlterm (mkf/lib/table/mkf_big5_to_ucs4.table)
>>         confirms to ftp://xcin.linux.org.tw/pub/xcin/i18n/charset/BIG5HKSCS.gz.
           ^^^^^^^^ conforms:)
>>         and u+7881 is mapped to 0xf9d6(big5) and u+88cf is mapped to 0xf9d8.
>>         But these big5 characters are regarded as HKSCS charset , so you cannot
>>         use these mappings without -E big5hkscs option.
>
>   This confuse me somewhat, in
>   ftp://xcin.linux.org.tw/pub/xcin/i18n/charset/BIG5.gz
>   There had same maping for those "unstandard" chracters.

        Oh , sorry , I made a serious mistake.
        
        mlterm always regards all in 0x8140 - 0xa0fe , 0xc6a1 - 0xc8fe , 0xf9d6 - 0xfefe
        as hkscs character set when mapping between big5 and unicode in mkf_big5_ucs4.c
        so you cannot convert them to unicode under Big5(not big5hkscs) encoding.

        On the other hand , they are normally regarded as Big5 characters
        in mkf_big5_parser.c , which parses Big5 string , under Big5 encoding.

        That's why you can show them without anti alias , and cannot show with anti alias.

        I'll support unstandard characters in BIG5.gz.
        
>   The another problem is big5 Japanese characters are not the same maping in
>   BIG5.gz and BIG5HKSCS.gz. Such as U+F6F8 => 0xc6e8(big5), U3042 => 0xc6e8(big5hkscs).

        OK , I see.

--
kiken
j00...@ip...