For the translations, the best thing to keep as much as we can is to use the msgmerge utility - I guess you are already using this when integrating updates from Launchpad? We could do something like the following:
1. reconfigure our script for xgettext to collect all world-related strings into one .pot catalog, e.g. worlds/worlds.pot. 2. Grab the current Launchpad translations 3. Use msgmerge to merge the 4 old worlds into one, creating a new po file in the process. Something like this: msgmerge -o worlds/de.po world-blackland/de.po worlds/worlds.pot msgmerge -o worlds/de.po world-desert/de.po worlds/worlds.pot msgmerge -o worlds/de.po world-greenland/de.po worlds/worlds.pot msgmerge -o worlds/de.po world-winterland/de.po worlds/worlds.pot I think it would be a good idea to test this with German, because more than one of us speak the language, and we could open the resulting worlds/de.po and have a look if everything's OK. -- https://code.launchpad.net/~widelands-dev/widelands/one_world/+merge/222708 Your team Widelands Developers is requested to review the proposed merge of lp:~widelands-dev/widelands/one_world into lp:widelands. _______________________________________________ Mailing list: https://launchpad.net/~widelands-dev Post to : widelands-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~widelands-dev More help : https://help.launchpad.net/ListHelp
