Problem/Motivation

This is follow up to issue: #1831530: Entity translation UI in core (part 2)

Proposed resolution

We have no proposed resolution.

Remaining tasks

  • Clarify what the question is... via usability testing.
  • (novice) Need screenshot(s) of current translation form.
  • Need screenshot(s) of alternatives.
  • Make a decision
  • Need a patch
  • Need an UI review
  • Need an accessibility review (after the having had the patch)

User interface changes

The whole issue is about UI.

API changes

No API changes.

Original report

#1188388-181: Entity translation UI in core from the phone call

Comments

Issue summary:View changes

Updated Issue Summary with the template

@ancamp thanks! this issue summary looks good.

Lets see if we can get the people from the phone call (@webchick, @Bojhan, @plach, @Gábor Hojtsy) to clarify the question. I suspect this is not bound to feature freeze so we have some time to really think about this.

In the mean time, anyone could do the task from the issue summary with just a simple sample content of maybe an article content type:
"Need screenshot(s) of current translation form." ... maybe along with a screenshot of the view of the source.

Well on the current translation form its not easy to see what the original values are, that is something we could make more usable. However I am not sure if this is a big issue, I'd rather focus on usability testing to see whether this is needed

Bojhan: Agreed. I think we both believe this can happen after feature freeze, it is likely just slightly different presentation of existing data / functionality.

@Gábor Hojtsy

Did user testing reveal anything for this?

Can we make a task for the next user testing that might help us get more info about this aspect?

Well, we reproduced the bug where if you translation enabled an existing content type, your existing translatable field values were gone (such as body). That got many people confused obviously, because it did not show up as source on the translation form either. No further feedback on this point.

Issue tags:+language-content

Fix tag.

Issue summary:View changes

Correct typo

I think it makes sense to wait on #1810386: Create workflow to setup multilingual for entity types, bundles and fields since that is really close, and perhaps on #1868058: Open Issues based on the Drupal 8 multilingual user testing results since that would get some of the easier already identified tasks out of the way and maybe another round of user testing will help show what direction to take on this.

Component:translation_entity.module» content_translation.module

Issue summary:View changes

Updated issue summary remaining tasks