7 Replies
Dave Hansen

Hi, JP. 

We find that exporting the translation table (.doc export) is the easiest way for us to translate for our clients. Our translation platform accepts that without the need to try to go through the hassle of creating an .xliff file. 

If you're stuck and need some help, please feel free to reach out. 

daveh@inwhatlanguage.com 

Cell - 801.360.6832

J P

This is a feature that Articulate does not support, that comes straight from the Support desk.  I've attached the text from the email I received.  So have a "feature" of your software that you admit does not work and you cannot define....sure sounds smart. 

-----------------------------------------
9/7/2017
Hi Janelle,

I'm afraid we don't have a breakdown of how the XLIFF works but what I can tell you is that Storyline 3 currently only supports XLIFF version 1.0.  I also found this article which is applicable to Storyline 3:

https://articulate.com/support/article/xliff-translation-doesnt-work-sl2

If they are translating manually, it may be best to export the translation to MS Word.  This also has an option to include a Reference Column if needed.  More details here:

https://community.articulate.com/series/130/articles/articulate-storyline-3-user-guide-how-to-translate-content

 Hope this helps.

 Vevette Chua
Customer Support Engineer
Articulate Support - http://www.articulate.com/support/