From: Kenichi Handa <handa@m17n.org>
To: James Cloos <cloos@jhcloos.com>
Cc: stephen@xemacs.org, david@harpegolden.net, emacs-devel@gnu.org
Subject: Re: X11 Compound Text vs ISO 2022
Date: Fri, 06 Aug 2010 21:50:57 +0900 [thread overview]
Message-ID: <tl7bp9fsy4u.fsf@m17n.org> (raw)
In-Reply-To: <m362zulhh5.fsf@carbon.jhcloos.org> (message from James Cloos on Sun, 01 Aug 2010 07:06:22 -0400)
In article <m362zulhh5.fsf@carbon.jhcloos.org>, James Cloos <cloos@jhcloos.com> writes:
> The compound text spec shows a 1989 copyright, states that it is
> version 1.1 documenting X Version 11 Release 6.8 and notes that
> it might be expandepd in the future.
> The ctext addtions were clearly added to support additional locales.
> And the expansion has stopped thanks to the general shift from iso-
> 2022 to iso-10646.
> Clearly the ctext spec should have followed along with the reference
> code just like, eg, the elisp manual follows the code.
> I think it is more than fair to update the ctext spec to document the
> current reference code, especially now that the document is old enough
> to purchase alcohol in its home country. :)
I've just committed a new code to make ctext-with-extensions
conform to X's Compound Text spec. As for which charsets to
treat as "the standard encodings", I made a variable
ctext-standard-encodings and set the default value to this
at the moment (i.e. following the current (old) SPEC).
ascii latin-jisx0201 katakana-jisx0201 latin-iso8859-1
latin-iso8859-2 latin-iso8859-3 latin-iso8859-4
greek-iso8859-7 arabic-iso8859-6 hebrew-iso8859-8
cyrillic-iso8859-5 latin-iso8859-9 chinese-gb2312
japanese-jisx0208 korean-ksc5601
If we actually find that it is better to follow the current
CODE, we can just add more charsets to the variable.
The new code was committed to emacs-23 branch, but I don't
know when it is propagated to the trunk.
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2010-08-06 12:50 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
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 [this message]
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=tl7bp9fsy4u.fsf@m17n.org \
--to=handa@m17n.org \
--cc=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.