From: Pete Zaitcev <zaitcev@redhat.com>
To: linux-kernel@vger.kernel.org, zaitcev@redhat.com
Subject: Alphabet of kernel source
Date: Wed, 23 Jun 2004 14:06:28 -0700 [thread overview]
Message-ID: <20040623140628.3f1abfe9@lembas.zaitcev.lan> (raw)
Guys,
I have a silly question, for which I am unable to google out the answer
so far. Do we have a Linus' decree on the charset and encoding of the
kernel source?
I had a funny situation recently... I prefer non-MIME attachements
for two reasons: a) I grab parts of the header and fold them into
patch and b) it is easier to quote fragments of the patch with clients
I tried (mutt and sylpheed). Admittendly, a different MUA software may
change these habits, but please bear with me here. So, someone sent
me a patch which included a context line with MODULE_AUTHOR() with
an accented name, which the author entered in ISO-8859-1 (he was German).
I replied, but my mail agent recoded the reply as UTF-8. The author
agreed to my patch, and copied my reply, sent to me. Everything was
perfectly readable at this point, but the patch rejected. Because
I use Russian and Japanese simultaneously, all utilities run with UTF-8
my boxes, so it took me a moment to do "LANG=C vi" and find the problem.
Anyhow, long story short, this got me thinking... What is the charset
and the encoding of the actual source? I saw quite a discussion about
the filenames, but this is different. I am sorry if this was discussed
previously.
-- Pete
next reply other threads:[~2004-06-23 21:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 21:06 Pete Zaitcev [this message]
2004-06-23 21:46 ` David Eger
2004-06-23 22:18 ` Kalin KOZHUHAROV
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=20040623140628.3f1abfe9@lembas.zaitcev.lan \
--to=zaitcev@redhat.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
all inboxes | Powered by JetHome®