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: Sat, 03 Jan 2009 12:45:00 -0000 [thread overview]
Message-ID: <uzli8much.fsf@gnu.org> (raw)
In-Reply-To: <200901031022.n03AMq5c027637@brahms.sibelius.xs4all.nl>
> Date: Sat, 3 Jan 2009 11:22:53 +0100 (CET)
> From: Mark Kettenis <mark.kettenis@xs4all.nl>
> CC: brobecker@adacore.com, gdb@sourceware.org, ludo@gnu.org
>
> Well, I disagree. I think it was a mistake. UTF-8 support is not
> universally available.
Any specific examples?
> 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.
> I think we should keep our source files as 7-bit ASCII (with the
> possible exception of the files maintained by the translation
> teams), Developers should use a transliteration for their names,
> just like all deveopers from countries in east-asia or the former
> (current?) Russian empire seem to do.
I doubt if you can get that agreed to by many people who live in the
Latin locales. (But if you succeed, I won't mind going back to ASCII,
of course.)
Also note that leaving the encoding unspecified will almost always
produce incorrect display if someone uses non-ASCII characters, while
specifying the encoding at least does TRT in Emacs.
next prev parent reply other threads:[~2009-01-03 12:45 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 [this message]
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
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=uzli8much.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