Re: Internationalizing Linux

Jon K Hellan (
Fri, 4 Dec 1998 12:39:19 +0100 (MET)

> > This causes a maintenance headache. With this scheme,
> > whenever a new printk gets a macro-ized, you will have
> > to make sure the entries are correctly added to the 'n'
> > language specific headers, even if they are inserted in English.
> [...]
> It doesn't have to be like that. Consider using one file
> kmsg.h included by anything that needs the message #define's
> Now this file contains two lines only:
> #include <english.h> /* Because English is the development language for Linux
> */
> #include <norwegian.h> /* Or whatever you may want instead */

*If* this is done (I don't like the idea), messages must include a
language independent identifier (e.g. E1004, W2012, ... Only thus can
a support provider who doesn't understand swahili interpret the message.


Jon K. Hellan                        
Div. of Telematics, Norw. U. of Science & Technology, Trondheim - Norway

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to Please read the FAQ at