On mobile, when an article is missing in a given language, it is now surfaced when searching for it as an entry point to Section Translation (T286645). This is available for languages where the tool is enabled such as Bengali or Thai. However, there are still some aspects that need adjustment from the current behaviour:
- The entry point should be visible even if the Content Translation beta feature is disabled
- The navigation to Section Translation should happen in the same window (not a new window/tab)
- The mobile version should not be lost when navigating from the mobile version of an article to the tool on desktop
More detail about each aspect below.
The entry point should be visible even if the Content Translation beta feature is disabled
Currently, if the Content Translation beta feature is not enabled, the entry point to translate is not shown when searching for a language such as Thai.
The expected behaviour would be for the invite to translate an article to be visible when the beta feature is disabled and when it is enabled:
On mobile there is no clear path to adjust beta features. Given that we show the invite when searching for a specific language, I think that additional restrictions would only add confusion.
The navigation to Section Translation should happen in the same window (not a new window/tab)
Currently, when users access Section Translation, it is opened on a new window.
The expected result would be to just support it as a standard navigation (opening Section Translation in the same tab/window). Since it is a natural continuation and the user is not expected to frequently return back to the previous point (i.e., there is no need to keep the previous context).
The mobile version should not be lost when navigating from the mobile version of an article to the tool on desktop.
Opening this link on desktop shows the mobile version of the article. Currently, opening the language switcher and searching for Thai provides the option to translate which uses this link: https://th.wikipedia.org/wiki/Special:ContentTranslation?from=en&to=th&campaign=mflanguagesearcher&sx=true&page=Tenderloin%2C+San+Francisco
Notice that the domain changed from "en.m.wikipedia.org" to "en.wikipedia.org" (i.e., the ".m" part was lost). This results in the user navigating to Content Translation instead of Section Translation.
The expected behaviour would be for the domain to remain the same ("en.m.wikipedia.org") and the user to reach to the mobile version of Section Translation.
This issue does not happen when using a mobile device, it only happens when accessing the mobile version with a desktop device.