This Epic ticket compiles the different efforts needed for translation in the new approach to support the Community Wishlist process. These include the translation of the Wish pages using machine translation when community-translations are not available (T361514), the localization of the wish form (T361512), the automatic translaiton of discussions (T295862) and other initiatives captured in the sub-tasks.
Background
The new Wishlist aims to increase participation among users across the globe and our projects. We can measure this by 1) diversity of submissions and 2) diversity of participation/edits by language/ip addresses.
To create a new wish, users will enter a valid form submission. The form requires fields such as" project, type (bug/new idea), title, description, and users impacted, as well as optional fields for phabricator tickets.
Readers can come from anywhere, and we want to maximize participation among wish consumers. Users may read, edit and comment on wishes. WMF will then compile wishes into groups called "focus areas" which contributors may respond to and vote on.
Goal:
Help anyone viewing a wish or focus area (and its related discussion) in their native language
Keep all conversations and edits on a single wish to one page
Non-goals
- Conversations about wishes (and wish content) are de-centralized on language-specific wish pages. We risk missing conversations, adding bloat, and changing perceptions of a wish.
User story
As a person participating in the wishlist, I should be able to read the content of submitted wishes and focus areas in my native language so that I am able to fully contribute my ideas and participate.
Requirements/acceptance criteria
Given that I am viewing a wish, focus area page, or talk page and the content is not available in my native language, I should see a banner to
- (default behavior) When the page has been human-translated in my native language, then the page should load as the translated version.
- (default behavior) show a CTA to extension:translate and available translations
- On pageload, show a CTA banner to view an automatic translation.
- when the content is in a different language than my default language
- When we detect 2+ languages on the page.
- When I select automatic translation, I should see the following:
- I should see the ability to change the content source language to a language of my choosing
- The page contents should load into my preferred language.
- All wish content should load at once; users should not need to progressively load the page.
- Formatting should be preserved, however the representation of translated content is more important than 100% accurate formatting.
- There should be a disclaimer that the page contents are automatically translated and that this is an experimental feature. This disclaimer should be localized to the user. A link to the original content should be available.
- A link to translate using extension:translate should be available.
- Clicking "edit" on the page should re-open the page in its original language.