Follow up for #1831530: Entity translation UI in core (part 2)
Problem/Motivation
While testing et ui there were some sequence of creating and editing the thing (node) which caused the label source or original on the row that is the thing (not a translation) to not accurately describe it anymore.
Proposed resolution
none yet. the percentage of time this would happen might be too small to worry about.
Remaining tasks
- steps to reproduce - YesCT - use #96 #1188388-96: Entity translation UI in core as basis
User interface changes
Maybe add some words (back) into the translation overview
API changes
none.
Related Issues
This might have implications for the naming of the permissions #1807776: Support both simple and editorial workflows for translating entities
Original report
See comments
#54/4 #1188388-54: Entity translation UI in core item 4 (shows "original content")
#72 #1188388-72: Entity translation UI in core "content content" renamed to "original language"
#96 #1188388-96: Entity translation UI in core
#97 #1188388-97: Entity translation UI in core some discussion
#99 #1188388-99: Entity translation UI in core removing the phrase and just using n/a is proposed to leave it and move on with other things
#120 #1188388-120: Entity translation UI in core might have implemented the n/a
see related #184/6 #1188388-184: Entity translation UI in core item 6 has screenshot and talks of removal of "because source content has changed"
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | original_vs_source.png | 35.89 KB | effulgentsia |
Comments
Comment #1
plachComment #2
chrischinchilla commentedI followed the steps outlined http://drupal.org/node/1188388#comment-6576708 and I didn't get the problem anymore, after following the steps, nothing is marked as 'original'.
If this is largely fixed, do we need to write the steps to reproduce or can the issue just be closed?
Comment #3
yesct commentedyeah, in part we took out the words because we could not find a phrase that worked.
we will probably put the words back once we agree, and use them in #1833126: Having the original language in bold text in the node "TRANSLATIONS" tab is not semantic. make representation accessible.
Comment #4
effulgentsia commentedHere's a screenshot of the translations page for a node that I initially created in English, then made a Spanish translation, then went to node/1/edit and changed its language to French:
Note that French is labeled as "original" even though it wasn't the initial language the node was submitted in. Also note that the Spanish translation has a "source" of English, which is correct in that when I made the Spanish translation, it was based on an English source.
http://www.merriam-webster.com/dictionary/original has several definitions for "original". One is:
By this definition, French isn't strictly "original", since it isn't the "first instance".
Another is:
By this definition, French is the "original" one, in that by selecting it on node/1/edit, I specifically chose to make it the primary one, and all the other languages secondary.
Comment #5
gábor hojtsyI think we dont want to track both kind of originals, and the second understanding is fine. It was the same setup for Druapl 7's node copy translation. This text is already addded in #1833126: Having the original language in bold text in the node "TRANSLATIONS" tab is not semantic. make representation accessible., somI think we can close this.
Comment #6.0
(not verified) commentedfixed error in comment links