GNU bug report logs - #6721
X11 Compound Text vs ISO 2022

Previous Next

Package: emacs;

Reported by: David De La Harpe Golden <david <at> harpegolden.net>

Date: Sat, 24 Jul 2010 19:52:02 UTC

Severity: normal

Tags: moreinfo

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


Message #8 received at 6721 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: David De La Harpe Golden <david <at> harpegolden.net>
Cc: 6721 <at> debbugs.gnu.org, James Cloos <cloos <at> jhcloos.com>
Subject: Re: bug#6721: X11 Compound Text vs ISO 2022
Date: Tue, 08 Dec 2020 18:35:46 +0100
David De La Harpe Golden <david <at> harpegolden.net> writes:

> 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).

(This bug report unfortunately got no response at the time.)

I had a look at the emacs-devel URL, but I'm still not quite sure in
what circumstances Emacs sends `compound-text' to other X clients.  Is
this something you still see in more recent Emacs versions, and if so --
do you have a recipe to reproduce this bug?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no




This bug report was last modified 4 years and 117 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.