From: Eli Zaretskii <eliz@gnu.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: brobecker@adacore.com, gdb@sourceware.org, ludo@gnu.org
Subject: Re: "coding: utf-8" emacs local variable in ChangeLog (?)
Date: Wed, 07 Jan 2009 04:19:00 -0000 [thread overview]
Message-ID: <u7i57lpe8.fsf@gnu.org> (raw)
In-Reply-To: <200901062246.n06Mkwp6008750@brahms.sibelius.xs4all.nl>
> Date: Tue, 6 Jan 2009 23:46:58 +0100 (CET)
> From: Mark Kettenis <mark.kettenis@xs4all.nl>
> CC: brobecker@adacore.com, gdb@sourceware.org, ludo@gnu.org
>
> > Date: Tue, 06 Jan 2009 23:59:29 +0200
> > From: Eli Zaretskii <eliz@gnu.org>
> >
> > > Date: Tue, 6 Jan 2009 22:25:36 +0100 (CET)
> > > From: Mark Kettenis <mark.kettenis@xs4all.nl>
> > > CC: brobecker@adacore.com, gdb@sourceware.org, ludo@gnu.org
> > >
> > > 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))
> >
> > That's again because your defaults are set to interpret this as
> > something other than UTF-8.
>
> They're not. This is on a standard emacs 21.4 and there is *nothing*
> in my .emacs that doesn't touch anything related to 'coding'.
In which case Emacs uses your locale to set up things. I'm guessing
that your locale is not a UTF-8 one, probably Latin-1 or Latin-9?
> > > 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.
> >
> > And I'm arguing that adding the coding cookie will cause this to be
> > displayed properly in Emacs.
>
> Obviously that is not true on all systems.
"Obviously"? You mean, Ludo's name is not displayed correctly on your
system even after the `coding' cookie was added?
next prev parent reply other threads:[~2009-01-07 4:19 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
2009-01-06 21:59 ` Eli Zaretskii
2009-01-06 22:49 ` Mark Kettenis
2009-01-07 4:19 ` Eli Zaretskii [this message]
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=u7i57lpe8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=ludo@gnu.org \
--cc=mark.kettenis@xs4all.nl \
/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