English to Hebrew Translation Problem
Nov 05, 2014
Hi! is there any of you guys encounter same problem with mine? I just translated my course from english to hebrew, I have successfully imported the translated hebrew document, but unfortunately after importing, the content is not translated to hebrew, instead this character below shows up as replacement of hebrew language:
-"ðáéèä äéà ëàùø äæøò îöîéç ùåøù äòìéåï. éùðï ãøëéí øáåú ëãé ìðáåè æøòéí, àê äãøê äôåôåìøéú áéåúø ììðáåè æøòéí îöéáä àú äæøò áéï îâáåú ðééø øèåáåú. æä àîåø ì÷çú áòøê 1-7 éîéí, ëì òåã äæøò ùìê éäéä îú, àå æ÷å÷ ìéåúø èéôåì."-
This problem is just for the content, because when I tried to translate the player to hebrew it works. I already configure the right to left option but still don't work.
Do I miss some process in translating to hebrew? Any help or suggestion is much appreciated.
By the way I'm using articulate storyline 2.
Thank you,
Poenapi
31 Replies
Hello Poenapi!
Please make sure that you are working locally as described here.
I did a test file and was able to use the translate feature. I used Google Translate to translate the text in my file to Hebrew, and it did import Successfully:
Could you share the exported word doc here, or a page or two so we can test this from our end?
I would check the target font you have set in the course, may be you need to change it to one that has hebrew characters
Hi Emily,
Thanks for the quick response to my concern. Yes, I follow the guidelines as instructed from the link you provided. But it doesn't work. I used google translate in translating my content to hebrew and translation is successful, it just that when I imported the document to articulate, my problem appears.
By the way, I have attach here a sample of the translated document. It's already in hebrew.
Thanks,
Poenapi
Thanks Phil, I will also consider your suggestion.
Hello Poenapi!
Unfortunately the file is giving an error when I try to open it.
Can you attach the exported file before it is translated?
I have also found that there are different versions of Hebrew fonts depending on whether they are designed to work with certain word processors like Davka or if they are more generic. I have found that Adobe Hebrew or a font called David seems to be more compatible.
Finally, some of the fonts seem to only display the Hebrew when you have changed the keyboard configuration in Windows from an English keyboard to a Hebrew keyboard.
I hope that some of this helps.
I opened your Word file and all of the Hebrew is showing correctly . Since I don't have your .story file I could not test the import.
Hi Emily,
Here's the original file before translation.
Thanks
Thanks for your input Brent. I have attach here first few lesson of our course. Thanks for all your help guys. I'm looking forward for the solutions of this problem.
I am having the same problem. I made a very simple one slide, one phrase file. When it comes in it is displaying gibberish. I have a number of different Hebrew fonts installed and this seems to make little difference. I even tried it with the Hebrew keyboard active. When I type Hebrew text directly into the file, it displays fine with no issues so I know that the display fonts are active.
I am at a loss. I hope the Articulate team can help.
Hello Brent!
Unfortunately I am not able to recreate the issue on my end with a new file.
See attached. It did import successfully:
The only difference is that my text is in Open Sans font (the default) and your was in Arial.
However, I changed mine to Arial and it worked as well.
Poenapi, you may want to open a support case for this.
Emily:
Your files worked for me as well. I can't see anything that you are setting up differently than me. Did my simple set of files work on your machine?
By the way, I originally had Open Sans in the example and it probably changed when I was trying different fonts to see if it made a difference.
Are you changing any settings to the Storyline interface or player that are different from the standard default settings?
Your file did work for me as well. And no, I am not changing any settings. I opened a new file, inserted a text box, and typed, using all defaults.
When I try the import, I noticed that I get garbage and the font is no longer identified in the font bar. I inserted a screen shot below. I'm not sure what is happening. The English was, "Where is your house?" and the Hebrew should be "?איפה הבית שלך"
I started from scratch again with a new file and it imported correctly. The only difference that I can remember is that I saved the English .story before trying the translation. The first time I tried a quick import without first saving the English file. Do you think that could make a difference?
Hello Brent!
I just did a quick test file and did not save the file before translation, and it imported correctly. Then I saved one as well, and that imported correctly too.
Hi Brent and Emily,
Thank you for helping me out from this issue. I tried both of your samples, and Emily's sample works at my end when I imported it to articulate. So I decided to export the content again from Emily's example to look for possible settings that is different from Brent's output. But unfortunately it didn't work. I get the same issue again. Please see attached files for working and not working example. And the attach doc is from the new exported content from Emily's example.
Hello Poenapi,
I would suggest to open a support case to see if this may be something specific to your files or computer.
Okay. Thanks Emily. I will do that.
I will keep an eye out for the case as well to see what could be causing this issue.
Thank you, Emily. It's hard to troubleshoot when the behavior is so erratic.
I agree! Hopefully we can get to the bottom of this soon.
Thanks for both of you, for taking my issue seriously. I already have talk to my client regarding this issue, and he will be the one to contact articulate since I'm not the owner of my license. Hopefully we can get a positive reply from articulate support team.
thanks for the update, once a case is submitted, you can share the case number here so i can follow along.
Did this case ever get resolved? I'm having the same issues in Storyline 360.
Hi Sandy,
I do not see a case associated with Poenapi Cenas, so I don't have any updated information to offer there.
Can you explain more about the issues you're seeing in Storyline 360? Are you also using English to Hebrew translation, or another language altogether?
Hi Alyssa,
I was having trouble when pasting Hebrew directly from Google Translate into the translation word document. It would appear as random characters in the same way as Poenapi described.
I found that if I pasted it into the document without choosing to 'Use Destination Theme', I didn't have the same problems with the characters. Though obviously this did affect the formatting of the text, initially.
I also had the same problem and found the same solution for Arabic.
This discussion is closed. You can start a new discussion or contact Articulate Support.