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.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 6721 in the body.
You can then email your comments to 6721 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to owner <at> debbugs.gnu.org, bug-gnu-emacs <at> gnu.org:
bug#6721; Package emacs. (Sat, 24 Jul 2010 19:52:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to David De La Harpe Golden <david <at> harpegolden.net>:
New bug report received and forwarded. Copy sent to bug-gnu-emacs <at> gnu.org. (Sat, 24 Jul 2010 19:52:02 GMT) Full text and rfc822 format available.

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

From: David De La Harpe Golden <david <at> harpegolden.net>
To: bug-gnu-emacs <at> gnu.org
Cc: James Cloos <cloos <at> jhcloos.com>
Subject: X11 Compound Text vs ISO 2022
Date: Sat, 24 Jul 2010 20:50:52 +0100
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)





Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#6721; Package emacs. (Tue, 08 Dec 2020 17:37:01 GMT) Full text and rfc822 format available.

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




Added tag(s) moreinfo. Request was from Lars Ingebrigtsen <larsi <at> gnus.org> to control <at> debbugs.gnu.org. (Tue, 08 Dec 2020 17:37:02 GMT) Full text and rfc822 format available.

Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#6721; Package emacs. (Thu, 21 Jan 2021 17:33:02 GMT) Full text and rfc822 format available.

Message #13 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: Thu, 21 Jan 2021 18:32:00 +0100
Lars Ingebrigtsen <larsi <at> gnus.org> writes:

> 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?

More information was requested, but no response was given within a
month, so I'm closing this bug report.  If the problem still exists,
please respond to this email and we'll reopen the bug report.

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




bug closed, send any further explanations to 6721 <at> debbugs.gnu.org and David De La Harpe Golden <david <at> harpegolden.net> Request was from Lars Ingebrigtsen <larsi <at> gnus.org> to control <at> debbugs.gnu.org. (Thu, 21 Jan 2021 17:33:03 GMT) Full text and rfc822 format available.

bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Fri, 19 Feb 2021 12:24:04 GMT) Full text and rfc822 format available.

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.