Page MenuHomePhabricator

Update grey interlanguage links entry point popup
Closed, ResolvedPublic

Assigned To
Authored By
Pginer-WMF
Mar 7 2019, 11:51 AM
Referenced Files
F29655099: image.png
Jun 27 2019, 12:40 PM
F29655091: Screen Shot 2019-06-27 at 4.27.09 PM.png
Jun 27 2019, 12:34 PM
F29655080: image.png
Jun 27 2019, 12:21 PM
F29655083: image.png
Jun 27 2019, 12:21 PM
F28728444: cx-grey-links-invite copy 4.png
Apr 22 2019, 12:49 PM
F28374313: cx-grey-links-invite.png
Mar 12 2019, 11:14 AM
F28340986: cx-grey-links-invite.png
Mar 7 2019, 11:51 AM
Tokens
"Like" token, awarded by Volker_E.

Description

Content translation surfaces missing languages in the list of interlanguage links for users to consider translating them. In this way users reading a Wikipedia article can easily identify that the article is missing in a language that they can translate into.

In preparation for Content translation moving out of beta (T214689), which will expose these entry points to more users (including those not interested in translation), we want to review this entry point based on the following considerations:

  • Simplify the process. Instead of the current options to either use Content translation or start from scratch, we want to focus the action only on translating. The current data on deletion ratios suggests that by translating users are more likely to succeed. this also allows to simplify the current formby not requiring the user to provide a title for the translation yet.
  • Provide a way for users not interested in translation to disable.
  • Resolve styling and layout issues identified (T192316)

Proposed solution

The proposed solution conveys that the page does not exist on the selected language and encourages the user to create it by translating.

cx-grey-links-invite copy 4.png (768×1 px, 331 KB)

This page does not exist in <target-language> yet.
Do you want to create it?

You can help Wikipedia by translating this page. Translating is an easy way to create new content in your language.
<terms-of-use-text> [Translate from<source-language>]

The message makes it clear that the user will be creating a page (i.e., we want to reduce the ambiguity about "translating" meaning to either get or provide a translation). It encourages the user by presenting it as a simple task ("it's easy") and connecting it to a motivator ("more content in your language"). Options are provided to:

  • Start the translation ("Translate from <source-language>"). The user will access the translation editor to start the translation.
    • The "Translate from <source-language>" action will also activate the future invite to the "Contributions" page (which is covered in a separate ticket: T216498). This will allow users that discover Content translation for the first time through these grey language links to become aware of the main persistent entry point.
  • Close ("X" icon). Clicking the "X" icon or outside the popup will close the popup dialog.
  • Settings (cog icon). Will link to the preferences section where the user can disable the Content translation entry points (T223896). This option won't be shown for the cases where the tool is still in beta.

The text about terms of use and license is the standard one (which needs an update: T214673)

Event Timeline

Pginer-WMF renamed this task from Update grey interlanguage link popup to Update grey interlanguage links entry point popup.Mar 7 2019, 11:52 AM

A few minor comments:

  • I would propose the settings cog icon to be at the lower end of the dialog, not close to the close icon. Similar to the Page Previews treatment. Maybe even with less opacity.
  • The close icon should be on one line with the dialog heading
  • Callout should follow 8px outer size, see T85949

A few minor comments:

Is the mockup below capturing well your proposed changes?

cx-grey-links-invite copy 4.png (768×1 px, 331 KB)

@Pginer-WMF That mockup ^ looks excellent from my POV.

@Pginer-WMF That mockup ^ looks excellent from my POV.

Great. I updated the ticket description. Thanks for the feedback, Volker!

Change 509046 had a related patch set uploaded (by Santhosh; owner: Santhosh):
[mediawiki/extensions/ContentTranslation@master] Update interlanguage link entry point

https://gerrit.wikimedia.org/r/509046

Change 509046 merged by jenkins-bot:
[mediawiki/extensions/ContentTranslation@master] Update interlanguage link entry point

https://gerrit.wikimedia.org/r/509046

Change 513055 had a related patch set uploaded (by Santhosh; owner: Santhosh):
[mediawiki/extensions/ContentTranslation@master] Show settings button in interlanguage entrypoint if CX is not beta

https://gerrit.wikimedia.org/r/513055

Change 513055 merged by jenkins-bot:
[mediawiki/extensions/ContentTranslation@master] Show settings button in interlanguage entrypoint if CX is not beta

https://gerrit.wikimedia.org/r/513055

Etonkovidova subscribed.

The settings button is not displayed in cx2-testing.

@Pginer-WMF
Checking wmf.8 - if a user has not yet enabled ContentTranslation feature in a lang wiki, the interlanguage wiki will enabled it automaticlly when user is redirected via grey interlanguage link. Is this behavior 'as designed'?

Steps:

  1. A user has ContentTranslation enabled in enwiki, but not in eswiki. On enwiki find an article (via Random article) that does not exist in Spanish, e.g. Konstantinos Kosmopoulos.
  2. Click on español grey link - you'll be redirected to Especial:Traducción de contenidos page even though you do not have enabled ContentTranslation beta feature.

The settings button is not displayed in cx2-testing.

@Pginer-WMF
Checking wmf.8 - if a user has not yet enabled ContentTranslation feature in a lang wiki, the interlanguage wiki will enabled it automaticlly when user is redirected via grey interlanguage link. Is this behavior 'as designed'?

Yes. Content translation is available on each wiki, but it is perceived as a global tool by the users. Users are not aware (nor should be) that when translating from French to Japanese they are on Japanese Wikipedia, but when they do it from Japanese to French they are in French Wikipedia instead. Thus, once the user accessed the tool in one wiki, the transitions across wikis automatically enable the tool to avoid the user to get a broken experience.

Otherwise selecting a language pair and starting a translation in CX could lead you to a message telling the tool has not been enabled, which can be confusing if the user is not familiar with the technical details of multilingual wikis.

@Etonkovidova, alongside with the question (that @Pginer-WMF has already answered), you moved the task back to priority backlog.
Now that it is clarified that behavior is expected, can the task be resolved or there is some pending QA work left?

once this patch is reviewed and merged this task is ok to go live

@Etonkovidova, alongside with the question (that @Pginer-WMF has already answered), you moved the task back to priority backlog.
Now that it is clarified that behavior is expected, can the task be resolved or there is some pending QA work left?

Yes, thanks @Pginer for the clarification. As per @Jpita comment - waiting on the patch to check after deployment.

Checked in wmf.11 - works according to the specs. Note: the issue T224880: Gray interlanguage link dialog is misplaced is still unresolved.

@Etonkovidova this is still not showing correctly
(screenshot from production)

image.png (126×780 px, 35 KB)

(screenshot from this task description)
image.png (60×592 px, 22 KB)

@Jpita
'wmf.11 cawiki` shows the correct phrasing which is the scope of this ticket.

Screen Shot 2019-06-27 at 4.27.09 PM.png (450×753 px, 108 KB)

Other issues (misplacement and display of $1) might be resolved as separate issues.

@Jpita
$1 is a placeholder for lang version of https://foundation.wikimedia.org/wiki/Terms_of_Use/en. You may also check https://translatewiki.net/wiki/MediaWiki:Cx-license-agreement/en to see what languages have the link in place.

Another helpful link to see if a message has been translated properly: https://translatewiki.net/wiki/Special:Translations?message=cx-license-agreement&namespace=8

The specs for the updated interlanguage links entry point popup are in place. The $1 issue may be a part of this ticket but also might be a separate ticket.