Forum Discussion
Issues with translating using XLIFF file
Hi Everyone,
We have hit a major stumbling block with translating Storyline 360 courses to the point where we won't be able to use Articulate for developing our courses unless we can get this resolved. Our courses need to be translated into approx. 30 languages and we use native speakers for translation. The Word version is not an option so we have to use the XLIFF process. The process that we have used which works fine with other authoring tools is as follows:
- Export the XLIFF file
- We have a Java program that converts the XLIFF content into a spreadsheet that we share with translators
- Another Java program converts it back into the XLIFF file
- We then import the translated XLIFF file back into Articulate and manually fix any text formatting required.
This works just fine with Captivate and HTML courses but when we try it with Articulate it says import successful but nothing has changed, it just has the original English version.
We've been in contact with Articulate support but they told us it was out of scope so I'm putting it out here in case anyone has had similar issues and can offer any ideas on how we can work around this.
Thanks everyone!
Lots to unwrap here but let's start with some simple checks:
1. Look at your translated XLIFF file - does it have any TARGET elements? If you only have SOURCE elements that are translated, this could explain why you're getting the successful import but no translations.
2. Which XLIFF type are you using, 1.2 or 2.0? In my experience, the 2.0 standard is more closely adhered to by Storyline 360 than 1.2. This is mostly formatting but once you get the translation part working, this could potentially cause problems.
3. Start with a 1 to 2 slide course and then go through your process. See if you can get a successful import. It's a bit tedious but it will be quicker to determine where the problem might be.
Last insight - Storyline 360 does 'double-duty' with XLIFF files. Not only do they use it for translating but also for placement (font, position, size, color, etc.) An ingenious solution but it does make it a tad more difficult to get a properly formatted XLIFF file.
I hope that helps as a starter. Feel free to post what you learn.
Thor
Thanks Thor, I'm going to take a look at your suggestions and will let you know!
We've had some trouble identifying where we're going wrong with this.
I have created a one slide project with one text element (Hello World) as a test for this. Here is the .xlf File
<?xml version="1.0" encoding="utf-8"?><xliff srcLang="en-US" version="2.0" xml:space="preserve" xmlns="urn:oasis:names:tc:xliff:document:2.0"><file canResegment="no" id="Hello_x0020_World"><unit canResegment="no" id="65Dv4wdOu5h.Name" type="Articulate:PlainText"><segment canResegment="no"><source>Untitled Scene</source></segment></unit><unit canResegment="no" id="5zwlYb9VHtI" type="Articulate:DocumentState"><segment canResegment="no"><source><pc id="block_0"><pc id="span_1">Hello World</pc></pc></source></segment></unit><unit canResegment="no" id="6pMh8dnWnBS.Name" type="Articulate:PlainText"><segment canResegment="no"><source>Untitled Slide</source></segment></unit><unit canResegment="no" id="5v92wk0lwK7.Name" type="Articulate:PlainText"><segment canResegment="no"><source>Question Bank 1</source></segment></unit><unit canResegment="no" id="ProjectTitle.Title" type="Articulate:PlainText"><segment canResegment="no"><source>Hello World</source></segment></unit><unit canResegment="no" id="5ih9dSuLXeV.Name" type="Articulate:PlainText"><segment canResegment="no"><source>1 Untitled Scene</source></segment></unit><unit canResegment="no" id="5tQZNbkgYdN.Name" type="Articulate:PlainText"><segment canResegment="no"><source>1.1 Untitled Slide</source></segment></unit></file></xliff>
I wish to translate the text "Hello World" in the above to
"Salut tout le monde".
Would it be possible for you to return me the edited .xlf that will achieve this?
Mary,
I'm going to send you a private message so we can continue offline.
Thor
Sounds good thank you!
Just sent - please let me know if you didn't get it.
Hello,
is there any chance to share a modified/translated XLF file posted by Mary that is suitable for import in Storyline? I have the same problem - import is successful, but translated text is not imported. Many discussions end with private messages or file uploads outside of public posts and other users do not see a solution for described problems.
I really would like to see format of translated XLF file.
Thank you in advance for your help.Hello Gabriel - nice to meet you!
Attached you'll find a single slide Storyline file with a properly formatted XLIFF file. It's not the same as Mary's but it should give you a good idea in what it looks like.
A couple of notes:
- I took some content from a Rise 360 sample course
- I find SL interprets XLIFF 2.0 format better than 1.2 format
I hope this helps!
Hello Thor,
Nice to e-meet you!
Thank you very much for your quick response and for attached files. I really appreciate it.Glad to be of help! - if you're looking for an automated solution or more ideas, please send me a private message or reach out via LinkedIn as self-promotion is not permitted in the forums.
Hello everyone, 2 years later and I am having the exact issue. I wonder how accurate this translation process is, from the one who has used it. We are trying to avoid manual localization. We have a tool in the job which can translate xlif files, I imported back to SL and it says successfully but nothing change.
Hi Sofia,
Happy to help!
If your translation file is importing as successful but no text is getting translated, there's a possibility that no target tags were included in your translation file when the text was translated. For your reference, your translation file should have tags like this one:
<target><bpt ctype="x-block" id="block_0" /><ph id="generic_1"><Style Justification="Center" /></ph><bpt ctype="x-style" id="span_2"><Style FontSize="20" ForegroundColor="lt1,00" LinkColor="lt1,00" /></bpt><g ctype="x-text" id="text_2">text goes here</g><ept id="span_2" /><ept id="block_0" /></target>Try checking your translation file by opening it in a Word processor and searching for the presence of target tags using the Ctrl + F feature. If no target tags are present, you'll need to work with your translation team to have them correct the translation file. If target tags are present, please open a case with our support team here so we can take a closer look at why the translation process wasn't successful.
