#include <infodrom.style>
#include <projects.style>

<projectpg project="manpages-de" maxcontrib=5 title="Anonymous CVS-Access">

<h3 class=bar>Why don't we internationalise kernel messages?</h3>

<p>The question arose a couple of times in the past, both in private
mail to Joey and on the <a
href="http://www.tux.org/lkml/">linux-kernel</a> mailing list.  Even
though the answer seems to be quite obvious to those of use who are
deep into the kernel and it's development model, it may not be that
obvious for those who don't understand english and seek help
understanding messages.

<p>There are several reasons why this should not be done:

<ul>

<li> It would bloat the kernel sources.  The kernel is already huge
     and would grow up insanely if all messages were to be stored in
     100+ languages as well.
<li> It would drastically increase the cost of maintaining the
     kernel message database.
<li> Kernel message output would slow down, since each time a message
     has to be spit out the kernel would have to determine which
     language to use first.
<li> English is the language in which the kernel sources are
     written, and thus is the language in which kernel
     messages are written.  Developers cannot be expected to
     provide translations.
<li> Bug reports should be submitted in English, and that
     includes kernel messages.  If kernel messages were to be
     output in some other language, most developers could not
     help in fixing bugs.
<li> Translation can be performed in user-space, there is no
     need to change the kernel.  It's not that kernel messages are
     overly interesting for the averate user.  They should use
     user-space tools like ifconfig etc. instead.
<li> Finally, it will not be done.  No core developer supports this.
     Neither does Linus.  Don't even ask.
</ul>

</projectpg>

# Local variables:
# mode: indented-text
# end: