Forum Discussion
Noto Sans Thai font not displaying correctly
I am working on a module in multiple languages and we have had recurring issues with fonts not displaying correctly. To remedy this we have been using language-specific versions of Noto Sans.
Noto Sans Thai is not publishing correctly in Review 360.
When viewed in the SL file it displays fine - see image 1
When viewed in Review 360 in Chrome one character appears bold - see image 2
When viewed in Review 360 in Firefox the same character is corrupted - see image 3
When published and viewed in SCORMcloud it is the same as image 2
The fonts are installed correctly and I have published both locally and from our server and the problem occurs with both.
Any advice would be appreciated.
12 Replies
Thanks for your reply Dominik. It less noticeably, but still there. Thanks for the suggestion. We have tried many fonts and they all do it so I guess it will be a matter of choosing the less harm until this is fixed.
Hi, just wondering if there are any updates on this.
Is there any font that doesn’t display some Thai characters in bold on its own?Sorry to hear you're encountering this issue with Thai font rendering in Storyline!
I can confirm we still have this behavior logged as a bug in Storyline. This bug causes symbols to display differently for Thai language fonts. I've included you both in the bug report being tracked, so we can notify you as soon as a fix is ready.
In the meantime, as a workaround, we suggest exploring different font types as Dominik1 touched on. This behavior can vary depending on which font is being used. For example, Noto Serif Thai, which we find renders more accurately during playback.
Also, we've seen this behavior improve in some projects set to Display Accessible Text by Default.
Thank you for your patience. I'm sorry if this has been slowing you down!
Hi Aukalen,
We also had issues with Thai fonts in the past. Currently we are using Tahoma, as it seems to give the best results for us.
Maybe give this one a try.
Best,
Dominik
Hi, all!
I have some great news to share! We just released a new version of Storyline 360 (Update 102), which included a fix for the issue that caused symbols to display differently for the Thai language.
To take advantage of this update, launch the Articulate 360 desktop app on your computer and click the Update button next to Storyline 360. You'll find step-by-step instructions here.
Please let us know if you have any questions by posting here or reaching out to our Support Engineers directly.
Hi,
Was this issue fixed only for update 102?
My understanding is that it would be fixed for update 102 onwards, however, this still persists (some TH characters with Noto Sans Thai are displayed in bold). I am on update 104. The workaround of the Accessible text works though.
Thanks!
Hi PatrizioPucci-8!
Sorry to hear that Thai font from your Storyline course is not rendering properly!
Your understanding is correct. When we release a fix for a Storyline bug, that fix should remain in place for subsequent versions as well. I'd like to connect you with our support engineers so they can work with you directly on this setback. I've opened a support case on your behalf. Also, I've sent you an e-mail containing an upload link you can use to share your .story file privately with our team.
We can continue the conversation through your case to keep all information in one spot.
We had a huge problem with Noto Sans... we're waiting for a fix. Check to see the size or your styles.min.css file (I think that was the problematic file)... we found that ours ballooned to like 200MB with the Noto Sans bug which was causing all our courses to bog down. Our temporary fix was to remove the language from our course.
Unfortunately removing the language is not an option. We work in all languages and we need a reliable font that can be substituted in Storyline.
Hello MarkJones-1a149,
Thank you for reaching out!
What you are experiencing is related to a known bug on our end where we find the symbols display differently for Thai Language. I have added this discussion to the bug report so you can be informed of a fix.
- Are you experiencing this behavior with any other courses where you are using Noto Sans Thai or is it isolated to this course?
As a workaround, we recommend that folks turn on Accessible Text for their courses.
It looks like your image attachments did not send. No worries! Feel free to send them along, and I can add them to the existing bug report.
Looking forward to hearing from you!
Please see attached the images. This has happened with other courses and we've also had issues with Noto Sans in Chinese as well. Is there a font that will work consistently with other languages in Storyline as we work in other languages a lot of the time? Noto Sans is reliable with most other software except for Storyline.
In our particular case, it was only affecting the Chinese text localization, the Thai was not causing the issue.
