I've submitted a support ticket, but other people on my team have opened some weeks ago, and we're still not really seeing any results.
We are launching a 5 module training in Lebanon on Saturday, and noticing that although Articulate urged us to use Arial Unicode MS, we are still experiencing many issues.
The fonts display correctly in the source files. They are Arial Unicode MS. Although, when publishing, they are always shifted and distorted, making this illegible in Arabic.
Many other similar topics say that Arial Unicode fixes their issue...but it doesn't seem to be fixing ours. We don't have many days left to fix this showstopper.
It's not solved 100% though. There are still issues. Renz is looking into it, but I doubt we'll find a solution soon. I find it weird.
If Arial Unicode works on iSpring in all browsers, why not Storyline? If it's a browser compatibility issue...why do the iSpring publishes function well in all browsers?
Hi there, Michael. Sorry for the trouble this oddity is causing.
I shared your latest post with Renz so that we can gather more insight and look into other approaches. Look out for a follow-up email from him shortly!
We found an older font, version 1.5. I uninstalled the newer version of Sans Serif, installed the older one from the windows XP era, and unchecked "USE MODERN FONT"
8 Replies
Many other similar topics say that Arial Unicode fixes their issue...but it doesn't seem to be fixing ours. We don't have many days left to fix this showstopper.
I did a test using iSpring Arial Unicode MS, same font....no problems across browsers
Seems this is solely a Storyline problem that has been going on for many years.
It seems that unchecking Modern Text in the Design Tab may be fixing this issue - for those of you who are having the same issues.
Hi Michael,
Thanks for keeping us up-to-date on your findings.
I see that you were able to reach out to our support team as well and work directly with Renz.
I appreciate you sharing your solution.
It's not solved 100% though. There are still issues. Renz is looking into it, but I doubt we'll find a solution soon. I find it weird.
If Arial Unicode works on iSpring in all browsers, why not Storyline? If it's a browser compatibility issue...why do the iSpring publishes function well in all browsers?
Hi there, Michael. Sorry for the trouble this oddity is causing.
I shared your latest post with Renz so that we can gather more insight and look into other approaches. Look out for a follow-up email from him shortly!
Thank you for continuing to work with us.
So, Microsoft Sans Serif was not working
But now it is....for now.
I had Microsoft Sans Serif font version 6.69
We found an older font, version 1.5. I uninstalled the newer version of Sans Serif, installed the older one from the windows XP era, and unchecked "USE MODERN FONT"
This seems to be resolving the issue...for now...
Thanks for chiming in to share what is currently working for you, Michael.
I have added this note to the report as we continue investigating. This conversation is attached as well so that we can share any updates.
This discussion is closed. You can start a new discussion or contact Articulate Support.