From: James Cloos <cloos@jhcloos.com>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: david@harpegolden.net, emacs-devel@gnu.org,
Kenichi Handa <handa@m17n.org>
Subject: Re: X11 Compound Text vs ISO 2022
Date: Sun, 01 Aug 2010 07:06:22 -0400 [thread overview]
Message-ID: <m362zulhh5.fsf@carbon.jhcloos.org> (raw)
In-Reply-To: <87hbjeu14p.fsf@uwakimon.sk.tsukuba.ac.jp> (Stephen J. Turnbull's message of "Sun, 01 Aug 2010 18:35:02 +0900")
>>>>> "SJT" == Stephen J Turnbull <stephen@xemacs.org> writes:
>> 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.
SJT> Really? I can't say I'm terribly impressed with X.org's response
SJT> to complaints that specs and behavior don't match.
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. :)
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 1024D/ED7DAEA6
next prev parent reply other threads:[~2010-08-01 11:06 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 [this message]
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=m362zulhh5.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 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).