From: Andreas Schwab <schwab@suse.de>
To: Sven Joachim <svenjoac@gmx.de>
Cc: emacs-devel@gnu.org
Subject: Re: Garbled non-Ascii characters in ChangeLog files
Date: Wed, 26 Mar 2008 11:08:07 +0100 [thread overview]
Message-ID: <jezlslkdbs.fsf@sykes.suse.de> (raw)
In-Reply-To: <87abklyh19.fsf@gmx.de> (Sven Joachim's message of "Wed\, 26 Mar 2008 10\:24\:18 +0100")
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.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2008-03-26 10:08 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 [this message]
2008-03-26 23:10 ` Kenichi Handa
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
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=jezlslkdbs.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=emacs-devel@gnu.org \
--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 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).