Forum Discussion

BingjieHu's avatar
BingjieHu
Community Member
12 years ago

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!

  • LyaRyabenko's avatar
    LyaRyabenko
    Community Member

    Its incredible how little support there is for this obviously very common issue! 
    the basic things you ask us to do are done and do not influence anything. 

    I have imported a previous translation file into the same new version of articulate and that works fine, but my new language file is exactly the same, and also converted to Windowns 97-2003 - which is already quite an embarrassment for an updated software to not be able to read docx. 

    So three is clearly some bug going on, where reinstalling the program certainly is not a solution instead you should invest some real bug fixing in your updates. And this whole thread 3 years ago!!!

    I guess I am going to once again workaround manually, like with so many things with articulate. 

  • Hi Lya,

    I'm really sorry that you're still running into issues with this. I also responded to your other post here, and I'd love to make sure you're getting the help you need.

    Let me know if you hit any roadblocks, or if you'd prefer to work one on one with our Support Engineers, they're happy to help. Reach out to them here. 

  • Hi All,

    Hope you're all doing well & safe?

    I'm new here...

    I've been trying to import some translation files (in word format), and I have thoroughly inspected the document, yet Storyline crashed every time I tried.

    I have tried to restart my computer to see if it fixes the problem, but nothing helped so far.

    Could someone please guide me further?

    I have lots of work to finish and this problem is a bottleneck in my project.

    Thanks!

    • LaurenConnelly's avatar
      LaurenConnelly
      Staff

      Hello Prabhath!

      Welcome to E-Learning Heroes! I'm happy to help. This error message usually appears when files are located outside of your local hard drive. I'd recommend saving your project to your desktop and then trying to import the translation. Here's more information about creating, editing, and saving projects locally,

      If that doesn't do the trick, would you mind uploading both the .story and translation files to our team? You can share it privately in a support case. We'll respond as soon as possible.

      • ShrutiSinha-8b3's avatar
        ShrutiSinha-8b3
        Community Member

        Hello Lauren,

        Thanks so much for your quick response :)

        The problem I had highlighted earlier got sorted.

        I had not saved the translation file appropriately (I had excluded the original text column and I presumed I had to just retain the translation column in the local language).

        I could import the file without problems once I corrected this :)

        Thanks once again!

        Cheers from Bangalore, India..