Translating Editable Template | Community
Skip to main content
Clemente-3SHARE
Clemente-3SHARE
Level 2
March 13, 2018
Solved

Translating Editable Template

  • March 13, 2018
  • 3 replies
  • 3604 views

Hi all,

We are using Editable Templates, so far so good. Now the time for translation has arrived. We are using AEM Translation Projects workflow and a Translation Provider to achieve this.

The question is if someone ever had the experience of translating Editable Templates, and how they did it. It's weird that MSM doesn't support Editable Templates by default being Editable Templates the new approach recommended by Adobe, so I'm guessing some one else already ran into this issue.

Note: I would like to avoid the i18n approach.

Thanks!

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by smacdonald2008

    Heard back from Product Management on this:

    MSM does support editable templates

    AEM translation management workflows specifically work for content stored in /content, nowhere else.

    Translating content used in templates (“translating templates” per se doesn’t really make sense, with language copies etc.), can work two ways

    1) using content fragments, e.g. for header or footer content – this is one of the use cases content fragments were conceived for – including CF language copy content structure etc

    2) with i18n – correct, not ideal (i18n dictionary usage should be limited to UI and component strings), but not all that bad either, as volume is low. But it won’t create and manage language copy content structure of anything

    3 replies

    smacdonald2008
    smacdonald2008Accepted solution
    Level 10
    March 13, 2018

    Heard back from Product Management on this:

    MSM does support editable templates

    AEM translation management workflows specifically work for content stored in /content, nowhere else.

    Translating content used in templates (“translating templates” per se doesn’t really make sense, with language copies etc.), can work two ways

    1) using content fragments, e.g. for header or footer content – this is one of the use cases content fragments were conceived for – including CF language copy content structure etc

    2) with i18n – correct, not ideal (i18n dictionary usage should be limited to UI and component strings), but not all that bad either, as volume is low. But it won’t create and manage language copy content structure of anything

    Clemente-3SHARE
    Clemente-3SHAREAuthor
    Level 2
    March 13, 2018

    Thanks for the quick answer. Sadly it looks that Editable Templates still need some work on the AEM side.

    #1 May be OK for Header and Footer (though using Experience Fragments rather than Content Fragments), however one of the coolest things about Editable Templates is their Structure mode, unfortunately it is being really restricted by this Translation problem.

    It is a great tool for authoring several pages instances at once, but not being able to translate its content later is a real pain.

    #2 is not really practical in our case.

    Cheers.

      saurabhs5999723
      saurabhs5999723
      Level 2
      February 20, 2019

      how will you use content fragment for header and footer. You need to use experience fragment

      Terms & ConditionsAccessibility statement

      Loading footer...