Hi

I work on a website with more than 300 languages. I've set it up in Drupal 7, and I now look forward to port it to Drupal 8 and make use of all the new multilingual functions and to organize the translators in the project better.

However, from the way I understand it, the way D8 works now, every time a translator will make a small correction on a translation, then *all* translations are re-saved.

Is there a way to get around this? Could we implement an alternative "Create new revision (this translation only)" in the node edit form?

I guess something like this would make D8 much more scalable to handle websites containing more languages.

Comments

matsbla created an issue. See original summary.

plach’s picture

plach
he/him
Primary language Italian
Location Venezia
CreditAttribution: plach for Drupal Association commented
Status: Active » Closed (works as designed)

This was abundantly discussed (for the last time, hopefully) in #2453153: Node revisions cannot be reverted per translation. Please have a look there for details.

The short version is: we write to the storage only field values that actually changed, so no scalability issues on that side are foreseen. The most problematic aspects atm are #2465909: Implement per-language locking at entity form level, to avoid that concurrent edits of different translations will be prevented, and #2465907: Node revision UI reverts multiple languages when only one language should be reverted to allow to revert revisions only for specific languages.

mkalkbrenner’s picture

mkalkbrenner
Primary language German
Location 🇩🇪
CreditAttribution: mkalkbrenner at bio.logis Genetic Information Management GmbH commented

In general @plach is right. But as soon as a erroneously implemented custom field type or something like that breaks the logic to only save changed values, you "can" run into performance issues or hit limits like max execution time.

So I second @plach that there's nothing to do in core yet. But we need to keep an eye on contrib ...