Re: [Mlterm-dev-en] cut&paste problem
Hello KUBOTA san,
Thanks for your explanation, I have to do some homeworks.:)
I hope you don't mind, I Cc to CLE-devel and Debian-Chinese
list, maybe they will be interested about this discussion.
And maybe some people can comment my point of view(I don't
have too much knowledge about this topic and GB/GBK).
On Fri, Dec 07, 2001, Tomohiro KUBOTA wrote:
> Hello,
>
> At 07 Dec 2001 02:16:41 +0900,
> Araki Ken wrote:
>
> > rxvt/aterm copy and paste Big5 characters with ISO2022 ESC % / ... sequence ,
> > but mlterm doesn't still implement it.
> > At the present time mlterm converts Big5 to UTF-8 or CNS11643 in sending or
> > receiving characters with other X applications.
>
> I think converting Big5 into CNS11643 is a bad idea because it is
> not popular in Taiwan.
Big5 encoding(charset) is the popular use in Taiwan, but
has some problem. Big5 has 13094+ characters only. It
means some daily use characters are absent, so if mlterm
can support CNS11643, it will be useful for some people.
CNS11643 is the Taiwan goverment standard. And library,
they use CCCII(75684 characters), all because not enough
characters in Big5.
> When sending a CTEXT which contains Big5 characters:
> - use "XFree86 Big5" way.
>
> When receiving a CTEXT which contains Big5 characters:
> - accept "XFree86 Big5" and "Emacs Big5" ways.
>
> When sending a CTEXT which contains CNS11643 characters:
> - (optional) use "XFree86 Big5" as far as possible (within CNS11643-{1,2}).
> - (optional) use "CNS11643" way for other than CNS11643-{1,2}.
Actually, CNS11643 plane 1,2 which correspond to Big5 level 1,2.
> When receiving a CTEXT which contains CNS11643 characters:
> - (optional) accept "CNS11643" way.
>
> Note that:
> - "XFree86 Big5" is a way used in XTextListToTextProperty().
> Based on XFree86's xc/doc/specs/CTEXT/ctext "6 Non-Standard
> Character Set Encoding".
> 01/11 02/05 02/15 03/02 M L "b" "i" "g" "-" "5" STX (contents)
> Note that "big-5" may be in capital (uppercase).
> The contents is the raw byte sequence of the Big5 string.
>
> - "Emacs Big5" is a way used by Emacs. (Is this CNS11643?)
> Based on XFree86's xc/doc/specs/CTEXT/ctext "11 Extensions".
> It seems to use ESC $ ( 0 and ESC $ ( 1.
>
> - "CNS11643" is the way I don't know. (Used only by mlterm?)
> Are there any instances of this?
>
> This is because:
> - "XFree86 Big5" is the way which is widely used in Taiwan. Because
> Big-5 support is primarily for Taiwan people, mlterm should also
> use this way as far as possible.
> - I discussed with Handa-san (a developer of Mule/Emacs) and we agreed
> that future Emacs will use "XFree86 Big5" for sending/receiving,
> while "Emacs Big5" will be accepted for receiving for compatibility.
>
>
> Could you tell me where is the CTEXT composer and parser of mlterm?
> Since RTL is a heavy work, I will research this problem until you
> finish RTL.
>
>
> References:
>
> XFree86 Big5 bugs (adopted into XFree86 CVS tree in this September)
> http://www.xfree86.org/pipermail/i18n/2001-July/002091.html
>
> Detailed explanation on Big5 and CTEXT by Tung-Han Hsieh
> http://www.xfree86.org/pipermail/i18n/2001-June/002052.html
>
> ---
> Tomohiro KUBOTA <kubota@debian.org>
> http://www.debian.or.jp/~kubota/
> "Introduction to I18N" http://www.debian.org/doc/manuals/intro-i18n/
>
> _______________________________________________
> Mlterm-dev-en mailing list
> Mlterm-dev-en@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mlterm-dev-en
--
Warm Regards,
Edward G.J. Lee¡]§õªG¥¿¡^
Reply to: