From: Kalin KOZHUHAROV <kalin@ThinRope.net>
To: David Eger <eger@havoc.gtf.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Alphabet of kernel source
Date: Thu, 24 Jun 2004 07:18:41 +0900 [thread overview]
Message-ID: <40DA01C1.2030102@ThinRope.net> (raw)
In-Reply-To: <20040623214653.GA29728@havoc.gtf.org>
David Eger wrote:
> I started a thread a while ago (2.6.3/2.6.4) where I submitted some
> patches to UTF-8ifying the kernel sources. Basically, most of the
> kernel is ASCII (98.4% of the files). The rest are mostly ISO-Latin-1,
> with the rare bit of Japanese (in a couple of charsets) and some just
> random bytes in some of the Documentation/...
The "problem" is contributor names, although having everything in plain ASCII is resonable, I guess.
> http://www.yak.net/random/linux-2.6.4-utf8-cleanup-auto.diff
A lot of names and some art supposed to be ASCII.
> http://www.yak.net/random/linux-2.6.4-utf8-cleanup-cstrings2utf8.diff
Some degree symbols and microseconds... and names.
I remember having problems with lm-sensors trying to print degrees, how did they fight the problem?
> http://www.yak.net/random/linux-2.6.4-utf8-cleanup-jp.diff
Ok, this Japanese is only in the comments.
I can translate that in no time and fix this diff.
WTF is arch/v850/ ?
I guess you had some kind of script, can you try it on vanilla 2.6.7, plesae, and post results.
> http://www.yak.net/random/linux-2.6.4-utf8-cleanup-wrong.diff
There are a few microseconds written properly, but may commonly by typed as us, or just don't use abbr.
> It's sorta difficult to do non-ASCII patches over email because
> the kernel developers like reading their mail in mutt, and don't
> like attachments (the only sane ways to send non 7-bit clean data:
> 8-bit MIME: tagged and bagged or uuencoded)
>
> Further, you confuse the hell out of vi if you have any trash (8bit data
> in another charset) in a file that's supposed to be UTF-8. i.e. don't
> think you're going to be able to look at a charset changing patch in
> anything.
Totally agree, although I use Mozilla Mail (and sometimes mutt).
Kalin.
--
||///_ o *****************************
||//'_/> WWW: http://ThinRope.net/
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
next prev parent reply other threads:[~2004-06-23 22:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 21:06 Alphabet of kernel source Pete Zaitcev
2004-06-23 21:46 ` David Eger
2004-06-23 22:18 ` Kalin KOZHUHAROV [this message]
2004-06-24 6:16 ` David Eger
2004-06-27 5:48 ` [PATCH] Translate Japanese comments in arch/v850 ( was: Alphabet of kernel source) Kalin KOZHUHAROV
2004-06-23 21:58 ` Alphabet of kernel source Andries Brouwer
2004-06-24 11:06 ` Richard B. Johnson
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=40DA01C1.2030102@ThinRope.net \
--to=kalin@thinrope.net \
--cc=eger@havoc.gtf.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.