From: Kenichi Handa <handa@ni.aist.go.jp>
To: Andreas Schwab <schwab@suse.de>
Cc: svenjoac@gmx.de, emacs-devel@gnu.org
Subject: Re: Garbled non-Ascii characters in ChangeLog files
Date: Thu, 27 Mar 2008 08:10:48 +0900 [thread overview]
Message-ID: <E1Jeelc-0005dA-8m@etlken.m17n.org> (raw)
In-Reply-To: <jezlslkdbs.fsf@sykes.suse.de> (message from Andreas Schwab on Wed, 26 Mar 2008 11:08:07 +0100)
In article <jezlslkdbs.fsf@sykes.suse.de>, Andreas Schwab <schwab@suse.de> writes:
> Sven Joachim <svenjoac@gmx.de> writes:
> > It seems that non-Ascii characters have been messed up in ChangeLog
> > files for a while. For instance, the latest entry in lisp/ChangeLog in
> > EMACS_22_BASE looks like this:
> >
> > ,----
> > | 2008-03-25 Johan Bockg^[$(Q)[^[(Brd <bojohan@gnu.org>
> > |
> > | * info.el (Info-isearch-search): Always return point.
> > |
> > `----
> >
> > The trunk show similar garbage for Jan Djärv's changes in several files,
> > apparently starting after the merge of the unicode-2 branch.
> That appears to be a bug in the iso-2022 decoder in Emacs 22. Emacs 23
> can decode this properly.
"ESC $ ( Q" is for a charset newly introduced in Emacs 23.
So, Emacs 22 doesn't know how to decode it, and as Emacs 22
has a limitation on the number of charsets, there's no way
to support all of such escape sequence.
---
Kenichi Handa
handa@ni.aist.go.jp
next prev parent reply other threads:[~2008-03-26 23:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-26 9:24 Garbled non-Ascii characters in ChangeLog files Sven Joachim
2008-03-26 10:08 ` Andreas Schwab
2008-03-26 23:10 ` Kenichi Handa [this message]
2008-03-27 4:17 ` Eli Zaretskii
2008-03-27 7:26 ` Kenichi Handa
2008-03-27 19:56 ` Eli Zaretskii
2008-03-28 1:28 ` Kenichi Handa
2008-03-26 10:29 ` iso-2022-7bit coding changed (Was: Garbled non-Ascii characters in ChangeLog files) Jan Djärv
2008-03-26 10:39 ` Juanma Barranquero
2008-03-26 10:46 ` Garbled non-Ascii characters in ChangeLog files Kenichi Handa
2008-03-26 10:55 ` Juanma Barranquero
2008-03-26 14:55 ` Stefan Monnier
2008-03-28 1:27 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1Jeelc-0005dA-8m@etlken.m17n.org \
--to=handa@ni.aist.go.jp \
--cc=emacs-devel@gnu.org \
--cc=schwab@suse.de \
--cc=svenjoac@gmx.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.