From: Xan <DXpublica@telefonica.net>
To: John Bradford <john@grabjohn.com>, Matthias Schniedermeyer <ms@citd.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: i18n for kernel 2.7.x?
Date: Fri, 2 Jan 2004 01:53:58 +0100 [thread overview]
Message-ID: <200401020153.59030.DXpublica@telefonica.net> (raw)
In-Reply-To: <200312311604.hBVG4ruS000274@81-2-122-30.bradfords.org.uk>
Dimecres 31 Desembre 2003 17:04, en/na John Bradford (<John Bradford
<john@grabjohn.com>>) va escriure:
> > > > Just a thing: why not internationalization of kernel. That is, why
> > > > not that the kernel could display error or debug messages in
> > > > different languages (for example)?
> > >
> > > This is a FAQ.
> > >
> > > http://www.kernel.org/pub/linux/docs/lkml/#s9-16
> > >
> > > So it should be better to end this before it begins (again).
> >
> > It appears that you (kernel developers) have panic about it. Wow!. What a
> > contundent message!. It appears as a tabu topic.
>
> It is not a tabu topic at all, but as with all FAQs, unless you have
> solutions to the problems which have already been raised, there is
> little point in discussing them again. Read through the archives, and
> you will find responses to almost all of the points you mentioned.
>
> John.
Well... if (all of) you think that....
But, what happens with Documentation/ directory and README, COPYRIGHT, ... and
WEB PAGE of the kernel?
It's NOT so technically hard to do. Why not so?
next prev parent reply other threads:[~2004-01-02 1:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-31 12:32 i18n for kernel 2.7.x? Xan
2003-12-31 12:45 ` Tomas Szepe
2003-12-31 12:51 ` Matthias Schniedermeyer
2003-12-31 15:25 ` Xan
2003-12-31 16:00 ` Matthias Schniedermeyer
2003-12-31 16:04 ` John Bradford
2004-01-02 0:53 ` Xan [this message]
2004-01-02 2:39 ` Valdis.Kletnieks
2004-01-02 2:47 ` Toplica Tanasković
2004-01-02 15:27 ` Diego Calleja
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=200401020153.59030.DXpublica@telefonica.net \
--to=dxpublica@telefonica.net \
--cc=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ms@citd.de \
/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