Translation of Design Data | Community
Skip to main content
Lokesh_Shivalingaiah
Level 10
January 7, 2016
Solved

Translation of Design Data

  • January 7, 2016
  • 3 replies
  • 813 views

Usecase:

Footer component is authored to have the content in the footer in the design mode so that its applied across the template. As this gets stored under /etc/design/<project>/template

What is the best approach to translate these design level content so that the respective language data can be pulled from its language copy sites.

 

Regards,

Lokesh

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 joerghoh

Hi,

I would manage the footer as content and inherit the footer content using an iparsys. With this approach you can easily manage a dedicated footer per site.

Jörg

3 replies

Jitendra_S_Toma
Level 10
January 8, 2016

Hi Lokesh,

Just some thoughts:

First & foremost, Does all multi-lingual websites have common design & does every site keep their footer design content in the same design?. If it is yes, I guess, we should think through how to organize multiple site footer content based on their language.

Let's assume if we did categorize different website footer content based on language, how are we planning to send this content to translation service?. Is it custom integration?. If yes, you have to take care of many things ( from sending content to translation to pulling translated content to CRX + setting their design).

Jitendra

Jitendra_S_Toma
Level 10
January 8, 2016
Hello Lokesh, I am curious to know how are you proceeding on this issue and did you find any feasible approach?. ---- Jitendra
joerghoh
Adobe Employee
joerghohAdobe EmployeeAccepted solution
Adobe Employee
January 8, 2016

Hi,

I would manage the footer as content and inherit the footer content using an iparsys. With this approach you can easily manage a dedicated footer per site.

Jörg