From: James Cloos <cloos@jhcloos.com>
To: Kenichi Handa <handa@m17n.org>
Cc: stephen@xemacs.org, emacs-devel@gnu.org, david@harpegolden.net
Subject: Re: X11 Compound Text vs ISO 2022
Date: Sun, 08 Aug 2010 05:47:36 -0400 [thread overview]
Message-ID: <m3tyn5qvu7.fsf@carbon.jhcloos.org> (raw)
In-Reply-To: <tl7bp9fsy4u.fsf@m17n.org> (Kenichi Handa's message of "Fri, 06 Aug 2010 21:50:57 +0900")
>>>>> "KH" == Kenichi Handa <handa@m17n.org> writes:
KH> I've just committed a new code to make ctext-with-extensions
KH> conform to X's Compound Text spec.
Thanks.
I read through the patch on the diffs list; everything looked right.
KH> As for which charsets to treat as "the standard encodings", I made a
KH> variable ctext-standard-encodings and set the default value to this
KH> at the moment (i.e. following the current (old) SPEC).
Good idea!
KH> The new code was committed to emacs-23 branch, but I don't
KH> know when it is propagated to the trunk.
I will probably wait until it is merged into trunk to test; all of my
systems currently run trunk or a packaged snapshot thereof.
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 1024D/ED7DAEA6
next prev parent reply other threads:[~2010-08-08 9:47 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
2010-08-08 9:47 ` James Cloos [this message]
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=m3tyn5qvu7.fsf@carbon.jhcloos.org \
--to=cloos@jhcloos.com \
--cc=david@harpegolden.net \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.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.