Forum Discussion

sayali-sathe1's avatar
sayali-sathe1
Community Member
5 years ago

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 J...
storyline 360
MarkMarino's avatar
MarkMarino
Community Member
16 days ago

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.

 

  • MarkMarino's avatar
    MarkMarino
    Community Member
    15 days ago

    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.