Forum Discussion

KellyNott-ce1c0's avatar
KellyNott-ce1c0
Community Member
20 days ago

Font issues in Storyline when enabling browser translations

We are trying to leverage auto translation tools within Microsoft Edge Browser because of the number of courses, languages, and versions of content we need available. The auto translation tool works well within Articulate Rise, but for some reason in Storyline it causes issues with spacing within the font and makes it unusable for a learner trying to review in another language. 

Has anyone encountered this before? We are seeing it with both in house built and vendor built courses. 

Going to test out other fonts, but it feels like it might have to do with the SCORM packaged content? 

Thanks for any insights! 

accessibility
advice
storyline 360
  • Jürgen_Schoene_'s avatar
    Jürgen_Schoene_
    Community Member
    20 days ago

     

    short version: it's not possible with storyline

    long version: there are two versions of text in storyline

    • svg text (single-line)
    • html text (single- or multi-line)

     

    svg text

    • is use in storyline for all 'normal' text on slides
    • for svg text every single char is positioned to x, y while publishing
    • if the text is changed afterwards, the new chars are not matching the positions of the orginal chars - the font does not matter
    • for slide text with %variables% included, there is a special solution without precalculated x, y positions

     

    html text

    • is use in storyline for menu and accessible text
    • there may be problems with the text length subsequently generated translation

     

    in Rise only html text is used

     

Related Content