translate
MT engines don't always map language codes to Pootle language codes
When using the Google Translate machine translation option, the Google button does not always show up. This has to do with the existence of the Pootle language at Google.
Example: Pootle uses 'nb' for Norwegian Bokmål (which is the official ISO 639-1 notation) , but Google has chosen to use 'no' for Norwegian, not making a difference between Bokmål and Nynorsk (nn).
This means, we cannot use machine translation for Norwegian. The same issue exists when we add a language ourselves and use the official locale as its code, e.g. nl_BE for Flemish. Although Google knows 'nl', the Google button is not shown.
Clearly, Pootle checks for the existence of the language code at Google, which is good. But we should have the possibility to define ourselves which Google language we want to use for the machine translation. E.g. for 'nl_BE' we would indicate 'nl'. Although the machine translation from Google is not correct Flemish, it would help the translator a lot if she gets it in Dutch.
If no Google language is given, Pootle should just use the first part of the language code if it is a locale (all the characters until the first underscore), or the complete language code if it is not a locale (not containing an underscore).
Could this be milestoned for 2.6.0 or 2.6.1?
Regards,
Edwin Boersma
using Pootle 2.5.1.1
I'd say the summary of this issue is this:
- The codes chosen on Pootle for languages and those used by MT providers don't always map.
- We need some way way to allow that mapping or to override that mapping.
@princeofnaxos we wanted to try to address this as part of the larger need to standardise Pootle's language codes and normalize them between Pootle and external. We might need to just add this to the MT configuration for now.
I see this FR is milestoned now for 2.10.1? I hope you really make it work in that version...