Hi there! Sorry for any trouble–I took a peek at your case and see Richard is wrapping up his findings for your most recent email; Leslie's right: you're in excellent hands, and he'll be in touch shortly. ☺️
I know how frustrating this can be, so really appreciate you working through this oddity with our Support Rockstars. I see our team is carefully analyzing the source code to nail down the culprit, and you should hear back with some next steps very soon. Thanks for continuing to reach out, and I'll also follow along!
Circling back to share our findings in case anyone else comes across a similar issue.
After rigorous testing, my teammate, John, isolated the issue to extra formatting tags in the translated XLIFF file. Looks like removing those extra tags in both the source and target tags did the trick ...phew!
It looks like the issue that the user was running into above was specific to their file. To specify:
We were able to isolate a number of <trans-unit>'s in your translated XLIFF file that was causing the issue. When you delete them, the xliff file will import into SL.
With your permission, I'd like you to share your project file with our support engineers to investigate what's happening with your file. You can share it privately by uploading it here. It will be deleted when troubleshooting is complete.
Sorry you've hit this roadblock — we're here to help! I want our support engineers to step in and take a closer look at this. I've opened a support case on your behalf, and we'll reach out soon via email with the next step!
I'm sorry to hear that you're experiencing this issue. I've opened a case on your behalf, and you should be hearing from one of our Support Engineers shortly via email.
For me after pushing a claim to my supplier, he sent me a new version that could be imported into storyline without issue. But in the end, I don't know exactly what the root cause is. I guess it's related to the tool used for translation. Today I had another case in Turkish, so I think it's not due to a specific language but rather an incompatibility between the tool used and Storyline.
Hello Hugues Lumiere, thank you for your quick reply. What can I do? Are there specific criterias the translator has to respect? Is there a possibilty to "convert" the file? thx Manja
When I indicated at our supplier the object of the translation either to be used to Storyline, they sent me the exact same file but adapted to Storyline, so I assume that indeed there are specific criteria to be met. How to proceed, which ones, unfortunately I don't know.
Sorry if I wasn't clear, I guess there are specific criteria that the translation tool needs to consider in order to be compatible with Storyline. Sending my own file will not solve your problem. Anyway, the Storyline technical support should be able to help us depending on these key features required.
I had xliff files that were displayed as ok via xliff validator - and caused a crash when imported into storyline.
I have also asked for a specification for "articulate" xliff files in the context of a support case (03201470) and got no helpfull answer.
my question was:
Is there any written specification for the extra Articulate XML/xliff requirements, which we can send to the translation agency.
articulate answer:
Thanks for clarifying. We're already tracking a feature request that will allow Storyline to show better-detailed error reports/messages. I attached your case to the request so that it will count as a vote. Once reviewed by our teams, perhaps it will be available in a future release. You can refer to this article to know more about our process for handling feature requests:
22 Replies
Hello, Learning Agency Team!
I'm really sorry you keep running into this error message. It looks like you submitted your project files to us in case #01468431, is that right?
Thanks for letting Richard know that you're still having trouble with the new XML file he recently sent. You should hear back from Richard soon!
Hello, I have got some help but it does still not work and Richard has not answered me back do I have to make a new case?
Hey Learning Agency Team,
Looks like Richard reached out to you and you've replied, so I think you're getting the replies.
You're in good hands :)
Hi there! Sorry for any trouble–I took a peek at your case and see Richard is wrapping up his findings for your most recent email; Leslie's right: you're in excellent hands, and he'll be in touch shortly. ☺️
Hi Katie and Leslie I have still not got any answer and I have not been able to find out why it is not working :S
Thanks for your follow-up, Learning Agency Team!
I know how frustrating this can be, so really appreciate you working through this oddity with our Support Rockstars. I see our team is carefully analyzing the source code to nail down the culprit, and you should hear back with some next steps very soon. Thanks for continuing to reach out, and I'll also follow along!
Circling back to share our findings in case anyone else comes across a similar issue.
After rigorous testing, my teammate, John, isolated the issue to extra formatting tags in the translated XLIFF file. Looks like removing those extra tags in both the source and target tags did the trick ...phew!
Thanks again for working through this puzzle with us, Learning Agency Team! Give us a shout if you have any more questions!
What were the tags please? I am having the same issue?
Hi Development Ucps-elearning,
It looks like the issue that the user was running into above was specific to their file. To specify:
We were able to isolate a number of <trans-unit>'s in your translated XLIFF file that was causing the issue. When you delete them, the xliff file will import into SL.
With your permission, I'd like you to share your project file with our support engineers to investigate what's happening with your file. You can share it privately by uploading it here. It will be deleted when troubleshooting is complete.
Hello,
I have the same problem. Is there any solution?
So sorry you're having this trouble, Elena.
I see you also reached out in this discussion. Let us know if you can share the course for testing—we'll export it and let you know what we find!
This post was removed by the author
Hi, I have run into this exact same issue. Any assistance is appreciated ! I have attached the file.
Welcome to E-Learning Heroes, Chantel ⭐️
Sorry you've hit this roadblock — we're here to help! I want our support engineers to step in and take a closer look at this. I've opened a support case on your behalf, and we'll reach out soon via email with the next step!
Hello,
I have also the same issue, but only with a xlf in china version, all imports on others languages work well. Do you have an idea of this problem?
thank you in advance for your help.
Hi Hugues LUMIERE,
Welcome to the E-Learning Heroes community! ✨
I'm sorry to hear that you're experiencing this issue. I've opened a case on your behalf, and you should be hearing from one of our Support Engineers shortly via email.
Hello,
I have the same issue with chinese language with the XLIFF file.
I've done translation to english with Word - this worked very well.
I would highly appreciate your support,
Manja Conrad
Hello Kelly & Manja,
For me after pushing a claim to my supplier, he sent me a new version that could be imported into storyline without issue. But in the end, I don't know exactly what the root cause is. I guess it's related to the tool used for translation. Today I had another case in Turkish, so I think it's not due to a specific language but rather an incompatibility between the tool used and Storyline.
BR
Hello Hugues Lumiere, thank you for your quick reply. What can I do? Are there specific criterias the translator has to respect? Is there a possibilty to "convert" the file? thx Manja
Hi,
When I indicated at our supplier the object of the translation either to be used to Storyline, they sent me the exact same file but adapted to Storyline, so I assume that indeed there are specific criteria to be met. How to proceed, which ones, unfortunately I don't know.
Hi, can you send the adapted file to me? So I can re-import this file?
Viele Grüße
Manja Conrad
Von: E-Learning Heroes
Gesendet: Dienstag, 30. August 2022 09:48
An: Conrad, Manja
Betreff: Reply to Importing xlf translation file
[Das Bild wurde vom Absender entfernt. E-Learning Heroes]
Sorry if I wasn't clear, I guess there are specific criteria that the translation tool needs to consider in order to be compatible with Storyline. Sending my own file will not solve your problem. Anyway, the Storyline technical support should be able to help us depending on these key features required.
I had xliff files that were displayed as ok via xliff validator - and caused a crash when imported into storyline.
I have also asked for a specification for "articulate" xliff files in the context of a support case (03201470) and got no helpfull answer.
my question was:
articulate answer:
I should do a feature request !!! - for fixing bugs and creating dokumentation ???
Jürgen