One thought I just had was why the message catalog should be in the database at all.
I can see how a web-based interface for translating is nice, and that's easier to write if you have things in the database.
But as far as I can see, we still need it as a flat text file for a lot of things (distributing language packs, handing them off to off-site translators who can just go through and translate it all, etc.), and having to synchronize DB and flat file is annoying.
After all, we're slurping the whole thing into RAM, anyway, at server startup.
Any thoughts?
