Trouble using Hebrew fonts - Storyline 2
Jul 09, 2015
Hey,
I guess not many of you have encountered this problem, since it happens only using hebrew fonts.
Everytime I try to use punctuation mark or using English and Hebrew in the same sentence - The publish "goes wild".
Question mark turns into another letter, or a bullet or even attached/overrides words....
Sometimes you can see the problem on the stage, while working - and on other times it will surprise you on the publish.
It didn't happen on Storyline1. It happens only on Storyline2, even though I'm using the latest update possible.
HELP :)....
Maytal.
13 Replies
Hi, Maytal -- Sorry to hear of the issues you are experiencing. Please see this information on Supported Languages in Articulate Storyline, including Hebrew. You may also find this article on language translation helpful.
If issues persist, you may want to run through the following troubleshooting steps. Please make sure you are working locally as described here, and you may want to try importing the file into a new file. If you are still having issues, you might want to try to repair Storyline. Also, could you please ensure that you are utilizing the most recent SL2 Update? Info on Update 5 can be found here.
You are welcome to submit a case with our Support Engineers if you would like them to take a closer look using this form.
Hey Christie,
Unfortunately your answer doesn't help.
Here's a print screen of same text, same font, same size different Storyline versions (2 VS 1).
Maybe it will help in presenting the problem.
In Storyline 2 (on the left side) - as you can probably notice, the question mark overrides the word behind it. It doesn't happen with the second word - but you can not tell when and how will it happen. Sometimes the problem occurs only while publishing.
As I wrote before, it gets even worse while using bullets, English and Hebrew on the same sentences and while using different fonts (that were purchased and work absolutely fine in Office and in Storyline 1).
I'm not a new user. I'm using Storyline for more than 2 years now.
Also I made sure that I have the latest update possible for Storyline 2.
The problem I'm presenting regards to many more Hebrew users, It came up
with some colleagues of mine.
Please help us.
Thanks in advance,
Maytal.
Hi, Maytal --
Thanks for your response and I have gone ahead and created/submitted a Support Case ticket, so you will be hearing from someone shortly. I thought it best that our Support Engineers take a closer look, as they may have suggestions beyond what I would be able to provide at this time. As always, we aim to provide the most comprehensive support possible for our valued customers and community members, and I will look for your case to follow along. :)
Thank you very much :)
You're welcome, Maytal. I see that Abel is doing some testing for you with respects to your case (#00602421), and I am sure he will be in touch with additional information as soon as possible
Hello,
Are there any news regarding this very important issue?
Unfortunately, It is not possible for us to use SL2 without solving it :(
Hi Yael! I do not have an update to provide on this issue at this time as it is in the hands of our QA Team.
Ok, thank you
Maytal, did you find any solution? Does this happen with all fonts?
Hey Yael,
My colleagues and I have discussed this spesific matter on a facebook group we're running (Israeli Storyline users):
https://www.facebook.com/groups/964532846924576/997677883610072/?notif_t=group_activity
We came to the conclusion that it has to do with the type of font you're using.
SL2 can only work with web hebrew fonts, many of the print hebrew fonts make all kind of different bugs.
Thanks for sharing your findings as well as a group to connect for Yael :)
Great, Thanks a lot Maytal.
Leslie- This of course is still a huge problem for Israeli users, so please let the QA Team know :)
Hi,
Is there any news regarding this issue?
It's been a while and no one wrote anything about that.
the bug still exists
thank you,
Yael
Hi Yael! So sorry that we do not have any news to share at this time, as the issue remains with our QA team. Your patience is appreciated, and since you have replied to this thread, you should now be subscribed. As such, you will receive notification of any additional updates shared here at that time.
This discussion is closed. You can start a new discussion or contact Articulate Support.