GNU bug report logs - #330
Emacs 22.2: iso-2022-jp fails to encode some valid characters

Previous Next

Package: emacs;

Reported by: achurch <at> achurch.org (Andrew Church)

Date: Wed, 28 May 2008 03:50:03 UTC

Severity: normal

Tags: moreinfo

Done: Lars Magne 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 330 in the body.
You can then email your comments to 330 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 bug-submit-list <at> lists.donarmstrong.com, Emacs Bugs <bug-gnu-emacs <at> gnu.org>:
bug#330; Package emacs. Full text and rfc822 format available.

Acknowledgement sent to achurch <at> achurch.org (Andrew Church):
New bug report received and forwarded. Copy sent to Emacs Bugs <bug-gnu-emacs <at> gnu.org>. Full text and rfc822 format available.

Message #5 received at submit <at> emacsbugs.donarmstrong.com (full text, mbox):

From: achurch <at> achurch.org (Andrew Church)
To: bug-gnu-emacs <at> gnu.org
Subject: Emacs 22.2: iso-2022-jp fails to encode some valid characters
Date: Wed, 28 May 2008 12:42:38 JST
The iso-2022-jp coding system in Emacs 22.2 seems to fail to encode
certain characters which are in fact valid in that coding system.  For
example, Unicode character U+2606 WHITE STAR encodes to 0x21 0x79 in
ISO-2022-JP (JIS X 0208), but when one attempts to save a buffer
containing this character, Emacs complains about being unable to encode
that character, and prompts the user to select a different coding system.
The same is true for U+266A EIGHTH NOTE (0x22 0x76), and possibly others.

I'd like to be able to offer a patch, but I haven't been able to locate
where the encoding mappings are defined in the Emacs source code.  If you
can point me in the right direction, I'll see what I can do.

  --Andrew Church
    achurch <at> achurch.org
    http://achurch.org/





Information forwarded to bug-submit-list <at> lists.donarmstrong.com, Emacs Bugs <bug-gnu-emacs <at> gnu.org>:
bug#330; Package emacs. Full text and rfc822 format available.

Acknowledgement sent to Eli Zaretskii <eliz <at> gnu.org>:
Extra info received and forwarded to list. Copy sent to Emacs Bugs <bug-gnu-emacs <at> gnu.org>. Full text and rfc822 format available.

Message #10 received at submit <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Andrew Church <achurch <at> achurch.org>, 330 <at> debbugs.gnu.org
Cc: bug-gnu-emacs <at> gnu.org, bug-submit-list <at> donarmstrong.com,
        bug-gnu-emacs <at> gnu.org
Subject: Re: bug#330: Emacs 22.2: iso-2022-jp fails to encode some valid	characters
Date: Wed, 28 May 2008 22:07:38 +0300
> From: achurch <at> achurch.org (Andrew Church)
> Date: Wed, 28 May 2008 12:42:38 JST
> Cc: 
> 
> The iso-2022-jp coding system in Emacs 22.2 seems to fail to encode
> certain characters which are in fact valid in that coding system.  For
> example, Unicode character U+2606 WHITE STAR encodes to 0x21 0x79 in
> ISO-2022-JP (JIS X 0208), but when one attempts to save a buffer
> containing this character, Emacs complains about being unable to encode
> that character, and prompts the user to select a different coding system.

What does Emacs tell about these characters if you go to them and type
"C-u C-x ="?  Compare that to what Emacs displays for the same
characters in an iso-2022-jp encoded file, and you might have a hint
as to the nature of the problem.





Information forwarded to bug-submit-list <at> lists.donarmstrong.com, Emacs Bugs <bug-gnu-emacs <at> gnu.org>:
bug#330; Package emacs. Full text and rfc822 format available.

Acknowledgement sent to Eli Zaretskii <eliz <at> gnu.org>:
Extra info received and forwarded to list. Copy sent to Emacs Bugs <bug-gnu-emacs <at> gnu.org>. Full text and rfc822 format available.

Tags added: moreinfo Request was from Chong Yidong <cyd <at> stupidchicken.com> to control <at> emacsbugs.donarmstrong.com. (Sun, 07 Sep 2008 19:00:05 GMT) Full text and rfc822 format available.

bug closed, send any further explanations to 330 <at> debbugs.gnu.org and achurch <at> achurch.org (Andrew Church) Request was from Lars Magne Ingebrigtsen <larsi <at> gnus.org> to control <at> debbugs.gnu.org. (Sun, 11 Sep 2011 17:13:01 GMT) Full text and rfc822 format available.

Information forwarded to owner <at> debbugs.gnu.org, bug-gnu-emacs <at> gnu.org:
bug#330; Package emacs. (Sun, 11 Sep 2011 17:38:03 GMT) Full text and rfc822 format available.

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

From: Lars Magne Ingebrigtsen <larsi <at> gnus.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: Andrew Church <achurch <at> achurch.org>, bug-submit-list <at> donarmstrong.com,
	330 <at> debbugs.gnu.org
Subject: Re: bug#330: Emacs 22.2: iso-2022-jp fails to encode some
	valid	characters
Date: Sun, 11 Sep 2011 19:05:08 +0200
Eli Zaretskii <eliz <at> gnu.org> writes:

> What does Emacs tell about these characters if you go to them and type
> "C-u C-x ="?  Compare that to what Emacs displays for the same
> characters in an iso-2022-jp encoded file, and you might have a hint
> as to the nature of the problem.

More information was requested three years ago, but apparently wasn't
given, so I'm closing this bug report.  Please reopen if it's still
valid.

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




bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Mon, 10 Oct 2011 11:24:03 GMT) Full text and rfc822 format available.

This bug report was last modified 13 years and 312 days ago.

Previous Next


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