From: David De La Harpe Golden <david@harpegolden.net>
To: Emacs developers <emacs-devel@gnu.org>
Cc: James Cloos <cloos@jhcloos.com>, Kenichi Handa <handa@m17n.org>
Subject: Re: X11 Compound Text vs ISO 2022
Date: Thu, 08 Jul 2010 01:24:14 +0100 [thread overview]
Message-ID: <4C351AAE.5070700@harpegolden.net> (raw)
In-Reply-To: <m3pqyzul31.fsf@carbon.jhcloos.org>
On 07/07/10 20:51, James Cloos wrote:
> I misstated that. Ctext should still use the 8859 sets where possible,
> and the GB_2312-80, JIS_X0208-1983, JIS_X0208-1990, KS_C_5601-1987 and
> CNS11643-1992 sets(but not JIS_X0213) for characters covered by Emacs'
Modifying function mule.el/ctext-non-standard-encodings-table with, say*:
(not (string-match "jisx0213" (symbol-name charset)))
in its charset-list-walking dolist does exclude that in particular from
consideration, yielding:
(encode-coding-string "•" 'compound-text-with-extensions)
"^[%G\342\200\242^[%@"
... But excluding ones that are not expected to work may be contrary
given a shortlist of ones that can be expected to work (I'm still a bit
unclear why adding a :charset-list with a shortlist to definition of
compound-text-with-extensions didn't work, maybe something isn't getting
bound somewhere.)
[* similar to existing line for excluding cns11643, which I think was
because "big5" was preferred, see
"bzr log -r52413.1.843"/"bzr diff -r52413.1.842..52413.1.843"]
next prev parent reply other threads:[~2010-07-08 0:24 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 [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C351AAE.5070700@harpegolden.net \
--to=david@harpegolden.net \
--cc=cloos@jhcloos.com \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).