To propagate the idea further, why not have proper message catalogs,
and that way translations. Instead of:
> printk(KERN_WARN "This driver is messed up!\n");
There would be:
printk(KERN_WARN "1234-6789 this driver is messed up!\n")
In the old days of big iron beasts, there used to be multivolume
binders full of system messages, and their explanations.
Searching went thru those "1234-5678" strings.
There were sets of those manuals in a number of customer languages.
...
> I'm looking for a possible uniform design to make this happen, short of
> adding a complete machine translation module to the kernel. :) Userland
> internationalization support is already provided(I haven't personally
> used other languages besides English, but I've seen the options), but a
> kernel module or printk addition that handles localized kernel messages
> seems reasonable.
Compiled in strings take up kernel space, which has better uses.
Even those code-labels take up space. If not much in kernel (in
form of e.g. 32 bit integers ?) then at least in the dmesg buffer.
> Thoughts, comments?
>
> Regards,
> Frank
/Matti Aarnio
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/