nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to set up an i18n page

smitty42

Hi,

I want to set up a page for international usage. Templates will be the same on every country the page will be rolled out. But content will differ because of the native language.

My approach is to set up many branches for each country. But than, changes on layout templates has to be updatet form main branch manually? Is there a better approach?

thanks in advance
Martin

Find more posts tagged with

Comments

bittu

=> I think you can use DCR translation for native language.
=> Also check form api for calling translated DCRs.

smitty42

ok, may be. But the content will differ some more: may be on some countries there will be more / less pages than on the master site. And every language will be deployed on an own domain. So the only things that will be in common for all sites / branches are the templates and data capture forms.

nipper

Hi,

I want to set up a page for international usage. Templates will be the same on every country the page will be rolled out. But content will differ because of the native language.

My approach is to set up many branches for each country. But than, changes on layout templates has to be updatet form main branch manually? Is there a better approach?

thanks in advance
Martin

You should have gone to GearUP last year. I talked about this a great deal

You can do different branches or different folders on the same branch. (/data/en-us, data/fr-fr etc).

In any event, your DCTs should be 1 line, an in-line tag to run an IPL that builds up the XML required for a DCT. That way if you need to change the DCT, you change it in a single IPL rather than on mulitple branches.

The TPL will behave in a similar manner. It will have 2 lines, the first will be a tiny bit of prel to output the BOM and the second will be an iw-include for the real TPL.

Email me off-line if you want me to send my GearUp slides.

Andy

cesarecastro

Here is a solution that one of our developers (Goverdhan) identified as an approach to managing DCTs and TPLs that are used across multiple branches.

XML Entity References
An XML document, which include DCTs and TPLs, can be created by calling other files via Entity References. In the attached test.txt file you will find that the ENTITY dct_items1 and dct_items2 are declare and called back to build the DCT file. There is a lot of information about this topic on the internet.

Branches to Support Multiple Languages
While setting up your language structures in Teamsite, keep in mind that your approach will be greatly impacted by several factors. The two that I have found have the greatest impact are your security concerns (who has access to what) and the Branch Licensing agreement that your company may have. Not everyone has unlimited Branches.

Nipper's presentation was also very informative last year. So I would get it since he offered it.

nipper

Nipper's presentation was also very informative last year. So I would get it since he offered it.

How would you know, you fell asleep. Smiley Very Happy

Or was that Bo ?

cesarecastro

I tought I heard someone snoring. It wasnt me, I was comparing your presentation against the IW documentation that I love so much.

I dont know who it was, I was sitting way in the back. I swear.

Edited to keep things kewl. By the way, I did not know who Bo was but now I know who he is.

ISCBorisB

Cesare... Do not let Andy's easy tone to fool you. We are friends - and it does not mean that I would appreciate
stupid jokes from anybody who wants to chime in. Regards.

gir

I have worked on creatind Multilingual templates as it was a requirement for one of my project.
I am using Teamsite 6.5.0. I created a language branch (Ex:en(English),pt(potuguese)etc.) used a common presentation tpl and DCT file which could be replicated to all lanaguages.
Translation of the DCR's where done through 'en' branch with a translation workflow we had built.
All this time i had thought this one idea but seeing this discussion I think you are talking about a different thing which i didnt try.
Could you please tell me in detail.

Thanks,

cesarecastro

Gir,

Did you see my example? Did you try using it? Take a try at it, and after that if you have any questions I can help you. But with this approach, you do not need to replicate the structure of the DCR or TPL or any XML accross branches.

I tought the question you had was, how to manage a DCR that is replicated accross many branches from a central location? If we are not addressing your question, please explain.

Hint(high level) - using the example. by the way you need to rename the attached txt file to dct.

1. Take the xml structure from your current DCT and put it into a seperate xml file and store it some place accessible by the a DCT.
2. create a new dct - similar to example
3. Use the Entity to call the xml you created in step 1
4. Now open the DCT from the Teamsite interface. The DCT should show as normal.

This are some very high level instructions. I am pretty sure you can figure out the details.

NOTE:My last post was edited to protect the inocent.