public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Xan <DXpublica@telefonica.net>
To: linux-kernel@vger.kernel.org
Subject: i18n for kernel 2.7.x?
Date: Wed, 31 Dec 2003 13:32:15 +0100	[thread overview]
Message-ID: <200312311332.15422.DXpublica@telefonica.net> (raw)

Hi,

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)?

I think that internationalization is a remarkable thing of a kernel of
any operating system. It makes the kernel project more international
(in the sense that there is no privileged language) and make that more
people feel envolved in this (because these people see the kernel less far
than before, because it "speaks" their language). And (perhaps indirectly)
it makes that more people detect more bugs: if I'm a newbee and I see
"This is a bug [...] EIP: ....", in normal circumstances (and more if I
don't know english), I don't know what can I do [If the kernel "says" the
bug in rumanian for example, then I know that is a kernel bug and, maybe,
I say it to my friend that know english...]

I believe that it could be done in the future releases of kernel (I don't
believe that it could be done in the present series (2.6) because I
believe that it implies a little bit of work!).

I'm not a kernel guru so I don't know what is necessary to do for i18n of
the kernel, but I think that it's necessary to do:

1) Make a module, M, for display all the message that now kernel displays
directly. So the core of the kernel and all the other modules send the
message to display to M and then M displays this message in the selected
language (selected in the compilation of kernel). The default language
were english as now, for example, because the kernel developers are
majorty of english speakers.

2) Translate the documentation. That is,
	a) Documentation/ directory of the kernel
	b) README file and other ./ files (as COPYRIGHT...)
		Optionally, we could say in the translated files that the "official"
		translate is the english translate (for legal purposes...)
	c) Translate the web page of the kernel (www.kernel.org) for that we
	could display the language that we selected in this page (as
	www.debian.org do).


This is all what I want to communicate to you and I _hope_ that you like
it.

Regards and happy new year,
Xan.

PS: Please don't email-me. Discusion about it in group. Thanks.


             reply	other threads:[~2003-12-31 12:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-31 12:32 Xan [this message]
2003-12-31 12:45 ` i18n for kernel 2.7.x? 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
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=200312311332.15422.DXpublica@telefonica.net \
    --to=dxpublica@telefonica.net \
    --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