Urgent translation import problem

Hi Peter,

Thank you for your reply!

To answer your questions: We have been each working from our local drives - we use the same version of a file downloaded from our file server, but each makes a local copy on their own computers when testing the imports. I think that our published output is less than 260 characters... I will have to check this for each of our machines, but to my knowledge so far I think that they are within the character limit. We do not use special characters or symbols or accents in our file names.

Our workflow: we used one computer (actually, the one with the oldest version of Storyline) to export Word documents for translation. We send these Word documents to a company which translates them, and sends it back to us in the same format. We then disperse the returned files across different members of our team, who import the file, and this is where we have seen the problems. 

My suspicion was that maybe the problem came up because the older version of Storyline exported the Word files, so it caused problems on all of the computers with new versions of Storyline?

We just tried a test run on two computers to see if this is the problem.. I will try to describe what we did below, and maybe you can help us understand the back end a little more? To give context, computer1 is the one with the old version of Storyline, and computer2 has the updated version of Storyline. The file we are trying to import is the one returned by our translation company. Same word file, same Storyline file. We downloaded fresh copies of the Storyline file from our network onto both computers and tried a Translation-import of the document - Computer1 had no problems and Computer2 encountered several missing text boxes.

After this, we ran a test and downloaded fresh copies of the Storyline file.story onto both computers. 

1. Computer1 ran a Translation-export on "file.story" and saved the output as "test1.doc". We changed font colors on "test1.doc" and tried a Translation-Import on fileA.story in the same computer. Everything ran smoothly - we can tell because all the font colors changed in the Storyline file. 

2. Computer2 ran a Translation-export on "file.story" (downloaded from the network) and saved the output as "test2.doc". We changed font colors on the file, ran a Translation-Import on the same computer, and everything ran smoothly. 

3. We exchanged and opened up "test1.doc" and "test2.doc" on the opposite computer. Computer1 tried a translation-import with "test2.doc" on its local copy of "file.story", and vice versa. Both computers were able to run this test smoothly, no problem.

4. We then ran the Translation-import on the original file given to us from the translation company - now, it works smoothly on both computers, even though we encountered missing text boxes on Computer2 at the beginning.

Then, we ran one more test only on Computer2, trying to remove Computer1 from the equation. We used another fresh copy of file.story, translations-exported a Word document, re-imported this Word document to ensure that this works, and then re-imported the translated document from our translation company. Now, it works again. We did one more test by downloading a fresh copy of file.story, and only importing the translated document. Again, there are missing text boxes. 

This is as much as we have tried to do so far... I apologize for such a long message! But I hope that providing this information can help you to maybe see where the issue is, and help us to solve it? Our temporary solution is to always do the process of export-import-import to ensure that text boxes are maintained...