Thu, Oct 14
A related issue was reported as a separate ticket: T293387: Language not available for a new translation when used as target for suggestions
Tue, Oct 12
Mon, Oct 11
Section Translation is now also available also in Thai, Igbo, Yoruba, Hausa and Kurdish, and we are open for requests to enable it in more. For other languages, Section Translation is available on test wiki where it can be used until it becomes available in more wikis.
This is a known issue with Google Translate. I'm merging the ticket with our task, but the main activity would happen in Google's tracking system.
I think this may be a duplicate of this style regression: T291252: Regression in link styles on Content Translation
In Content Translation we have not been doing language detection, the focus has often been on content mapping across two languages we knew in advance. In particular:
- Finding which could be the equivalent sections across two versions of an article in different languages. For which we use a database of equivalent section titles across different languages.
- Finding which could be the equivalent template parameters across templates in two different languages. For this[[ https://github.com/digitalTranshumant/templatesAlignment/tree/master | a machine learning approach ]] based on multilingual fastText vectors was used.