1. We must have all kinds of translations if we wouldn't like to scare
non-English users and make Linux non-hackers-only system.
Of course newbies won't understand what kernel says even in their own
language but it is not necessary - getting a clue in this case means
setting up some ways of message->action translation in their minds. It
doesn't have much to do with understanding. Have you tried MS-Windows? I
know a lot of messages in them which I do not understand or are completely
misleading but I learned what should I do when I see them. And for those
who don't know English seeing them in their native language helps to
remember messages.
2. English-only hackers should still be able to understand all the
messages. Using messages identifiers is not enough, although it may be
useful anyway. The only way is to display messages in both languages,
or to make it configuration option at least (to configure pl+en or
en or even pl+en+de?).
3. The way it should be done should try to conform as much as possible
to GNU Translation Project and gettext libraries.
4. The translation should be available as compiled-in and as a standalone
kernel module. It can't be a user space program because it won't work
during the kernel startup.
R.
-- Rafal Maszkowski rzm@torun.pdi.net http://www.torun.pdi.net/~rzm Opinia publiczna powinna byc zaalarmowana swoim nieistnieniem - St. J. Lec