# How to export opts in other languages

**URL:** <https://discourse.openehr.org/t/how-to-export-opts-in-other-languages/274>\
**Category:** ADL\
**Tags:** template\
**Created:** [17 January 2020 05:35 UTC](https://discourse.openehr.org/t/how-to-export-opts-in-other-languages/274 "2020-01-17T05:35:19Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Joyce](https://discourse.openehr.org/letter_avatar_proxy/v4/letter/j/35a633/32.png) [@Joyce](https://discourse.openehr.org/u/Joyce)\
**Post date:** [17 January 2020 05:35 UTC](https://discourse.openehr.org/t/how-to-export-opts-in-other-languages/274/1 "2020-01-17T05:35:19Z")

</div>

Hello,

How can I export opts to have them containing another language (or just in that other language) using Template Designer? The archetypes used in those templates are already translated. I have tried adding additional language when exporting but nothing has changed, is there some other setting I am missing?

---

<div class="post-metadata">

**Author:** ![sebastian.garde](https://discourse.openehr.org/user_avatar/discourse.openehr.org/sebastian.garde/32/3070_2.png) [@sebastian.garde](https://discourse.openehr.org/u/sebastian.garde)\
**Post date:** [17 January 2020 07:40 UTC](https://discourse.openehr.org/t/how-to-export-opts-in-other-languages/274/2 "2020-01-17T07:40:48Z")

</div>

From memory, you can start TD with a parameter, e.g.

“C:\Program Files (x86)\Ocean Informatics\Template Designer\TemplateDesigner.exe” /l:DE-de

It’s always one language in the generated opt I think

Sebastian

---

<div class="post-metadata">

**Author:** ![ian.mcnicoll](https://discourse.openehr.org/user_avatar/discourse.openehr.org/ian.mcnicoll/32/4430_2.png) [@ian.mcnicoll](https://discourse.openehr.org/u/ian.mcnicoll)\
**Post date:** [17 January 2020 10:44 UTC](https://discourse.openehr.org/t/how-to-export-opts-in-other-languages/274/3 "2020-01-17T10:44:50Z")

</div>

Hi Joyce,

TD will incorporate translations into other ‘secondary’ languages as long as all of the data points have translations but you have to make sure you include them when generating the .opt. There is specific dialog in the opt process that allows you to set secondary languages

However, as Sebastian says, the ‘primary’ language will remain whatever language was used at startup, unless you use the parameters that Sebastian suggested .

Some additional [stuff here](https://github.com/freshehr/openehr_tool_docs/blob/master/docs/tools_internationalisation.md)

---

<div class="post-metadata">

**Author:** ![Joyce](https://discourse.openehr.org/letter_avatar_proxy/v4/letter/j/35a633/32.png) [@Joyce](https://discourse.openehr.org/u/Joyce)\
**Post date:** [17 January 2020 18:30 UTC](https://discourse.openehr.org/t/how-to-export-opts-in-other-languages/274/4 "2020-01-17T18:30:45Z")

</div>

Thank you guys, this has helped so much!

---

<div class="post-metadata">

**Author:** ![ian.mcnicoll](https://discourse.openehr.org/user_avatar/discourse.openehr.org/ian.mcnicoll/32/4430_2.png) [@ian.mcnicoll](https://discourse.openehr.org/u/ian.mcnicoll)\
**Post date:** [17 January 2020 23:09 UTC](https://discourse.openehr.org/t/how-to-export-opts-in-other-languages/274/5 "2020-01-17T23:09:18Z")

</div>

I’d love to know more about your project, if you can share?
