Re: [Widelands-dev] [Merge] lp:~widelands-dev/widelands/one_world into lp:widelands

2014-06-10 Thread SirVer
Review: Needs Information I'd rather not do the juggling with the translations in this branch/merge request. I did the test merge of all de.po of the old worlds into a new one in a new branch and pushed for inspection: https://code.launchpad.net/~widelands-dev/widelands/one_world_translations

Re: [Widelands-dev] [Merge] lp:~widelands-dev/widelands/one_world into lp:widelands

2014-06-10 Thread GunChleoc
Review: Needs Fixing merging world catalogues Commented here: https://code.launchpad.net/~widelands-dev/widelands/one_world/+merge/222708/comments/533683 Set to "Needs fixing", because we still need to work this out and test ;) -- https://code.launchpad.net/~widelands-dev/widelands/one_world/+m

Re: [Widelands-dev] [Merge] lp:~widelands-dev/widelands/one_world into lp:widelands

2014-06-10 Thread GunChleoc
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

[Widelands-dev] [Merge] lp:~widelands-dev/widelands/one_world into lp:widelands

2014-06-10 Thread SirVer
The proposal to merge lp:~widelands-dev/widelands/one_world into lp:widelands has been updated. Description changed to: This merges all worlds into one, converts its configuration to Lua, adds the compatibility layer to map loading needed for this. This also regresses some issues: - Bug 13286