That's a reasonable set of advantages, I suppose. Aside from the compression/indexing one, all can be automated in other ways, though. I store translations in a database that is accessed through a little program I put together, and it keeps track of what has or has not been translated for each language and uses the default text if no translation has been made. It also writes out the actual language file with the click of a button.
Quote:
|
And if a text hasn't been translated the original text is shown.
|
If I understand your first post correctly, don't you still have to go into each of the language files and add or modify the msgid/msgstr lines? That would seem to still require a lot of manual legwork, especially for something with a large number of languages. With my method, a variable only needs to be added to the database once. The only repetitive work is outputting each language file and saving it over the old version, which could also be automated if I ever wanted to bother.
Dan
Hybrid Mode
