How to translate content using XML?

Hi Ashley,

thank you very much for your quick response!

MS Word vs. XLIFF

The translation process works well with the MS Word files but it doesn't work with the xliff-file. As the company who will translate the content is using a special software (SDL Trados Studio), they would rather prefer the XML-Format for an efficient translation process.

You've written that "in some cases" it won't work. Is there a Workaround I can do, e.g. changing some things in the file, so that it works correctly with an xliff-file? Do you know when this "known issue" will get fixed?

Source Language in XLIFF

I've changed the language of the Player but the language in the xliff-file hasn't been affected: The header of the *.xliff shows source-language="en-US" target-language="ge-DE"

Thank you for your help!

Kind regards,

Franz

Hi Franz,

I don't have a time frame on when the issue would be fixed unfortunately, but a few of the known reasons include a file with special characters or diacritical marks in the slide titles. I've included this thread in the existing report with our QA team so that when there is additional information to share we'll be able to update you here. 

Could you share your XLIFF file here too? 

Any news on an update. I also work with a 3rd party translation service that requires XML.

Hi Kurtis and welcome to Heroes!

This is still an outstanding issue with our QA team and you can see that information here. 

Hello Heroes,

Is there any update on the above query ?

Regards,

Vaibhav

Hi Vaibhav,

This is still a known issue documented here for Storyline 1 and Storyline 2 detailed here. 

Hello Ashley,

we are having the same problem! Wen need to do the translation ia xliff. It is a critical function for a global working company. Please give me an update or a workaround. Is it possible to sent a not working XLIFF to the support so that they can tell us what signs are to change or what else is to do to make the specific File work?!?

Hi Evelyn,

Did you review and test the information shared in the links I previously included ( the post right above your reply here)? It's up to the translation tool  to set the state equal to something other than "new". If you modify the file to have state="translated" and then perform the import the translation change is made. You may want to follow up with your team who manages the translation tool to see if they can assist with making this change. 

Hi Ashley,

for my testing I changed the Xliff by myself without any translation program. For testing I had changed only one entry. So definitely it could not caused from a translating program.

Hi Evelyn,

Thanks for clarifying that element. It looks like we're talking in a few different forum discussions, and I'd like to centralize that conversation to ensure I don't miss anything and that you get the help you need. Can you reach out to our Support Engineers using this form and you'll be able to upload your project file and describe the different issues you're running into?  Once you've started a case, please let me know the case number and I'll follow along as well. 

Case #00834526
 

Thanks Evelyn and I see you're working with Ryan, so I'll keep an eye on the case as well to share any updates here in the forum discussion. 

Thanks Evelyn, and it looks like Ryan was able to confirm this as a connection to a bug and filed a report with our Quality Assurance team to investigate further. At this time we don't have any additional information to share, but we'll do so via your case and in this forum discussion.  

Dear Ashley, 

I went throught all QAs regarding the same issue everybody seems to have.

I represent a translation agency and we struggle to upoad or SDL 2014 XLIFF to Articulate Storyline 2. 

Tried manual override of
"new" -> "translated" issue
"de-DE" -> "de-GE" language pair issue

Tried various type of exports from SDL and none of it worked. 

When reading this QAs I understand that this issue is at hand for more than 3 years. 

Where you guys able to solve this to some extent? 

Thank you 

Martin

Hi Martin, 

Are you seeing the blank text fields after the import? That was an issue in Storyline 2 and it was fixed with the release of Storyline 3 and Storyline 360. 

If you're seeing a different behavior in the import, let me know and we can dig deeper! 

Dear Ashley,

exactly as you describe it. The fields will turn blank , litteraly all
of them.

I m sending a video of the process.

Kind regards

Hi Martin! Did you mean to include a video file with your reply? It looks like it didn't come through, so you'll want to click here to open the forum thread. Then, use the "Add Attachment" button to attach the video file. Thanks! 

I've send the video as a reply to email which apparetly did not work :) 

Thank you for the heads up and hope it works this way. 

Thanks Martin for the video - looks like that's Storyline 2 and matches what I mentioned. Could you also share a copy of your .story file and translation document? I'd like to test your examples as well. 

You'll need to visit the forum discussion to upload these attachments. 

Dear Ashley, 

I am able to send you the files directly , however I can not in good faith post it to a forum discussion. Would it be ok for you to provide a direct contact ? 

Kr

Hi Martin,

Absolutely - if you can upload it to me here. That's a private link and then I'll be able to test your files and share with our Engineers if needed. The files will only be available to Articulate employees. 

If you have any other questions about that let me know - and just give me a heads up here when you upload the files.

Done

Thanks Martin - I'll respond in your case! 

Can y'all report back on what was resolved, or if it was? I've got clients who want to use automated translations, but I don't want to guide them the wrong way since they're planning on translating the courses for 5-9 languages.