Per this thread, Translating Editable Template , there is a suggestion to use content or experience fragments in an editable template for translation.
I have gone down this road using 6.4 to little success. I have tried using Fragment translation two ways, within and outside the variants. The issue is within the editable template the Experience Fragment path is not translated from en to the other languages. What is the best practice for header and footer content using fragments and MSM?
Here is what I have tried:
Example Content paths
one way to do it is create language copy by using translation workflow.
1. either select create and translate while creating language copy (fr) from English page. make sure no fr language copy of fragment exist.
2. or create a translation project and include your English page. It will ask to create language copy.
But.. but.. but.. this solution only works for creation. While update again the same issue comes.
We have not investigated further as the project that needed it has not started because of a rebranding effort. I am attending the session on multi-lingual handling at Summit this year for this question a lone. It seems ridiculous this does not just work. I have been using some other contacts at Adobe and they confirm this does not work today.
I would recommend your own fragment include component that is language aware. Rather than blindly include the path in the fragment is looks for the fragment path for the proper language. You have to make sure you handling all the caching cases to ensure you are showing the latest content. One good option would be an Apache SSI include on the publish side. This will have apache do the include dynamically getting around the need for invalidation of all pages. It will always pull the latest fragment HTML without needing to invalidate the parent page.
Hope that helps.
Hello Ankur, If templates are not looked at for translation workflows then what is the Adobe recommended approach for creating a header a footer for multi-lingual sites? If they cannot be in the template then we need to go back to the iparsys approach so everything is translated correctly without impacting the authoring.