From: James Cloos <cloos@jhcloos.com>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: emacs-devel@gnu.org, David De La Harpe Golden <david@harpegolden.net>
Subject: Re: X11 Compound Text vs ISO 2022
Date: Wed, 07 Jul 2010 01:19:39 -0400 [thread overview]
Message-ID: <m3y6dnvpfg.fsf@carbon.jhcloos.org> (raw)
In-Reply-To: <87r5jgnn52.fsf@uwakimon.sk.tsukuba.ac.jp> (Stephen J. Turnbull's message of "Wed, 07 Jul 2010 09:36:41 +0900")
>>>>> "SJT" == Stephen J Turnbull <stephen@xemacs.org> writes:
SJT> But that goes against the spec, which AFAIK still provides that in
SJT> COMPOUND_TEXT the escape to non-ISO-2022 should only be used for
SJT> characters not in the repertoires of the registered charsets:
SJT> Extended segments are not to be used for any character set
SJT> encoding that can be constructed from a GL/GR pair of approved
SJT> standard encodings. For example, it is incorrect to use an
SJT> extended segment for any of the ISO 8859 family of encodings.
SJT> I would argue that you have two choices here: consider the whole
SJT> string to be Unicode, and used an extended segment for the whole
SJT> thing; or consider the string to be pieced together from segments in
SJT> approved standard encodings, in which case a character that can be
SJT> represented in those encodings should be.
AFAICT, gtk and qt doe the former, and that is really what I was
suggesting, except when there is reason for Emacs to beleive that the
user may perfer the CJK set.
SJT> BTW, for the case of MIDDLE DOT using JIS X 0213, the most recent spec
SJT> I could find on the web doesn't admit JIS X 0213 (or JIS X 0212 for
SJT> that matter).
Exactly the complaint. And even compound-text-with-extensions makes
that choice. I'm testing the latter now in xfns.c, but the ctext
charsets still need to avoid JIS X 0213.
Yes, that seems to fix everything except the usage of 0213.
>> The question, then, is how best to do that?
SJT> Wouldn't it be better to avoid use of COMPOUND_TEXT targets? How many
SJT> apps prefer it to UTF8_STRING? So, for example, when asked for
SJT> supported targets Emacs could list UTF8_STRING first.
Things are getting better, but ctext is still required for some
properties and for interactions with some other clients. I'd prefer
UTF8_STRING everywhere, but not to the extent of breaking compatability
with the other clients I (and others) use.
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 1024D/ED7DAEA6
next prev parent reply other threads:[~2010-07-07 5:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-06 16:21 X11 Compound Text vs ISO 2022 James Cloos
2010-07-06 20:18 ` David De La Harpe Golden
2010-07-06 22:30 ` James Cloos
2010-07-07 0:36 ` Stephen J. Turnbull
2010-07-07 5:19 ` James Cloos [this message]
2010-07-07 19:51 ` James Cloos
2010-07-08 0:24 ` David De La Harpe Golden
2010-07-14 21:07 ` James Cloos
2010-07-06 23:38 ` David De La Harpe Golden
2010-07-07 1:15 ` David De La Harpe Golden
2010-07-07 4:55 ` James Cloos
2010-07-29 12:36 ` Kenichi Handa
2010-07-29 15:51 ` James Cloos
2010-07-30 1:27 ` Kenichi Handa
2010-07-30 18:46 ` James Cloos
2010-08-01 9:35 ` Stephen J. Turnbull
2010-08-01 11:06 ` James Cloos
2010-08-02 8:14 ` Stephen J. Turnbull
2010-08-06 12:50 ` Kenichi Handa
2010-08-08 9:47 ` James Cloos
2010-08-09 1:49 ` Kenichi Handa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3y6dnvpfg.fsf@carbon.jhcloos.org \
--to=cloos@jhcloos.com \
--cc=david@harpegolden.net \
--cc=emacs-devel@gnu.org \
--cc=stephen@xemacs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.