I do agree. Another issue is that quite often the actual line to be
printed is likely fairly short, and often in an error path (so it's
indented and in an inconvenient place), but the explanation - even for a
_single_ language - may well be pretty involved and long.
Which is why I think for something like this, it really needs to be
entirely outside. Because putting it inside the kernel simply isn't going
to result in anything really useful. Either it can be close to the message
and be updated reasonably (never mind that if we really do support
multiple languages, that's not going to happen anyway, even if it's
close), or it's going to be somewhere else and not be updated when changes
happen - and then it migth as well be a separate project.
The 'separate project' is especially appropriate since any parsing won't
be done by the kernel anyway, but by some ksyslog thing.
Linus
--
