> > > Dunno. Maybe Linus should start putting code and documentation written in
> > > .fi, others in .cz, .es, .de, etc. The point is, I cant help this guy it I
> > > dont know german. Or japanese, or whatever. We have a more or less common
> > > language. Why not stick to it?
> >
> > We don't and the respective "One language fits all" attitude is pissing of
> > quite a number of people. Remember that people on this list tend do be
> > higher school education than the average person on this planet. If Linux
> > wants to succeed beyond a certain limit it will have to become multiligual
> > despite all the technical problems this will result in. This will be one
> > of the key points to ``world domination'' just as important as apps.
> >
> > Ralf
> What about a numeric code to go with the error? Then we could just look up
> the error if we can;t read the laguage ...
It will be ugly but I consider it the solution for the kernel. As with for
example in SMTP messages one language will have to be in the kernel and
that's going to be English until the Chinese send a billion kernel
hackers ;-) klogd can then be used to parse and translate the messages.
/proc is more problematic, parts are considered to be human readable.
Ralf
-
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/