Whatever you do, keep english messages in the kernel. Perhaps place a
(secondary) error code that can be decoded if necessary (and if the
resources are available). It's better to have an english error message that
you may have difficulty translating than an error code. An error code would
require another working computer, web browser, etc,etc...to decipher. Much
more difficult. If you had these resources you could use
babelfish.altavista.com to translate the english text anyway!
I don't know if you guys have seen this (appeared on /. in November), but
there's a project to create a "Universal Network Language" that may help
greatly in this arena:
http://www.news.com/News/Item/Textonly/0,25,29199,00.html
I wish I had further references on it...it looks very interesting...
-- Bob
Bob McElrath (mcelrath@draal.physics.wisc.edu) Univ. of Wisconsin at Madison
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/