Not extraordinarily clear, though, if you don't have a language module
loaded (or a language-specific klogd running); the current scheme,
pit of seething anglocentrism that it is, at least has the advantage
of being readable to one group of non-necessarily technically competent
readers.
How about adding a code to the printks, like:
printk(SEVERITY CODE "english text", arguments);
| |
| |
bog-standard |
<number> |
|
not quite so bog-standard
{number}
if a language module is loaded (or a switch is set for a
language-specific klogd), it will either look for the
native message for the offending printk, then use that
as the format for the printf, or pass the {number} out
to klogd instead of the "english text" part.
The trivial solution, which is to have the language module
consist of printf format strings:
{1} -> "Console: %d point font, %d scans\n"
might fall over dead if there are languages where the order of
the arguments need to change for clarity. A possible extension
would be, I guess, to use
{1} -> "Console &1%d point font, &2%d scans\n"
And subvert & as a argument specifier.
____
david parsons \bi/ I have a clever proof for this, but don't have
\/ enough room in /tmp to add it to this message.