Problem/Motivation
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.
Proposed resolution
TBD
Remaining tasks
- Figure out a solution
- Write a patch
- Review it
User interface changes
TBD
API changes
None foreseen, possibily additions.
Comments
Comment #1
gábor hojtsyShould not be postponed anymore.
Comment #8
nterbogt commentedComment #16
dmitry.korhov