[lkml]   [1997]   [Jan]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Jive -> Kernel (International Linux)

On Wed, 15 Jan 1997, Adam D. Bradley wrote:
[snip - international kernel messages are good]
> This isn't a bad idea, really. We could do it as a compile thing, or
> maybe even at run-time with modules...(hmm)...
> For compiled-in language support:
> In each directory, create a file "printk_strings.h" like this:
> #endif
> #define FD_DISK_CHANGE_DETECTED "Disk Change Detected"
> #define FD_DISK_SCREWED "Your Disk is Screwed"
> /* etc etc etc */
> #define FD_DISK_CHANGE_DETECTED "Yo dis be diff'd"
> #define FD_DISK_SCREWED "Yo disk be like yo mama!"
> /* etc etc etc */
> #endif

But that would require that all possible kernel messages are available in
every language. It would probably be better to have a automagically
created message database that could default a given message to English if
it's not available in Timbucktooise.

IE a program that is run at compile time that would create prink_strings.h
like this:

#define FD_DISK_CHANGE_DETECTED "Yo dis be diff'd"
#define FD_DISK_SCREWED "Your disk is screwed" /* noone has translated
that message yet */

> To get more clever, we could do it at run-time. Have a universal "text
> constants heap" somewhere in the kernel/ directory, say a new file
> called "language.c":
[snip details]

I don't know how much kernel bloat that'd cause, but I think that
defaulting to English in the absence of a translation for a given string
might be harder to do well.

Mike Bristow:
The best UK M:tG tourney page:
My public PGP key:

 \ /
  Last update: 2005-03-22 13:38    [W:0.032 / U:1.076 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site