From: Kenichi Handa <handa@m17n.org>
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 19:46:54 +0900 [thread overview]
Message-ID: <E1JeT9i-0001lP-Pz@etlken.m17n.org> (raw)
In-Reply-To: <87abklyh19.fsf@gmx.de> (message from Sven Joachim on Wed, 26 Mar 2008 10:24:18 +0100)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=ISO-2022-JP-2, Size: 1010 bytes --]
In article <87abklyh19.fsf@gmx.de>, 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.
> |
> `----
I've just fixed that line for EMACS_22_BASE.
> The trunk show similar garbage for Jan Dj^[$(D+#^[(Brv's changes in several files,
> apparently starting after the merge of the unicode-2 branch.
I see no garbage for Jan's names in the ChangeLog files of
the trunk.
By the way, ChangeLog files use iso-2022-7bit that uses
ESC-sequence for encoding legacy charsets, and to which
legacy charset to map characters depends on the priorities
of charsets (and thus depends on one's locale). Perhaps we
should now use utf-8 for ChangeLog files to keep constant
encoding result.
---
Kenichi Handa
handa@ni.aist.go.jp
next prev parent reply other threads:[~2008-03-26 10:46 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
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 ` Kenichi Handa [this message]
2008-03-26 10:55 ` Garbled non-Ascii characters in ChangeLog files 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=E1JeT9i-0001lP-Pz@etlken.m17n.org \
--to=handa@m17n.org \
--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).