Jens> On Fri, Dec 04, 1998 at 09:53:08AM +0100, Jes Sorensen wrote:
>> I really can't see the point here, all the commands on the system
>> are in english anyway, C is using English. If you don't understand
>> the basic English terms used by a computer, how can you adminitrate
>> them.
Jens> Simple. Get an OS that gives you the messages in the language
Jens> you know best and understand best. I know of quite a couple
Jens> friends whose only reasons for not trying out something other
Jens> than Windows is that in Windows, everything is in their native
Jens> tongue (German, in my example). They are too lazy to learn
Jens> English just to use another OS. And they ARE in fact missing
Jens> something.
Tough luck for them. What are they doing when NT gives a BSOD or has
that been translated as well? What do these people do when
programming, do they run a special version of C where all the keywords
have been translated into another language?
>>> Once messages permeate back to this list, they can be converted
>>> back to English just as the original message was converted
>>> originally to the native language.
>> Sorry but I am not going to waste my time trying to decode error
>> messages from my own code just because someone wants to print it in
>> a different language.
Jens> You don't have to. Please think about the above message number
Jens> idea and THEN reply (if necessary).
I've thought about that approach and I can see why it will fail - who
is going to assign the system error codes? I am not willing to have to
wait for someone to assign me that sort of numbers when I am hacking
the kernel. Besides having all these translations inside the kernel is
going to be bloated as hell.
Jens> Is it a big problem adding a kind of language definitions (and
Jens> perhaps a utility that interactively creates these files) AND an
Jens> unique(!) error number scheme to avoid miscromprehension for bug
Jens> reports? Something like
Yes it is, as a kernel developer I want the most convenient way for me
to develop the code.
Jes
-
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/