> Me:
>> How about this:
>> There are several files, lang.err.msg (one for each language,
obviously),
>> each containing somthing like this:
>> english.err.msg:
>> #define ERROR_MSG_READ_ONLY "read-only"
>> #define ERROR_MSG_REMOUNT "Error, remounting "
>
>NO!
>please.
>This would make adding new printks much harder.
>
Not really:
1) Make up an ERROR_MSG_... name that makes sense for you.
2) Add it to english.err.msg
4) Add "#include <error_messages.h>" to above your printk (placement dosn't
matter, since the .h is just a bunch of #defines) (the .h has to be
semi-dynamicly created, but that's not the business of a mear printk user
<G>) (Most files will end up allredy having this)
5) Do a printk with the ERROR_MSG_ that you just created.
NOT 6) You don't need to put any translations in the other lang.err.msg
files since the English is included as default, and others will translate
the messages into their language (if you want to translate into any
languages you know, it would be a Good Thing).
Or, if you wanted to, you could simply use printk as it exists now, but
then it will be harder to add translations later (OK for can't happens and
debuging messages that will only occur to those doing Funky Stuff.)
-=- James Mastros