Forum Discussion
Japanese localisation output size increases considerably than the other languages output
We have created a course in 11 languages using storyline. One in English, and the rest are localization of the same English file. English output file size is 120mb.
Out of which, when we publish Japanese source file, the output file size increases considerably (i.e. 135 mb). All the other output files are of same size as english output. i.e. 120 mb.
Can someone please help.
Regards,
Sayali S.
17 Replies
Vielen Dank Jürgen!
Interesting to hear you have an extract script and see the output and your analysis, very nice!.
I suspected it was something Storyline was doing.
I will log a case and point them to this forum.
Thanks again.I am having this same problem but my published file set is coming out at 269mb in Japanese compared to the English which is 4mb. My client is not happy as this effects Japanese, Korean and Chinese (Simplified and Traditional)
the storyline otf to woff converter has a strange bug
example
- NotoSansJP-Regular.otf (4.442 MB) - full char set (windows 11)
- NotoSansJP-Regular.woff (3.37 MB) - full char set (found on github)
- NotoSansJP.woff created by storyline 14 MB converted to base64 ( x 1.33) = 18.6 MByte !!!!Hello! We are facing the same problem with Noto sans cjk font.
May I ask if there a font recommended for Japanese? it cause so much time to load and we think we should change the font in the file...
Many thanks.
Hi Yu Ying Lin,
Thanks for reaching out and I'm sorry to hear you've hit this snag!
I've seen that using MS Gothic font can make the file size smaller. If you're comfortable sharing your file, I'd be happy to do some further testing on my end! You can upload it here or share it privately in a support case. We'll delete it as soon as troubleshooting is complete.
We have been experiencing this issue for the last couple of years for our localized content. Our output.min.css files balloon from a megabyte or two to like 150MB - 200MB... and it's definitely Noto Sans font family that causes it... for us it has hit our Chinese and Vietnamese languages, we don't currently localize to Japanese.
I filed a bug report about this last year and never got a resolution.
Jürgen's post is the only clue I've seen about this... that the woff generator in Storyline broken. Apparently it's still broken b/c I'm seeing this bug in latest version of SL (v3.103.x)
I would love to know if there's been any progress on resolving this bug as it makes the localized output nearly un-usable... the browser takes forever to load & parse a 200MB CSS file.
For a workaround, we recently tried font substitution... we saved out a duplicate of our .story file specifically for our Chinese audience and then we used Storyline's font substitution feature to replace all instances of NotoSans CJK fonts with SimSun. This appears to resolve the issue with the ballooning output.min.css file. I am working with our Chinese counterparts to make sure this method works. The only problem we have run into with this is that we had to replace all NotoSans CJK font weights with regular weight SimSun, so the styling of headers was removed.
SimSun is specifically for Chinese and it is included with Windows... I don't know if there are other fonts that could be substituted for Vietnamese or Japanese as we currently don't localize to those languages.
Regardless, it would be great if Articulate fixed the Storyline bug that causes it to explode the NotoSans CJK conversion to epic proportions in the output.min.css file.
