From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Brown, Len" <len.brown@intel.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
"J.A. Magallon" <jamagallon@able.es>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: RE: [patch] 2.4.x ACPI updates
Date: 19 Aug 2003 14:30:39 +0100 [thread overview]
Message-ID: <1061299838.30566.38.camel@dhcp23.swansea.linux.org.uk> (raw)
In-Reply-To: <BF1FE1855350A0479097B3A0D2A80EE009FC79@hdsmsx402.hd.intel.com>
On Maw, 2003-08-19 at 03:04, Brown, Len wrote:
> The ISO_8859_1 acute accent, u with diaeresis, and registered sign, have been in Config.info since Feb 2002.
>
> Andy's tools seem to have extended them to 16-bit characters during a merge.
> A "minor gaff"? Okay, I guess that's fair. He promises that he
> doesn't know how to type a latin capital A with a circumflex on his
> keyboard;-).
8859-1 is wrong by all accounts even though the file uses it for
historical reasons. If anything his change is a good one since UTF-8
actually has all the accents for even European names (ñ, ŵ , ï etc) many
of which are missing from 8859-1.
For kernel messages we use 7bit ascii and fixed the 8bit oddments to
keep sysklogd happy, for Configure.help it is down picking something. In
the 2.5 case I'd definitely vote for UTF-8 since the configuration tools
are using libraries that grok UTF-8 properly. For 2.4 we might want to
be more conservative and use 7bit since fixing the tools is a PITA and
its wrong in most of the world to emit 8859-1 arbitarily and its wrong
in the USA to emit UTF-8 arbitarily since lots of US folks still use
8859-*
next prev parent reply other threads:[~2003-08-19 16:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-19 2:04 [patch] 2.4.x ACPI updates Brown, Len
2003-08-19 2:22 ` Jeff Garzik
2003-08-19 13:30 ` Alan Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-23 21:05 Brown, Len
2003-08-23 21:30 ` Marcelo Tosatti
[not found] <Pine.LNX.4.44.0308230015440.14227-100000@logos.cnet>
2003-08-23 17:26 ` Marcelo Tosatti
2003-08-23 2:15 Brown, Len
2003-08-22 2:49 Brown, Len
2003-08-20 0:04 Brown, Len
2003-08-20 18:15 ` Marcelo Tosatti
2003-08-18 19:09 Jeff Garzik
2003-08-18 20:55 ` J.A. Magallon
2003-08-18 21:10 ` Jeff Garzik
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=1061299838.30566.38.camel@dhcp23.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jamagallon@able.es \
--cc=jgarzik@pobox.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).