Mirror of the gdb mailing list
 help / color / mirror / Atom feed
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: Sat, 03 Jan 2009 23:56:00 -0000	[thread overview]
Message-ID: <200901032356.n03NuSbX005424@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <uzli8much.fsf@gnu.org> (message from Eli Zaretskii on Sat, 03 	Jan 2009 14:45:18 +0200)

> Date: Sat, 03 Jan 2009 14:45:18 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> 
> > 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?

Sure, the OpenBSD system console defenitely isn't UTF-8 aware, and as
far as I can tell the xterm's on OpenBSD don't have UTF-8 encoding
turned on by default either.

> > 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.  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.

> > 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.)

Well, their ancestors didn't have them ;)

Seriously though.  This is not worth fighting about.  I stated my
opinion.  I'll get back under my rock.


  reply	other threads:[~2009-01-03 23:56 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 [this message]
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=200901032356.n03NuSbX005424@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