Forum Discussion
Storyline360, Animation and GSAP ( Greensock )
Hi,
Trying to figure something out in SL360 i stumbled upon the ds-bootstrap.min.js file thats added to the lib/scripts folder when publishing a Storyline360 file. In that file are GSAP(Greensock...
interesting news - the coding depends on which characters really used in the text of the complete course (with the same font)
tests are made with Firefox - therefore the "good" view of non-printable characters
decoding
txt = txt.replaceAll("\uE000", "f");
txt = txt.replaceAll("\uE001", "ff");
txt = txt.replaceAll("\uE002", "fi");
txt = txt.replaceAll("\uE003", "fl");
txt = txt.replaceAll("\uE004", "ffi");
txt = txt.replaceAll("\uE005", "ffl");
Example 1: in the course is used "f – ff – fi – fl - ffi – ffl (Stoffflasche)"
Example 2: in the course is used "f – ff – fl - ffi – ffl (Stoffflasche)" <- no "fi" used (same decoding)
=> decode of "fl", "ffi", ffl" has different results!
=> don't use fonts with legatures, if you want to grab the vector text !
=> you can use e.g. font "Articulate" (no ligature at all) for the vector text
Or you could add all the ligatures in an offstage text box in the first slide which would/should make it predictable.
Just read it properly I think I will use Articulate font which would work for this.
Sent from my iPhone
Your ligature test.story is very helpfull...as it makes it easy to check whether any given font has issues with them in Storyline.
