Arabic Translation Issues - Translation Table
Dec 07, 2015
Looking for someone that has experienced issues with importing Arabic translation tables into Storyline...
We have the translation table from the translation vendor but there are issues making it impossible to import:
- Translated column on the left with ID column on the right did not work
- Translated text appears jumbled and not Arabic characters
- ID Column text is reversed when copy/pasted left of Translated Text Column
- When Style is added that reverses ID column to read left-to-right, importing does not work (nothing changes in storyline file)
- Translated Text is reversed when copy/pasted right of ID Column that is read left-to-right
- Importing works because IDs are correct, but text within Storyline is jumbled and not Arabic text
Any ideas would be much appreciated!
24 Replies
Hi, Tiffany -- So sorry to hear that you are experiencing issues! Perhaps you may want to take a look at this thread that seems to have posed a similar question and see if any of the advice shared does the trick for you. This thread may also be of some assistance. Please let us know if issues persist! :)
Christie,
Thank you for the response. The issue still persists. I have gone through all of the Arabic-related threads on here. One of which indicated that the Articulate staff was able to copy/paste Arabic text from Google Translate but not from the translation table. I am having that same issue. The thread did not indicate what the resolution was, though.
In fact, the slide titles that appear in the menu are correctly placed in Arabic, but the screen text is not - it's all jumbled.
Hi, Tiffany -- Would it be possible for you to share your file so that we can take a closer look for you? Please use the ADD ATTACHMENT button in the bottom left of the reply box and browse from there. :)
Christie,
My translation vendor entered a ticket with Articulate this morning - case #00706898
Many thanks, Tiffany, for sharing that update and for providing your case number. It appears that what I have provided below is the latest information concerning your case, and as such, I wanted to share non-confidential updates here for others who may be experiencing a similar issue and could benefit from the suggested workaround:
Thanks for contacting Articulate Support!
I understand that you're having issues with graphical anomaly on Arabic characters when importing a translated document in Storyline 2. We were able to duplicate your issue and I have submitted your case to our Quality Assurance team for their review. As a workaround you can try re-translating the existing Arabic Word document using Microsoft's Online Translation Service. Here's how:
NOTE: Tested to work using MS Office 2013.
1. Open the existing Arabic Word document.
2. Highlight all of the document's content.
3. Right click > select Translate. The "Research - translation pane will open on the right side of the document.
4. Set the languages to translate from "English" to "Arabic"
5. Click on the translate button (Green arrow). On the notification window that pops up, click on "Send" button. This will open up your web browser and display the translated texts using Microsoft's translator service.
6. Copy all the texts and replace the one's from the original file.
7. Save the document and import it to Storyline 2.
Unfortunately, I cannot offer a time frame for when or if this issue will be resolved so please continue to take advantage of the workaround if you encounter this issue in the future. I'll keep you posted on any updates on this issue.
Hope that helps! :)
Unfortunately, using the workaround changes the existing translation, which was done by an in-country linguist versus a computer.
Few additional notes:
Going from English to Arabic and copy/pasting the content flipped it to left-to-right and a style had to be applied to the column in order for it to appropriately read to right-to-left.
Going from English to Arabic caused the computer to translate the company name and other proper nouns that were in English from the linguist's version. Going from Arabic to Arabic alleviated this issue but still caused the original translation to be modified incorrectly.
Any additional suggestions?
Hi, Tiffany -- Thank you for your follow-up! I went ahead and added your most recent response to the ticket and alerted the Support Engineer who is working on the ticket. I will keep you posted on any updates I receive. Many thanks for your patience! :)
Any luck on an update today? I have a client anxiously awaiting their course...
Hi, Tiffany -- It looks like our Support Engineer Victor sent an updated translation doc to Michael from your Translation service who submitted the Support case, however, it is stated in the ticket that "It is possible that there's an underlying texts formatting issue which causes the error after the translation is done."
So as of Victor's last email exchange with Michael, he said:
"I'm sorry to hear that there's been some drawbacks using the workaround I've shared. I've ran several more tests but couldn't find another alternative. I'll keep an eye out on this case and keep in touch with you just as soon as we receive any updates from our Quality Assurance Team."
Any developments so far?
Even i have the exact same issue...If this is resolved please post the resolution here.
My client is on my head right now!
My translation vendor had me export the translation table as the .xliff - it is one of the options when you choose Translation - Export - Save as type: _______. The vendor had the ability to open the file, translate it, and import it back in. Of course, we had to pay for that service since we usually do translation imports on our own :(
Thanks for sharing an update with Suraj here, Tiffany, and although it was not ideal, I am glad to hear your issue got sorted out.
And if you are under a tight deadline/pressure from your client, Suraj, I wanted to mention you are always welcome to work with our Support Engineering staff directly by way of this form. I'll be sure to monitor their progress in order to share updates here for others who may benefit. :)
Thanks for this useful tip! Maybe next time i'll try this! :)
I found an interim resolution for my problem....Change the font of all the translated text in your translation table to Arial Unicode MS. Change the text boxes in your storyline to Arial Unicode MS as well - start copy pasting the text without any issues!
Excellent, Suraj -- so glad to hear you found a workaround and thank you for sharing it here, as well! :)
Hi! I'm experiencing this exact problem now with Arabic. I have followed all the instructions in the discussions and none of them fixed the problem with the menu. Has any progress been made on fixing this issue with Arabic?
Jill, we ended up using XLIFF files versus translation tables in Word and it seemed to work.
Hi! This is my last resort solution. My issue is only with the Menu in my course. Where would I paste the new version of the words in Ariel Unicode ms? Can you provide a bit more detail please?
If you go into the Player Menu, you can select the text labels button. This allows you to copy/paste the custom text for the buttons. Or, you can go into the Player, click on the menu button, then, double-click on the titles that you want to modify.
Hi I am having issue with Arabic course too! Can anyone suggest what to do about this? when user enter the name in the data field the name is flipped when the user reach the result slide. I am not sure how to work this out since we've been trying everything that needs to be done in regards with the arabic language course.I attached screenshots of the slides
Hello, Poloy,
Thanks for giving us a head's up about this. We're seeing the same thing, and it appears to be a software bug.
Let me get this to my team so we can begin looking at next steps. I'll keep you posted on any new developments!
Hello, everyone!
To follow up on Alyssa's post, I'm so happy to share that we just released Build 3.33.20697.0 for Storyline 360. It addresses the issue where variable references in right-to-left text displayed in the reverse order.
To see all the enhancements this version has to offer, follow these steps to update your software. Thanks for bringing this to our attention!
HI, is this new build fix the issue in Rise?
Hello Sara!
This fix was released for Storyline 360 since we don't have variables in Rise 360. If you're running into an issue with text in Rise 360, we are happy to help. Just connect with a Support Engineer to get started troubleshooting!