Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Problem/Motivation
Webform puts the whole form structure into a single string which can't be translated automatically by TMGMT
Proposed resolution
Similar to #2853516: Custom field types are not exported properly if stored in a non atomic way (eg. metatags), add the possibility of a custom processor per config schema type.
Remaining tasks
Tests, save translation data.
User interface changes
API changes
Data model changes
| Comment | File | Size | Author |
|---|---|---|---|
| #12 | support_translation_of-2908120-11-interdiff.txt | 954 bytes | Berdir |
| #12 | support_translation_of-2908120-11.patch | 21.47 KB | Berdir |
| |||
| #11 | support_translation_of-2908120-9-interdiff.txt | 3.83 KB | Berdir |
| #11 | support_translation_of-2908120-9.patch | 21.48 KB | Berdir |
| #9 | support_translation_of-2908120-9-interdiff.txt | 3.83 KB | Berdir |
Comments
Comment #2
BerdirComment #4
BerdirAlso implemented saving of the translation, fixed the PHP7 syntax which should fix the phplint error and wrote a basic test.
Comment #5
BerdirTodo:
* Refactor the processor so we have less to overwrite, possibly support # replacement on all elements, maybe use a different replacement
* Think about tokens, maybe support escaping, skip elements that only have a token completely (or actually, make them not translatable)
Comment #7
BerdirWrong webform dev dependency.
Comment #8
BerdirAdded support for parent keys with a #, e.g. select options.
Comment #9
BerdirAdded support to skip values with only a token from the translation entirely.
Comment #11
BerdirWas testing with an older webform version, they actually changed that token. Lets hope they don't do that again :)
Comment #12
BerdirWrong patch..
Comment #15
BerdirCommitted.