This is the first time trying to import Arabic, of course right to left. The translated file has the text set right to left and I set the option in Storyline for right to left. The import status goes very fast and nothing changes at all.
I tried to copy and paste from the Word document, and wow does it rearrange all the text completely different!
The other languages have gone very well with no problems. Has anyone done this successfully?
This is the first time trying to import Arabic, of course right to left. The translated file has the text set right to left and I set the option in Storyline for right to left. The import status goes very fast and nothing changes at all.
I tried to copy and paste from the Word document, and wow does it rearrange all the text completely different!
The other languages have gone very well with no problems. Has anyone done this successfully?
Adding an image of what happens when you paste in the text.
It's hard to tell from that image - but is the text that you're showcasing a part of a pop up or coming from the player labels? Those are handled differently as described here.
The image is the Word translation import file, and in the slide for storyline you have to look hard to see it has rearranged the text that I copy/pasted into it. The (EVC) text is broken up for example. If I use the backspace key to delete the text, the cursor jumps around in the text like crazy.
The import feature simply does nothing so I wanted to see how it would be to paste it in.
The source file and translation file are here if you like.
Yes - you'd want to make sure they were all set for the right to left within the text box. What do you mean by jumps around in Word also? You may want to look at conducting the involved repair of Storyline detailed here as it could help with the Word issues as well.
Thanks for the additional information. I would like to see a bit more in regards to how the import happens - and if you could record a quick screenr showing me the behavior I think that would be really helpful. You could send me the link in a private message - or if you'd prefer I can also send you directions on how we could take a look at this outside of the forums through a support case (which you're always welcome to connect with our Support engineers here).
No worries - I found it. For my reference it's case # 00408720
Also, I see that Regil shared the following:
Usually translation fails because of the Id on the translation document was accidently changed. I checked your translation document and the Id became Aligned Right. Perhaps this is the reason why translate failed.
I exported a new Translation file and copied the translated column from your translation document. I then imported it to Storyline and it worked.
Please see the following updated .story file and also the updated translation document (I did not include them here.)
If you need any other help, please feel free to let Regil or I know.
I did not get anything directly from Regil. I just tried what was suggested here and transferred the translations to a new export version.
It did work to some degree, but left many blank text boxes/shapes in main slides, quiz feedback sections and such.
The font changes to Times New Roman in Word and then in the import of course. I would need to fix it in Word and try another import to see if that helps.
If you didn't get an email, you may want to check your junk/spam folder for something from Support@articulate.com.
I've included the update you shared here also with Regil, but if you see some blank text boxes, it's possible something was missing within the file as he shared in regards to the Id on the translation document being modified. Since I wasn't able to share the updated document with you, I'll see if he can resend the email as well.
13 Replies
Adding an image of what happens when you paste in the text.
Hi Rick,
It's hard to tell from that image - but is the text that you're showcasing a part of a pop up or coming from the player labels? Those are handled differently as described here.
The image is the Word translation import file, and in the slide for storyline you have to look hard to see it has rearranged the text that I copy/pasted into it. The (EVC) text is broken up for example. If I use the backspace key to delete the text, the cursor jumps around in the text like crazy.
The import feature simply does nothing so I wanted to see how it would be to paste it in.
The source file and translation file are here if you like.
I looked at the tutorial link you gave me.
I did not know about that little button for the text box to set right to left. Do I have to do that through the entire course manually now?
I think this goes deeper than Storyline. The cursor jumps around a lot within Word also. I tried adding Arabic support but that did not seem to help.
Hi Rick,
Yes - you'd want to make sure they were all set for the right to left within the text box. What do you mean by jumps around in Word also? You may want to look at conducting the involved repair of Storyline detailed here as it could help with the Word issues as well.
I re-installed Articulate and there does not seem to be much that changed.
1. The translation import runs faster than normal and says it was completed, but nothing changes.
2. I cannot highlight the Arabic text within the text boxes at all. I can move the cursor and delete text however.
3. Now if I copy/paste from the Word translation file, it seems to be OK and no longer rearranging the text.
I really need the translation import to work, and have it change the text boxes to right to left in the process.
This is the first course where I used the variable references, and that looks like it will still be an issue I guess.
Thanks for the help so far!! It is greatly appreciated and I am still a big supporter of Storyline.
Hi Rick,
Thanks for the additional information. I would like to see a bit more in regards to how the import happens - and if you could record a quick screenr showing me the behavior I think that would be really helpful. You could send me the link in a private message - or if you'd prefer I can also send you directions on how we could take a look at this outside of the forums through a support case (which you're always welcome to connect with our Support engineers here).
Ashley,
I submitted a support case, added a quick video as the security settings will not allow Java and referenced this string as well.
Thanks again.
Thanks Rick - do you have a case number so that I could follow along?
Sorry Ashley, I guess I did not write the number down and there does not appear to be a way to look it up.
Hi Rick,
No worries - I found it. For my reference it's case # 00408720
Also, I see that Regil shared the following:
Usually translation fails because of the Id on the translation document was accidently changed. I checked your translation document and the Id became Aligned Right. Perhaps this is the reason why translate failed.
I exported a new Translation file and copied the translated column from your translation document. I then imported it to Storyline and it worked.
Please see the following updated .story file and also the updated translation document (I did not include them here.)
If you need any other help, please feel free to let Regil or I know.
Thanks Ashley,
I did not get anything directly from Regil. I just tried what was suggested here and transferred the translations to a new export version.
It did work to some degree, but left many blank text boxes/shapes in main slides, quiz feedback sections and such.
The font changes to Times New Roman in Word and then in the import of course. I would need to fix it in Word and try another import to see if that helps.
Hi Rick,
If you didn't get an email, you may want to check your junk/spam folder for something from Support@articulate.com.
I've included the update you shared here also with Regil, but if you see some blank text boxes, it's possible something was missing within the file as he shared in regards to the Id on the translation document being modified. Since I wasn't able to share the updated document with you, I'll see if he can resend the email as well.
This discussion is closed. You can start a new discussion or contact Articulate Support.