[Mlterm-dev-en] commit log , and Big5HKSCS etc.

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

        I committed changes below.

* ESC H (set tab) ESC [ 0 g (clear tab) ESC [ 3 g (clear all tabs) are supported.
* Big5HKSCS encoding/charset is supported.
* US ASCII font is not changed when encoding is changed to ISO8859 variant or UTF8. fixed.
* huge memory leaks when window is resized. fixed.
* input text is received in order of XmbLookupString => XLookupString => Xutf8LookupString.
* UTF8 selection is received as it is.

        I replaced BIG5 <=> UCS table based on
        http://www.unicode.org/Public/MAPPINGS/OTHERS/BIG5.txt
        with the new one base on
        ftp://xcin.linux.org.tw/pub/xcin/i18n/charset/BIG5HKSCS.gz.

        I found some characters(in C6A1-C8FE as well as HKSCS) are mapped to UNICODE
        PUA in it. I don't know whether it is ok or not and why it is like that (especially
        those in C6A1-C8FE) , but I decided to include them anyway.
        Is it preferable to ingore PUA mapped characters ?

        Then , I implemented Big5HKSCS support , too. (just still prototype)
        mlterm doesn't regard Big5HKSCS as supplement of Big5 but as a new character set
        including Big5 , and assumes that a font whose XLFD encoding name is "big5-0"
        or "big5hkscs-0" should include both Big5 and HKSCS , but I don't know if
        these are ok or not.
        
        Please tell me the right way around them.

        Regard,
        
--
kiken
j00...@ip...