Updated: Comment #N
Once we have #2161853: Add views language filter fallback, if node not in language of filter: show in source, show in X, hide → in place, content lists provided by language-filtered views will be able to (optionally) include content in a default/defined language (most likely the source language of each content piece) as a fallback mechanism if that content happens to not be translated yet to the current page language.
It would be really great UX-wise to provide links so that users with the right permissions can jump straight to translating these pieces of content to the specific language.
Add a link to the context to translate the entity to the page language.
Once we have #2161853: Add views language filter fallback, if node not in language of filter: show in source, show in X, hide → in place, content lists provided by language-filtered views will be able to (optionally) include content in a default/defined language (most likely the source language of each content piece) as a fallback mechanism if that content happens to not be translated yet to the current page language. It would be really great UX-wise to provide links so that users with the right permissions can jump straight to translating these pieces of content to the specific language.
Example use case scenario:
- Site has 2 languages enabled for its content (lets say English and Italian).
- The front page is as view of content set to filter the list to the current language with a fallback to the source if a piece of content is not translated yet.
- A user with the translator role comes to the front page and switches the language to Italian.
- What they see is a list of content shown in Italian if the content is already translated to that language + some content in English (not translated yet - shown because of the fallback).
- Next to each content shown in English there's a "Translate to Italian" link. When the translator hits the link, they are taken to the edit form for the Italian.
- Once done translating, they hit the save button and they return to the view where they started from, only this time the content they just translated in shown in Italian.
- They move on to translate the next piece of untranslated content.
Closed: outdated
11.0 🔥
views.module
Related to the Views in Drupal Core initiative.
(Drupal 8 Multilingual Initiative) is the tag used by the multilingual initiative to mark core issues (and some contributed module issues). For versions other than Drupal 8, use the i18n (Internationalization) tag on issues which involve or affect multilingual / multinational support. That is preferred over Translation.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Going through (really) old issues to clean up a bit.
The issue that this was based on was Closed (won't do), so just reading the IS here it seems that this won't need doing either.
Feel free to reopen this issue if you feel there is still something we can/should do here.