The proposal to merge lp:~widelands-dev/widelands/glossary_checks into lp:widelands has been updated.
Description changed to: After the British English fiasco in Build 19, I decided it would be good to have some glossary checks for translations. We are using this kind of check at my workplace, and they help with keeping consistency on big projects. Downloading the glossary from Transifex can't be automated, so we have to download it manually each time before we do the checks. So, I decided against committing it to the ode base - we won't want to accidentally check against an outdated glossary. Translators can hack the glossary's comment fields to provide inflected word forms, so in the long run, it won't annoy the translators with false positive hits. For example, for "worker" = "Arbeiter", "workers" = "Arbeitern" can pass the check if a translator has added the relevant data. I am also using the Hunspell stem function to reduce the noise. This is slow, but any entry that a translator doesn't have to look at needlessly is a good entry. These check will be a service for the translation teams and NOT mandatory - we can't require of volunteers to go through them. Some of the translators gladly snapped up my last round of validations though, so some will like using this. For more details, see: https://code.launchpad.net/~widelands-dev/widelands/glossary_checks/+merge/312430 -- Your team Widelands Developers is requested to review the proposed merge of lp:~widelands-dev/widelands/glossary_checks into lp:widelands. _______________________________________________ Mailing list: https://launchpad.net/~widelands-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~widelands-dev More help : https://help.launchpad.net/ListHelp
