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

[Edward G.J. L. <ed...@ms...>]

Hi,

On Wed, Jan 09, 2002, Araki Ken wrote:
> >   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.

  This confuse me somewhat, in
  ftp://xcin.linux.org.tw/pub/xcin/i18n/charset/BIG5.gz
  There had same maping for those "unstandard" chracters.

  Sorry, I didn't say clearly. I'm using big5 locale(not big5hkscs).
  I can display those extra characters even big5 Japanese charaters,
  but can not display it, when i use AA(-A). 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).

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

  Thanks the hint. I can display those "unstandard" chinese characters now.
  I will try to figure out to display the big5 encoding Japanese characters.

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

  Thanks, I forgot that Xft accepts Unicode only(Keith had been said
  that before).


-- 
Warm Regards,
Edward G.J. Lee