> And as for the actual explanations: either they need to be totally outside
> the kernel (in a project of their own), or they'd need to be "kernel-doc"
> style things that are _in_ the source code. Not in Documentation/. Not
> separate from the printk() that they are associated with.
You really don't want 32 languages in mixed left/right rendering with
multiple fonts in your kernel source. At least not with most editing and
viewing tools....
User space uses message catalogues and has tools for maintaining them
which make using any other format somewhat dumb. They extract strings
using _("hello") type wrappers to identify what are translatable strings
so if the kernel source has _() macros all the tooling just works and can
live outside and way from the kernel.
Just needs _() to do the right thing compiled into the kernel and a
printk formatting to do the right thing with the result. In truth you
don't even need a hash in printk just the ability to make it produce
either
"Hello my name is 'fred3'"
and something like
"Hello my name is '%s%d'\0Fred\0\000\000\000\003"
The kernel contains the English which should be a pretty passable hash.
Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-s390" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
