Skip to main content
lutzU
Level 4
October 27, 2026
New

Translation of CF' s| Adjusting paths of referenced Content Fragments

Situation:
We have Content Fragments which have are referencing to other Content Fragments. When we send out this CF’s to translation, we expect that the path to the referenced CF’s are adjusted to the locale of the target page although the referenced CF’s are not part of the translation job as they have not been changed.

 

The path adjustment is currently only done if translation configuration is not set to “Do not translate”  under the dropdown "Translate Content Fragment Assets”. So, the path is only adjusted if te referenced CF’s are part of the translation job.

 

Requirement: 

To avoid unnecessary translation costs, we need an option  that the paths to referenced are adjusted although they are not part of the translation itself.

 

 

    4 replies

    shrutid56001193
    User Group Leader
    shrutid56001193User Group Leader
    User Group Leader
    October 27, 2026

    Hi ​@lutzU ,

    AFAIK, there’s no OOTB option for this in AEM. before diving into custom solutions, better to check what it really costs first. Most translation providers use translation memory, so a fragment that was already translated and hasn’t changed comes back as a 100% match. That is usually billed at little or nothing. 

    Translate
    https://www.shrutidamle.com/
    lutzUAuthor
    Level 4
    October 27, 2026

    Well, it’s a pitty that AEM does not offer this option. As you know, CF are used from external applications (could be a web shop for instance). We have thousands CF “snippets” also heavily using referenced CF’s.
    We do not want to unneccessarily pull in CF’s into the translation project which have not changed! 

    As you might know AEM Translation Framework has performance issue when you build bigger translation “packages”. We need to keep those collections as small as possible as we currently realy struggle with that already. So, this is definitely not a solution, sorry. 

    Translate
    shrutid56001193
    User Group Leader
    shrutid56001193User Group Leader
    User Group Leader
    October 27, 2026

    That makes sense. With thousands of snippets and the framework already struggling with job size, pulling unchanged fragments in is clearly not an option.

    This is not an optimal solution, but its what I could think of atm:

    • I would keep the “Do not translate” setting ON. The translation packages stay small, but AEM doesn’t adjust the paths, so the translated fragments still point to the source-language references.
    • After the job finishes, some custom code can do the thing AEM skips: it browses the references in the translated fragments and repoints them to the existing target-language copies.

    Worth raising it with Adobe as an enhancement request. A “rewrite references without translating” option - I know it wont help you immediately, it will take a while from their side to accept and implement, but I am sure others would have similar issue like this. 

    Translate
    https://www.shrutidamle.com/
    Terms & ConditionsAccessibility statement

    Loading footer...