Change Details

When users are creating a new page, we want to let them know (once) that translating is an alternative. The solution supported in T216032 provides a generic entry point to start a translation where users have to search for the article to translate. In many cases it is not possible to guess which is the corresponding article in another language for the article that the user is trying to create (but does not exist yet). However, there are cases where we can have a reasonable guess. For cases where we can guess which article is the user trying to translate, we will adjust the new page invite to include it as a suggestion: |New page invite with a suggestion|Translation dashboard with the selected translation pre-filled| |---|---| |{F29898709, size=full}|{F28244391, size=full}| To support this we need strategies to have good guesses about the source article and the source language. Some approaches are listed below, but other ideas can be explored: For the source article we can consider: - Articles with the same title. This may work for articles on proper names or scientific names that do not change across languages (at least for the same script). - Use machine translation (when available) to find the article. - Use Wikidata labels to find the article. For the source language we can consider: - The language (other than the current one) where the user has more contributions. - A language the user has accessed (based on the #uls-compactlinks ), giving priority to larger wikis which are more likely to act as source languages. Additional considerations: - For this context is better to show no suggestion (which as covered by T216032) rather than showing a totally unrelated suggestion. So an approach that provides suggestions only in few cases but those are showing the article the user intended to create is preferred to a system where always provides suggestions but those are often unrelated to the user intent. - We may want to filter out disambiguation pages, not showing them as a suggestion.

When users are creating a new page, we want to let them know that translating is an alternative. The solution supported in T216032 provides a generic entry point to start a translation where users have to search for the article to translate. In many cases it is not possible to guess which is the corresponding article in another language for the article that the user is trying to create (but does not exist yet). However, there are cases where we can have a reasonable guess. For cases where we can guess which article is the user trying to translate, the new page invite will include a specific suggestion: |New page invite with a suggestion|Translation dashboard with the selected translation pre-filled| |---|---| |{F29898709, size=full}|{F28244391, size=full}| # When to show this invite We'll show the invite when all the conditions below apply: - On wikis where Content translation is enabled by default (no longer in beta). - When the system is confident that the suggested source article (T227571) and language are relevant for the user. It is better not to show the invite than showing it with an irrelevant proposal. # Design details - Note that this invite can be shown multiple times for a user, depending on the criteria defined above. - A cog icon provides access to the preferences (T223896) as a way to disable entry points if needed. Note that the settings are only available for wikis where the tool is available as default (i.e. out of beta). - Clicking on the suggestion will lead to the Translation dashboard with the translation information pre-filled. Ready for the user to confirm and start to translate. - The "find another page to translate" option will lead the user to the translation dashboard with the new translation dialog open for the user to search for an article to translate. - We may want to filter out disambiguation pages, not showing them as a suggestion. # Approaches to explore for getting good suggestions To support this we need strategies to have good guesses about the source article and the source language. Some approaches are listed below, but other ideas can be explored: For the source article we can consider: - Articles with the same title. This may work for articles on proper names or scientific names that do not change across languages (at least for the same script). - Use machine translation (when available) to find the article. - Use Wikidata labels to find the article. For the source language we can consider: - The language (other than the current one) where the user has more contributions. - A language the user has accessed (based on the #uls-compactlinks ), giving priority to larger wikis which are more likely to act as source languages.

When users are creating a new page, we want to let them know (once) that translating is an alternative. The solution supported in T216032 provides a generic entry point to start a translation where users have to search for the article to translate. In many cases it is not possible to guess which is the corresponding article in another language for the article that the user is trying to create (but does not exist yet). However, there are cases where we can have a reasonable guess. For cases where we can guess which article is the user trying to translate, we will adjust the new page invite towill include it as aa specific suggestion: |New page invite with a suggestion|Translation dashboard with the selected translation pre-filled| |---|---| |{F29898709, size=full}|{F28244391, size=full}| # When to show this invite We'll show the invite when all the conditions below apply: - On wikis where Content translation is enabled by default (no longer in beta). - When the system is confident that the suggested source article (T227571) and language are relevant for the user. It is better not to show the invite than showing it with an irrelevant proposal. # Design details - Note that this invite can be shown multiple times for a user, depending on the criteria defined above. - A cog icon provides access to the preferences (T223896) as a way to disable entry points if needed. Note that the settings are only available for wikis where the tool is available as default (i.e. out of beta). - Clicking on the suggestion will lead to the Translation dashboard with the translation information pre-filled. Ready for the user to confirm and start to translate. - The "find another page to translate" option will lead the user to the translation dashboard with the new translation dialog open for the user to search for an article to translate. - We may want to filter out disambiguation pages, not showing them as a suggestion. # Approaches to explore for getting good suggestions To support this we need strategies to have good guesses about the source article and the source language. Some approaches are listed below, but other ideas can be explored: For the source article we can consider: - Articles with the same title. This may work for articles on proper names or scientific names that do not change across languages (at least for the same script). - Use machine translation (when available) to find the article. - Use Wikidata labels to find the article. For the source language we can consider: - The language (other than the current one) where the user has more contributions. - A language the user has accessed (based on the #uls-compactlinks ), giving priority to larger wikis which are more likely to act as source languages. Additional considerations: - For this context is better to show no suggestion (which as covered by T216032) rather than showing a totally unrelated suggestion. So an approach that provides suggestions only in few cases but those are showing the article the user intended to create is preferred to a system where always provides suggestions but those are often unrelated to the user intent. - We may want to filter out disambiguation pages, not showing them as a suggestion.