Problem/Motivation
When translating views Config translation renders Global field twig output instead of source.
E.g: if I have a Global text field with value:
<div><em>Text in bold</em>
Adding a translation will render it instead of showing it.
This makes really difficult to translate if you want to keep the same markup, having to open the field in the edit view page in a different tab.
Proposed resolution
Escaping the source before display?
Remaining tasks
Discuss.
User interface changes
Instead of rendering the markup/twig, show it instead. This makes translation easier.
API changes
None.
Data model changes
None.
Comment | File | Size | Author |
---|---|---|---|
#2 | translate_view.png | 51.96 KB | maxocub |
#2 | edit_view.png | 100.69 KB | maxocub |
Issue fork drupal-2779221
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
maxocub CreditAttribution: maxocub commentedEdit view:
Translate view:
Indeed, the translate view form use a different text format than the edit view form. You can still view the source of both the source and the translation, and translate it instead of the rendered content, but maybe we should use the same text format that was use on the edit view form?
Comment #4
Gábor HojtsyI think the same input format should be used. But that is not exactly what @penyaskito found as bug, no? I think we are using the ck widget on both sides to support entering values, since the original UI also used the ck widget when appropriate (based on the input format docs).
Comment #16
LendudeSo #2741187: Allow usage of WYSIWYG in views text area fields comes at this from the other end, it allows the use of CK editor in the Views UI. That would be preferred I guess, more ckeditor instead of less?
Comment #18
quietone CreditAttribution: quietone at PreviousNext commentedAdding the issue in #16 as related.