2004-01-02 01:43:31

by Xan

[permalink] [raw]
Subject: Re: i18n for kernel 2.7.x?

Dimecres 31 Desembre 2003 17:04, en/na John Bradford (<John Bradford
<[email protected]>>) 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?


2004-01-02 02:46:25

by Toplica Tanasković

[permalink] [raw]
Subject: Re: i18n for kernel 2.7.x?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Xan wrote:
> Dimecres 31 Desembre 2003 17:04, en/na John Bradford (<John Bradford
>
> <[email protected]>>) 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?

Agreed. KDE end GNOME knowledge can be used for help if needed...
- --
Regards,
Toplica Tanaskovic
Coordinator of Serbian KDE Translation Team
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/9NuotKJqksC6c0sRAjpLAKC1RxgvZM8RjjUZ8ixHoLPoBY/WkACeJupf
Vv+DUI8Vrg3ZXlBPgdzxN7k=
=SzUP
-----END PGP SIGNATURE-----

2004-01-02 02:39:28

by Valdis Klētnieks

[permalink] [raw]
Subject: Re: i18n for kernel 2.7.x?

On Fri, 02 Jan 2004 01:53:58 +0100, Xan said:

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

Oh, give me a <bleep>ing break, already.

We demonstrably have *enough* trouble keeping the English-only contents of the
Documentation/ directory in sync with the source. What do you propose to do if/
when some kernel change requires a document update, and we can't find somebody
who is qualified to translate to Swahili, or one of the Baltic languages(*),
and so on? Pretty soon, you have 15 or 20 slowly diverging versions due to
missed updates and the like.

As far as translating the COPYING file, I think you need to see what the FSF
thinks of translating the GPL into other languages:

http://www.fsf.org/licenses/licenses.html

(Bottom line - English is canonical, and the others are basically considered
study aids for the English-challenged).

(*) Don't look at me - although I went bughunting in the cpufreq code, and have
more relatives in Riga than I do in the US, and my Latvian is quite sufficient
to deal with a newspaper, dinner conversation, or television programming, I'd
hate to be the guy trying to understand my attempt to explain the cpufreq code
in Latvian.. ;)


Attachments:
(No filename) (226.00 B)

2004-01-02 15:27:52

by grundig

[permalink] [raw]
Subject: Re: i18n for kernel 2.7.x?

El Fri, 2 Jan 2004 01:53:58 +0100 Xan <[email protected]> escribi?:

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

People are already doing this for the help entries of the configure process:
http://es.tldp.org/NuLies/web/index.html (in Spanish). This is just a patch
over the kernel. The 2.6 split of the configure files will help to coordinate
the efforts, it'd not be very difficult to include it as a "extra" package
in normal distributions. It's not complete of course...