From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: eliz@gnu.org
Cc: brobecker@adacore.com, gdb@sourceware.org, ludo@gnu.org
Subject: Re: "coding: utf-8" emacs local variable in ChangeLog (?)
Date: Tue, 06 Jan 2009 21:26:00 -0000 [thread overview]
Message-ID: <200901062125.n06LPZUc011511@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <ur63gkwc1.fsf@gnu.org> (message from Eli Zaretskii on Tue, 06 Jan 2009 22:34:22 +0200)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1852 bytes --]
> Date: Tue, 06 Jan 2009 22:34:22 +0200
> From: Eli Zaretskii <eliz@gnu.org>
>
> > Date: Sun, 4 Jan 2009 00:56:28 +0100 (CET)
> > From: Mark Kettenis <mark.kettenis@xs4all.nl>
> > CC: brobecker@adacore.com, gdb@sourceware.org, ludo@gnu.org
> >
> > > > I can see why Ludovic wants to have his name spelled properly, but
> > > > he should realize it'll look like "Ludovic Court?\203?is" to many
> > > > people.
> > >
> > > Not if they use Emacs.
> >
> > What do you think I'm using? Ok, that's in emacs running in screen
> > running in an xterm, and those question marks are really some funny
> > looking character that I wouldn't know how to type.
>
> "C-u C-x =" will spell what is that character, and there's
> latin1-disp.el that can display quite a few of these characters even
> on a text terminal.
This is what C-u C-x says about the funny character in Ludo's name:
character: Ã (0303, 195, 0xc3)
charset: eight-bit-graphic (8-bit graphic char (0xA0..0xFF))
code point: 195
syntax: whitespace
category:
buffer code: 0xC3
file code: 0xC3 (encoded by coding system raw-text-unix)
terminal code: not encodable
> > But even if I look at the 2007 ChangeLog with emacs running as an X
> > application Ludo's last name shows up with that funny capital A with
> > a tiled and " after it. I'm fairly sure that's not right.
>
> That's _exactly_ the reason to add the `coding' cookie: you were
> looking at what happens when Emacs tries to interpret a utf-8 encoded
> text as if it were Latin-1 (or maybe Latin-9) encoded. Now, after the
> cookie was added, I see Ludo's name displayed correctly.
I'm not saying that adding the `coding' cookie is a problem. I'm
arguing that turning ChangeLog into a UTF-8 encoded file was a bad
decision, since there are enough systems where it will not be properly
displayed.
next prev parent reply other threads:[~2009-01-06 21:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-03 6:14 Joel Brobecker
2009-01-03 9:48 ` Eli Zaretskii
2009-01-03 10:23 ` Mark Kettenis
2009-01-03 12:45 ` Eli Zaretskii
2009-01-03 23:56 ` Mark Kettenis
2009-01-06 20:34 ` Eli Zaretskii
2009-01-06 21:26 ` Mark Kettenis [this message]
2009-01-06 21:59 ` Eli Zaretskii
2009-01-06 22:49 ` Mark Kettenis
2009-01-07 4:19 ` Eli Zaretskii
2009-01-07 10:06 ` Mark Kettenis
2009-01-07 21:06 ` Eli Zaretskii
2009-01-03 12:35 ` Ludovic Courtès
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=200901062125.n06LPZUc011511@brahms.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=ludo@gnu.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox