From: David De La Harpe Golden <david@harpegolden.net>
To: 6721@debbugs.gnu.org
Subject: bug#6721: X11 Compound Text vs ISO 2022
Date: Sat, 24 Jul 2010 20:50:52 +0100 [thread overview]
Message-ID: <4C4B441C.30900@harpegolden.net> (raw)
Logging issue to tracker so it doesn't disappear behind certain recent
mammoth junk threads:
James Cloos raised on emacs-devel:
http://lists.gnu.org/archive/html/emacs-devel/2010-07/msg00255.html
The problem that emacs has been sending "compound-text" using charsets
not generally supported by other X11 clients. The spec for compound
text seems clear enough, emacs shouldn't do that (though maybe should
remain permissive in what it accepts).
Emacs has compound-text and compound-text-with-extensions, the latter
having support for some widely used extensions to the original spec
including embedded unicode.
Compound-text-with-extensions (since it supports embedded unicode) and
probably compound-text should be restricted to only encoding to the
known shortlist of acceptable charsets for compound-text, including some
but not all of the iso2022 charsets emacs presently supports.
Given UTF8_STRING support in X11, I reckon it is fairly unlikely the set
of acceptable compound text charsets will be expanding much in future.
Emacs should also probably use compound-text-with-extensions in the
places it is currently using compound-text (or just make the former its
latter)
next reply other threads:[~2010-07-24 19:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-24 19:50 David De La Harpe Golden [this message]
2020-12-08 17:35 ` bug#6721: X11 Compound Text vs ISO 2022 Lars Ingebrigtsen
2021-01-21 17:32 ` Lars Ingebrigtsen
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=4C4B441C.30900@harpegolden.net \
--to=david@harpegolden.net \
--cc=6721@debbugs.gnu.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).