Forum Discussion

MarineDEMAISON's avatar
MarineDEMAISON
Community Member
4 months ago

Important bug when publishing Korean fonts

Hello all, 

We have a module that we translated to Korean and while everything is fine in Storyline, once published, wether in Review, web, or SCORM version, the published text is absolutely meaningless.

For more info, see the attached pictures. I have uploaded a test .story fil, that enables to reproduce the problem. In the attached picture Font_problem_when_translating_to_Korean, on top you have the fonts in SL, on the bottom the published result. In this case, the Acumin font translated well, and the Calibri got messed up. Both ARE unicode fonts. In our original project, the Acumin font gets messed up as well.

I'll try switching for native Korean fonts and keep you updated, but it would be great if this bug could be resolved, because for instance Chinese works well.

Have a great day,

storyline 360
  • MarineDEMAISON's avatar
    MarineDEMAISON
    Community Member
    4 months ago

    OK, I've kind of solved it using the search/replace fonts tool in Storyline and Switching European fonts for Pretendard.

    I'll keep an Eye out for Chinese and other non-latin tranlsations to see if this problem reoccurs.

Related Content