Problem/Motivation

The upcoming editing form for entities will allow to edit translatable and non-translatable values on the same form.
To maintain the usability the form elements should have a way to indicate whether the are language specific or not.

Proposed resolution

Introduction of a new form element property e.g. #multilingual that allowes to define whether a field element is language specific or not.
The behavoir should be equal to the #tree property, which means child elements inherent the property value from the parent but can override it if necessary.

Remaining tasks

User interface changes

API changes

Related issues

#1807776: Support both simple and editorial workflows for translating entities postponed on this issue.
D7 #1282018: Improve UX of language-aware entity forms
#1188388: Entity translation UI in core

Files: 
CommentFileSizeAuthor
#4 add-2012-12-26_0023.png59.19 KBYesCT
#4 af-2012-12-26_0024.png59.84 KBYesCT

Comments

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

related background see #1188388-54: Entity translation UI in core/2 and #57

Also, #1188388: Entity translation UI in core has a work around to do a simple version.

Title:UX: Introduce a #multilingual key (or similar) for form elementIntroduce a #multilingual key (or similar) for form element
Issue tags:+Usability

StatusFileSize
new59.84 KB
new59.19 KB

When adding content, the fields are not noted with what would be shared across languages if translated.

add-2012-12-26_0023.png

When adding a translation, it shows which fields, when changed, would change every translation (and the actual content/node). Those are marked with (all languages) on the field labels.

af-2012-12-26_0024.png

Next steps:
determine if this issue is still needed or if it is solved as part of the previous work.
if it is still needed: add more detail in the form of specific next steps to take.

Issue summary:View changes

Updated issue summary to put related issues together under related issue heading and added et-ui 1188388 as a related issue