Notes tab – Font appearing distorted in Storyline 2

Fonts appear to be rendering differently in Storyline 2, when compared to Storyline 1. 

Please refer to image below of the Notes tab in Storyline 1 and Storyline 2, both using the exact same font settings: Arial 11pt 

The font in the Storyline 2 output appears narrower, thus making the font appear more like 'Arial Narrow' rather than 'Arial'. 

The font in the Storyline 2 output also appears taller, thus making the content occupy more space than in Storyline 2. 

Furthermore, the width of the text area also appears to be narrower in width compared to Storyline 1. Please refer to line 4 in the Notes below, where the word 'eium' fits on the line in Storyline 1, but does not fit on the line in Storyline 2. 

Can the Storyline team please advise why the appearance of fonts in the Notes tab has changed when publishing in Storyline 2?

Distorted font in Notes tab in Storyline 2

I have attached two sample story files so you can check that both fonts are exactly the same in development, but appear differently when published. 

 

7 Replies
Christie Pollick

Hi, Kuriko - Thank you for providing your files, and I will take a look at them. In the meantime, could you please check a few things to rule out some common issues? Please make sure you are working locally as described here, and you may want to try importing the file into a new file. If you are still having issues, you might want to try to repair Storyline. Also, could you please ensure that you are utilizing the most recent SL2 Update? Info on Update 5 can be found here

Christie Pollick

Hello again, Kuriko - I went ahead and published your files and viewed the published output in Tempshare, and I am also seeing the issue you described. I checked, and this is a known issue in with our QA team for further exploration. I am going to add your thread to the ticket, and although I cannot provide a timeframe for resolution, one suggested workaround would be to use the "clear formatting" button in SL2, and the notes will return to the default, but you can't change the font, add bold formatting, etc. I will be sure to update here with additional information when I receive it. 

Kuriko A

Hi Christie

I'm glad this bug has been reported to the QA team already.

In relation to your suggested workaround, it doesn't work. Did you test it?

When applying the 'clear formatting' setting to the Notes tab in my Storyline file, it does not change the font back to default. It keeps it in Arial font, but just changes the size to 9pt instead of 11pt. You can test this in the file I provided previously.

You will notice that the original issues still remain: 

1) The font is taller than regular Arial font

2) The font is narrower than regular Arial font

3) The width of the text area is narrower than Storyline 1.

The only way that your workaround appears to work is if you create a brand new slide in which you have not previously adjusted formatting on the font in the Notes tab, and then create your slide again from scratch. Then, type the content into the Notes section, and it will be in the default font: Open Sans 9pt. Is this what you are suggesting – that in order to fix the issue we would need to create a new blank slide and basically recreate our slide from scratch in order to fix the font on the Notes tab?

Furthermore, even if this workaround did work, it is not a very useful workaround as it says that the Storyline Notes tab doesn't work with any font other than 'Open Sans' font. I don't imagine many people are going to change their organisation's style and branding guides to match Storyline's default font. Therefore, Storyline needs to be able to work with fonts that are specified by the user because these fonts are usually required by an organisation's strict branding and style guides. 

 

 

stanton mackellar

Hi there. I am experiencing some issues similiar (the same) as those discussed here where spacing or font kerning is randomly being applied to letters making spaces appear in the middle of words.

You mentioned that the developers were looking into this... have they come up with a solution yet? I am using Open Sans.

Thanks

Stanton

 

Christie Pollick

Hi, Stanton -- Thanks so much for touching base. This matter is still under investigation by our QA team, so while I do not have updates to share at this time, any info I am provided will be shared here as it is received. As since you have replied in the comment thread, you are now subscribed to this post and will receive notification via email. Your patience is appreciated.