Forum Discussion
Urgent translation import problem
Hi all,
Our team has been using Storyline and want to import translated Word documents into Storyline, but we are running into several big problems. When we import the text file, we encounter one of several scenarios:
1. All the text boxes import properly. This is the ideal situation. However, this does not happen all the time. More often, we encounter the next two scenarios:
2. Most of the text boxes import properly. We notice that anywhere between 2-20 text boxes do not have the newly imported text. Instead, the text box content seems to be deleted, while the object itself stays on screen, now blank. This is not ideal, but we have figured out ways to just manually copy/paste the missing text into these boxes. However, most recently we've encountered scenario 3:
3. Every single text box has its content deleted after import is finished. All text boxes are empty. Upon clicking on the text box to manually insert text, the entire text box disappears on contact.
This problem is even more confusing to us because one computer will import and see scenario 1, where another computer sees scenario 2 and another scenario 3 for the same set of Storyline and Word files... We are using 6 computers, all on Windows 7 either through the main PC or through Parallels. The only computer which consistently sees scenario 1 is using an older version of Storyline. The other computers are all using the latest updated version of Storyline.
Can you please help us to understand why this is happening, and what we can do about it?
Thanks!
I have now conducted the following test:
- Used the same original file as in my previous test
- Exported text to .xliff format
- Made a small change to the .xliff file and re-saved it
- Imported .xliff file to my project
- Viewed the content to discover the change had not been implemented
- Checked the .xliff file to confirm edit was saved
- Renamed the .xliff file
- Reimported to my project
- Confirmed that the change had not been made
I do accept that my XML knowledge is sparse and I could perhaps have not edited the .xliff correctly. The import of the XML was incredibly rapid, which implies that nothing is actually being imported.
Here is a video of the above:
https://qlnk.io/ql/548b8c86e4b0c9434c042404
Hi Martin and Ashley,
I thought it may be easier for me to respond in line with this post.
I also tested Martin's files and was unable to recreate the issue.
I wonder if this issue lies with a very specific Office setup, as the fault does seem to only occur at the stage word makes changes.
To test this, I have suggested we both take a copy of Martin's test course to try:
- On machine A - export a file, make changes, save and send to machine B. Import this file on machine B.
- Repeat the above for machine B to machine A.
- If this yields results, we may further test by exporting the file, as above, but make no changes. The tested file will simply have been exported and unopened.
Hi Martin and Ben,
Did you open up a new support case yet? If not, I can reopen the one Ben was previously working on so that our team can continue troubleshooting this with you as it may be easier to handle this outside of the forums, especially in terms of sharing files back in forth.
If you have a new case number, please let me know - otherwise, I'll share the information here with John who worked on the initial case, and have him include both of you in the email replies.
Hi Ashley
Yes I have opened a new case and the ref is #00445400. Iam just studying a reply from John Say on your support team now.
There is a suggestion that this may relate to using a Mac and possibly on the placement of the import/export files on the hard drive.
I shall respond to John and update the forum as I get further.
Regards
Martin
Thanks Martin - and I'll follow along in your case as well to see what else John has to share.
Hi Martin,
I just checked in on your case today - and it looks like all is working as expected now! It looks like there were a few issues such as a Shared profile on a mac, and a known issue of translating content via XML Localization Interchange File Format (XLIFF).
Glad things are back in working order and that John was able to help you!
Good day everyone,
I'd like to report that following the suggestions from staff here has greatly reduced the number of missing text boxes. That is, on a test I ran the import with both files on the root of my c:\ and eventually I made a folder right on my C: called c:\storylineimport\ and this reduced the number of missing text boxes from about a dozen or so to about 1 in 25 slide lessons.
However it was still random text in random objects. Usually just one per import.
Test Case 1:
Exported and translated the document. When I went to import a random block of text was missing. I closed both files. I reopened Storyline and imported the translation again. This time a completely different text box on a different slide went missing.
Test Case 2:
I opened a different lesson in Storyline. I exported the English text for translation. I then imported the document that was just exported, not making any changes to it. A random textbox on a random slide went missing. Repeated this experiment and found a different block of text on a different slide went missing.
Test Case 3:
I opened a Storyline file and did a translation import. A text box went missing. Without closing the document I merely imported it a second time. Now more than one text box was missing. Everytime I imported an additional random block of text from a different screen went missing.
I assume if I continued the experiment eventually the entire document would be devoid of text.
If anyone has additional tips or solutions I would appreciate it.
Hi Shawn! I see where you have a support case (00629486) open with our team, but it looks like the e-mail address we have on file is bouncing back as invalid.
Could you e-mail support@articulate.com with your correct e-mail address and reference Case#00629486 so that we can continue to assist you?
Had the same issue. Thanks Jennifer St. George. Changing the language in Word did it!
Awesome! Glad you found this older thread helpful, Kaja!
