> Ack! Worst problem:
> (1) Strings have to be _recognized_ and then substituted. Have to do a
> bunch of strstr()'s over a massive string table. Alternately, you could
Tough. You want international language support, you pay the price in
efficiency.
> module is loaded; there's no allowance for "quick+dirty" dumps, eg OOPS
> data which we don't have/want to think about translating/formatting.
Oops data is not performance critical. IMHO, no printk()s are -- if
they're happening so often that you need to worry about the time to
translate, then you almost certainly have some other problem.
P.