Menu
▾
▴
Re: [Mlterm-dev-en] commit log , and Big5HKSCS etc.
|
From: Edward G.J. L. <ed...@ms...> - 2001-12-17 11:30:45
|
Hi, I'm sorry reply so late. I confirm the author of Big5 charmap, here is his comment. And I also mail to Anthony Fok, maybe he will kindly to comment something. === the comment of T.H. Hsieh === : * 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 ? These C6A1-C8FE characters are called "Eten extension". Historically these mapping comes from the old Chinese system running on MS-DOS plateform. Its name is called "Eten Chinese system". Because in that old days only that system is available, so most of people in Taiwan are comfortable with its implimentation. The "Eten extension" defines a lot of symbols and rarely used characters. Since so many people are comfortable with it, so in the recently days many companies and/or orgnizations in Taiwan who want to implement the mapping from Big5 to other encodings (say, Unicode), they all want to take these "Eten extension" into consideration. For example, the Arphic Tech. CO., LTD. maps these characters to the PUA of Unicode. Since these extra symbols and characters are not found in the Unicode definition, but they should be there for compatibility, so they do this mapping. Forthermore, in glibc-2.2, the BIG5 encoding definition is also adjusted to include the "Eten extension" and follows the implementation of Arphic Tech. Co., LTD. Similarly for BIG5HKSCS for Hong Kong. Such extension is also available in XFree86-4.X. So, I suggest that this extension should be also available in mlterm. : 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. The Big5 FontSet now we use is: -*-iso8859-1, -*-big5-0 For the Big5HKSCS, according to Debian's patching (maybe also available in the new comming XFree86) is -*-iso8859-1, -*-big5-0, -*-big5hkscs-0 In my memory, they seems to separate the Hong Kong extension characters out to a new font named -*-big5hkscs-0, such that the pure Big5 part is compatible to the one Taiwan people using. For more details, you may contact Anthony Fok <an...@th...> He is responsible to the Debian Chinese porting and Hong Kong Chinese patching. === The comment of T.H. Hsieh === On Sat, Dec 15, 2001, Araki Ken wrote: > > 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... > > _______________________________________________ > Mlterm-dev-en mailing list > Mlt...@li... > https://lists.sourceforge.net/lists/listinfo/mlterm-dev-en -- Warm Regards, Edward G.J. Lee¡]§õªG¥¿¡^ |
