In #2431329: Make (content) translation language available as a field definition → we made the language field translatable, but we prevented translation languages from being changed, as this would require some refactoring that was not strictly needed to fix the parent issue. However changing the translation language has perfectly valid use-cases, hence we should not forbid that unless it turns out it's very difficult to implement.
TBD
TBD
None foreseen, possibily additions.
Active
11.0 🔥
(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.