From: mru@kth.se (Måns Rullgård)
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] UTF-8ifying the kernel source
Date: Thu, 04 Mar 2004 11:32:03 +0100 [thread overview]
Message-ID: <yw1xsmgogaxo.fsf@kth.se> (raw)
In-Reply-To: E1Aypx5-0000mb-5u@rhn.tartu-labor
Meelis Roos <mroos@linux.ee> writes:
> DE> Here you find the first of several patches to convert the kernel
> DE> source from ISO Latin-1 to UTF-8. I'm working on the files that didn't
> DE> auto-convert easily; comments welcome ;-)
>
> Why? It's just easier to use plain 8-bit text files today (with editors,
> code tools etc) and accept the limitations of it that to overcome the
> limitations by forcing people to UTF-8 editors & other tools.
How do you propose that editors should know which encoding a file
uses? The trend seems to be moving towards UTF-8 for everything, so
the kernel might as well do it too.
--
Måns Rullgård
mru@kth.se
next prev parent reply other threads:[~2004-03-04 10:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-04 10:05 [PATCH] UTF-8ifying the kernel source David Eger
2004-03-04 10:19 ` Meelis Roos
2004-03-04 10:32 ` Måns Rullgård [this message]
2004-03-04 21:51 ` Alex Belits
2004-03-05 8:26 ` Miles Bader
2004-03-05 20:01 ` H. Peter Anvin
2004-03-05 21:00 ` Mike Fedyk
2004-03-05 21:02 ` H. Peter Anvin
2004-03-05 21:17 ` Måns Rullgård
2004-03-05 21:26 ` Charles Cazabon
2004-03-05 21:20 ` David Eger
2004-03-05 23:24 ` David Eger
2004-03-05 23:33 ` H. Peter Anvin
2004-03-06 11:08 ` Xavier Bestel
2004-03-06 11:14 ` Måns Rullgård
2004-03-09 0:30 ` H. Peter Anvin
2004-03-09 9:49 ` Xavier Bestel
2004-03-06 13:33 ` Other bizarre thing... backspaces? David Eger
2004-03-06 14:04 ` Måns Rullgård
2004-03-14 16:25 ` Petr Baudis
2004-03-09 12:19 ` [PATCH] UTF-8ifying the kernel source Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2004-03-05 13:21 paolo ciarrocchi
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=yw1xsmgogaxo.fsf@kth.se \
--to=mru@kth.se \
--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