| santhosh | |
| Oct 10 2022, 9:44 AM |
| F35784353: translate_entry_point.webm | |
| Nov 16 2022, 3:56 AM |
| F35726282: Screen Shot 2022-11-08 at 9.20.17 PM.png | |
| Nov 9 2022, 3:22 AM |
| F35560446: image.png | |
| Oct 10 2022, 9:44 AM |
Since the mobile language selector does not show the current language in the language selector, searching for it produces 'no-results' state. Ultimately showing CX entrypoint:
Here you can see that in https://tn.m.wikipedia.org/wiki/Aforika_Borwa#/languages search for tn gives entrypoint to translate to tn(Setswana)
Change 841040 had a related patch set uploaded (by Santhosh; author: Santhosh):
[mediawiki/extensions/ContentTranslation@master] MF languagesearcher: Avoid showing option to translate to current language
Change 841040 merged by jenkins-bot:
[mediawiki/extensions/ContentTranslation@master] MF languagesearcher: Avoid showing option to translate to current language
@santhosh Please correct me if I am wrong, typing tn in the search for the link in question shows Vietnamese here instead of Setswana ?
@santhosh Please correct me if I am wrong, typing tn in the search for the link in question shows Vietnamese here instead of Setswana ?
If your interface language is English (can simulate by adding uselang=en in URL) the name of Vitnamese language has "tn" in it and you get Vietnamese - because of very relaxed matching logic in search interface.
In my case, the interface language was not "en", but "ml". (can simulate by adding uselang=ml in URL). Then I wont get Vietnamese by searching "tn"
For testing this ticket you can use ml as interface language. Or any language that will produce "no results state" for "tn"
@santhosh thanks for the clarification
Test status: QA PASS
the translate entry point does not display when searching for a language in the Langauge selector