We exported a .story file to XLF 1.2 and created a pseudotranslation to test the import. When we import the pseudotranslated XLF, there is no error from Storyline, but only the slide names update to the pseudotranslation strings. All body content on the slides disappears completely -- we don't even see the original English copy.
We are happy to help! I do not see a similar issue when importing an XLF file into Storyline. Can you share your .story file with us? This will help us better understand why only the slide names update and why the slide content disappears.
A quick update: the pseudo translated strings are in Storyline, because after the import, we tested exporting the story again, this time as MS Doc, and the psuedo translation appears in the Source Text column of the tables. They just are not visible in the Storyline editor.
We also tested an export to MS Word from the original, clean English .story file. Test translations from that do display in Storyline after we import the translation back in, but because of the way the course is structured, we believe that XLF is a better solution to manage the translations.
Please see attached a zip pack holding the .story file, the xlf file created by Storyline and the corresponding pseudotranslation, and a screen shot showing what we see after importing the pseudotranslation.
I'm sorry to hear that you're experiencing this issue as well! I went ahead and opened a support case on your behalf. You should be hearing from one of our Support Engineers soon via email.
7 Replies
Hi Sonja!
We are happy to help! I do not see a similar issue when importing an XLF file into Storyline. Can you share your .story file with us? This will help us better understand why only the slide names update and why the slide content disappears.
A quick update: the pseudo translated strings are in Storyline, because after the import, we tested exporting the story again, this time as MS Doc, and the psuedo translation appears in the Source Text column of the tables. They just are not visible in the Storyline editor.
We also tested an export to MS Word from the original, clean English .story file. Test translations from that do display in Storyline after we import the translation back in, but because of the way the course is structured, we believe that XLF is a better solution to manage the translations.
Please see attached a zip pack holding the .story file, the xlf file created by Storyline and the corresponding pseudotranslation, and a screen shot showing what we see after importing the pseudotranslation.
Hi, Sonja.
Thank you for sharing the .story file with the translation and for the additional details!
I went ahead and opened a support case on your behalf with our engineers. You should hear from our team soon via e-mail.
How was this solved in the end? We have exactly the same situation here.
Was the problem in the xlf or in the story file?
Thanks!
Hi Felix,
We were not able to get the xlf file to import into Articulate and our deadline was at risk. So my team worked from the MS Doc export.
Hi Felix,
I'm sorry to hear that you're experiencing this issue as well! I went ahead and opened a support case on your behalf. You should be hearing from one of our Support Engineers soon via email.