Contrib.social

Support asymmetric translations

Open on Drupal.org →
Created on 29 March 2015, over 9 years ago
Updated 16 September 2024, 3 months ago

Note: this issue is now Closed (won't fix). For details and where to go from here, see #249 → .

Problem/Motivation

Currently the only supported way of translating paragraphs is to have paragraphs translatable, but the host field not translatable.
Let's call this Symmetric translation workflow.
It perfectly fits for the case if page translations are really translations (say, copies, but in the different language). For example, website owner uses translation agencies to translate pages.

Many customers want an ability to have different paragraphs per translation.
Let's call this Asymmetric translation workflow.

Proposed resolution

In general:

  • Introduce Asymmetric translation workflow.
  • Let website developers decide which translation workflow to use.
  • Mark Symmetric translation workflow as recommended in the online documentation.
  • Inform website developers about possible negative effects of the Asymmetric workflow.

Overview of the Symmetric translation workflow:

  • Results in:
    • identical amount/order of paragraphs on all host entity translations
  • Benefits:
    • perfect integration with translation management tools like TMGMT
    • perfect integration with standard drupal translation workflow
  • Downsides:
    • paragraphs can be added/deleted only on the source translation
    • if new paragraphs were added on the source translation, website visitors may see them untranslated on other page translations until they are translated
    • reordering paragraphs on any translation leads to updating the order on all translations

Overview of the proposed Asymmetric translation workflow:

  • Results in:
    • different amount/order of paragraphs on host entity translations
  • Benefits:
    • paragraphs can be added/deleted/reordered independently per translation
    • it is not possible that website visitors can see untranslated content
  • Downsides:
    • increased complexity of the paragraphs module
    • not so good integration with translation management tools like TMGMT (not a case for the first translation, see #234)
    • translation workflow does not match standard drupal translation workflow (confirmed in #237)

Remaining tasks

  • define how it should work together with the maintainer
  • get the working patch (with tests)
  • commit it
  • update online documentation

User interface changes

- it is now possible to setup Asymmetric translations
- warning messages text is updated from "unsupported" to "not recommended"

API changes

- none

✨ Feature request
Status

Closed: won't fix

Version

1.0

Component

Code

Created by

🇨🇭Switzerland miro_dietiker Switzerland

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024