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

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

	Hi,

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

>   I can display the extra traditional Chinese character(such as
>   U+7881, U+88CF ...) when I use Arphic TTF(bsmi00lp.ttf). But
>   if I use -A and use aafont setting:
>
>   ISO8859_1=AR PL Mingti2L Big5-iso8859-1;
>   BIG5=AR PL Mingti2L Big5-iso10646-1;
>
>   then I cannot display those extra traditional Chinese characters.
>
>   I know it's not the Unicode standard, but I try to change the
>   map table still cannot display.

        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.
        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.

        # FYI , IS_HKSCS_ONLY macro in mkf/lib/mkf_ucs4_big5.c is used in mkf_map_big5_to_ucs4
        # to exclude "unstandard" big5 characters.

        But if you want another mapping table for u+7811 , u+88cf etc , please point it
        to me.

>   Sorry, I have a silly question, can we use big5-0 encoding when
>   need AA function?

        "iso10646-1" is used for specifying a font encoding.
        if your font(Arphic TTF?) is encoded by iso10646-1 , you cannot
        specify big5-0 as an encoding.(this is the specification of Xft)

        And in addition , Xft accepts Unicode only.
        so anyway you cannot avoid big5 => unicode mapping somewhere.

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