A translator will be used to the string translation where he has the source on the left and the translation on the right.
To make the experience with config translation more unified attached a patch which changes the UI for translation of configuration to a left/right source/translation base.

attached screenshot shows how it looks

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Schnitzel’s picture

Status: Active » Needs review
FileSize
5.89 KB

Status: Needs review » Needs work

The last submitted patch, 1998528-translation-ui-2.patch, failed testing.

victor-shelepen’s picture

How to attach the translation posibility to a custom settings form?

Schnitzel’s picture

@likin
mhh this question does not really have to do with this issue ;)
please open another issue if you've got a question. thanks!

Schnitzel’s picture

oops, forgot to adapt the tests with the new Form Structure, this is fixed now

Schnitzel’s picture

Status: Needs work » Needs review
Kristen Pol’s picture

I've tested and it looks pretty good. I'm not sure how clever it needs to be in terms of the textarea height at full width (it's pretty close to what it needs to be):

d8mi-config-trans-full-width.png

and the height at narrow width (for mobile):

d8mi-config-trans-responsive.png

Is "close" good enough for the full width? Do we need to deal with mobile? If so, should it be its own issue?

Gábor Hojtsy’s picture

Status: Needs review » Fixed

I committed this as-is for now. Let's do a followup for the responsive layout.

Schnitzel’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.