[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: X11 Compound Text vs ISO 2022
From: |
James Cloos |
Subject: |
Re: X11 Compound Text vs ISO 2022 |
Date: |
Fri, 30 Jul 2010 14:46:55 -0400 |
User-agent: |
Gnus/5.110011 (No Gnus v0.11) Emacs/24.0.50 (gnu/linux) |
>>>>> "KH" == Kenichi Handa <address@hidden> writes:
KH> iso-8859-1, ctext-with-extensions, utf-8 respectively in
KH> this order.
D'Oh. I read COMPOUND_TEXT even though you wrote ctext. :(
KH> By the way, the spec of COMPOUND_TEXT (included in
KH> xorg-docs-1.5) lists these registered charsets.
KH> ISO8859-1 through ISO8859-9
KH> JISX0201.1976-0
KH> GB2312.1980-0
KH> JISX0208.1983-0
KH> KSC5601.1987-0
KH> but libX11-1.3.2/src/xlibi18n/lcCT.c lists many more
KH> charsets (e.g. more 8859 series and all CNS11643 series).
KH> I think it is better to follow the above spec than lcCT.c.
KH> What do you think?
The changes to the code go back many, many years, and I (as an Xorg
member) expect that the spec will be updated to match the code.
So I'd follow the Xlib code rather than the spec.
-JimC
--
James Cloos <address@hidden> OpenPGP: 1024D/ED7DAEA6
- Re: X11 Compound Text vs ISO 2022, (continued)
Re: X11 Compound Text vs ISO 2022, David De La Harpe Golden, 2010/07/06
Re: X11 Compound Text vs ISO 2022, Kenichi Handa, 2010/07/29