kernel support for non-english user messages
Quoted 11 lines
Quoted 9 lines
How about changing the way printk works, so that instead of
combining the format string, it just "prints" its args:
printk("%s: name %p is %d\n", name, ptr, val);results in the following in the kernel buffer:
"%s: name %p is %d\n", "stringval",
0x4790243, 44Debugging a non-klogd enabled kernel would be a pain
Why? Shouldn't it be easy to fix dmesg so it unmangles the output?
The real problem I see is that this approach doesn't make it any
easier to translate the messages.
Maybe someone should just try to write a Babelfish-like thing that
takes English kernel-speak and translates it as best it can? It would at least be amusing to read the output. :)
--
Chuck
I am not a number!
Quoted 8 lines · Chuck Ebbert
Quoted 8 lines
Quoted 8 lines
How about changing the way printk works, so that instead of
combining the format string, it just "prints" its args:
printk("%s: name %p is %d\n", name, ptr, val);results in the following in the kernel buffer:
"%s: name %p is %d\n", "stringval",
0x4790243, 44
[...]
Quoted 2 lines
The real problem I see is that this approach doesn't make it any easier to translate the messages.
If you habe the above, you could use/copy/reuse gettext() since the format string is used a key/hash/unique id for the translation.
Bernd
Signature · 4 lines
Bernd Petrovitsch Email : [email protected] g.a.m.s gmbh Fax : +43 1 205255-900 Prinz-Eugen-Straße 8 A-1040 Vienna/Austria/Europe LUGA : http://www.luga.at