Forum Discussion
xliff file imports, but removes all text boxes
I have a quiz created in English in Storyline 3 with a variety of extra triggers to keep track of the learner's progress. The quiz elements are out-of-the-box multiple choice and multiple select question types in a question bank, with a couple of introductory slides. I exported an xliff that was translated by our translation service (Smartling) into Spanish and French. When I tried re-importing the xliff file, it imported successfully, but left me with a file in which all the text fields are now blank. The titles of the slides reflect the translated language, but beyond that, none of the translation appears in the file and all the text seems to be removed (both in the slide view and the form view on the question slides). Is this a common issue? What can I do to resolve this so I can get these translations out to my learners?
6 Replies
Hi Gina,
Uh oh! I'm sorry the import of your translated text is ghosting you, but luckily it's not something I've heard a lot of! I do find one other recent user with the same issue, but we've yet to narrow down the cause or replicate the behavior.
I'd love to get some samples of your course into the hands of our team for some more testing. Can you share a copy of your .story file, the exported translation doc, and the one you were importing? You can include those here by clicking the Add Attachment button and I'll take a look!
You said you're using Storyline 3, so I wanted to check that you're on the latest update too - which is Update 3. Also let me know what version of Word and Windows you're using, just in case.
We encountered the same issue today (in SL2), and I was able to solve it by modifing the XLIFF file.
The <mrk> tags in the <seg-source> tags were added to the <target> tag (as per the XLIFF spec, as far as I was able to find).
When I removed all <mrk mtype...> and </mrk> tags from the XLIFF file (to be sure both in the <source> and <target> tags, the import went fine and all translated text was visible in SL.
Is this something that can be updated in the SL XLIFF import flow, so we do not have to do this removal work in the future?
Hi Dieter,
Thanks for sharing that workaround. I'll certainly pass this along to our product team for consideration. If we make changes to this in the future, we'll let you know!
I've run into a similar problem today, three years after this original post. I've imported my XLIFF file, and the slide names translate, but the text fields are blank. Was a cause or solution ever found for this? I haven't been able to find an answer here.
Hello Brian!
In our bug report, I see that we released a fix for this bug in one of our 2018 updates for Storyline 360. We haven't had others report this behavior since the update, so I'd like to work with you to understand what you're running into. It sounds like the slide names are translated, but the text fields are blank when importing the XLIFF file.
Which version of Storyline are you using? Also, by text fields, do you mean text entry fields or text boxes?
Lastly, are you noticing this happens with every project or just the one you're currently working on?
I appreciate your help in troubleshooting this issue!
We are five years later, but it seems the bug persists in Rise:
If an xliff includes <mrk> tags, the text content between those tags is simple ignored and the element of the course in which this text should go seems ignored.
I noticed that with the course title, I did not dig further.
for the records, the exported xliff include all content as this sequence of tags:
<trans-unit><source>[content in original language]</source></trans-unit>The translators add translations like this
<trans-unit> <source>[content in original language]</source> <target>[content in target language]</target> </trans-unit>
But some translators transform the xliff code the following way, compatible with the norm xliff 1.2:<trans-unit> <source>[content in original language]</source> <seg-source> <mrk mtype="seg" mid="1">[content part 1]</mrk> <mrk mtype="seg" mid="2">[content part 2]</mrk> </seg-source> <target> <mrk mtype="seg" mid="1">[translated content part 1]</mrk> <mrk mtype="seg" mid="2">[translated content part 2]</mrk> </target> </trans-unit>Indeed the file works again if the <mrk> tags are removed. But it is not clear if some space should be added if the slicing occured int the middle of a sentence.
the encoutered mrk are incremented in the 'mid' parameter throughout the file. Not clear what it is used for.The best would be that those file could be imported a such in Rise without modification...
