I am just publishing a module where I have used variable text - (learners input their name and then it is used throughout).
When I publish I have noticed a consistent error - whenever there is variable text the font changes from Articulate (which I set as the theme font) to Times. Happens in every instance. My client hates Times, and I am not too far behind her.
As this is an old thread about a problem that has affected many, many, many... people, would you please provide more information about where manual tweaks need to be made, and what the tweaks look like?
Hi, Naito -- If you would like to share your file so Pete and others can take a look, I just wanted to mention that you are able to do so by using the "ADD ATTACHMENT" button in the bottom left of the reply box. You will then be able to browse for your .story file and upload from there! :)
Hiya, just to share on this. In order to see my font for variables, in this case Dax-regular, I changed the player.css, lines 12, 13, 15 to commented out so they don't inherit font-weight, font-style, font-family. I don't know if all 3 were really necessary I could have probably done the same with just font-family, but it 'appears' to work for me. I also changed line starting 476, added a margin as you can see below, to correct the indent seen in the HTML5 version, doesn't affect Flash version. In SL2 itself I made the variable box have no internal margin (0px). Hope it helps someone, have not yet tested on other machines.
it seems we have this issue now as well. We use our own branded font and I assumed it was embedded. Having a workaround is nice, but since the discussion is 4 years old, I can't imagine that this is not solved in the application. Can you clarify this?
We use the variables to put in closed captions. These are displayed on screen as text.
Currently I am facing the same "issue". If it is not possible to easily embed the font within the module, can I then change the fall back font? In our case the fall back font is Times New Roman and I would like to change it to Arial which is closer to the font we use in our eLearning modules. I am not sure if it can be changed within Storyline. I haven't found anything. Maybe it is a computer setting?
Not that I'm aware of unless someone in the community has a suggestion.
Default system fonts will be substituted for variable text. Default system fonts may be different for each computer, tablet, or smartphone where your content is viewed.
Experiencing the same problem. Fonts applied to variable references in my published Articulate Storyline 2 output aren't the fonts I expected. I read that fonts can't be embedded in published output for variable text. And as a result, default system fonts will be substituted for variable text. Is there already a work around this?
You may find that fonts applied to variable references in your published Articulate Storyline 2 output aren't the fonts you expected.
Fonts can't be embedded in published output for variable text. As a result, default system fonts will be substituted for variable text. Default system fonts may be different for each computer, tablet, or smartphone where your content is viewed.
Hi Leslie, any plans for the upcoming release of Storyline 3 to include fixing the "default system fonts substituting for variable text" issue? I know that would be a very popular fix!
The font issue can be fixed fairly easily in the HTML5 output, since the variable text fields are real html, not rendered on a canvas like normal text in SL
Just embed the font as for any webpage (generate from fontsquirrel for example) and add the following code to the player.css
44 Replies
I found a workaround for this. You can embed your font via CSS after you publish.
Hi Naito
Sounds like a clever workaround.
As this is an old thread about a problem that has affected many, many, many... people, would you please provide more information about where manual tweaks need to be made, and what the tweaks look like?
Thanks on behalf of a grateful community!
PeteB
Hi, Naito -- If you would like to share your file so Pete and others can take a look, I just wanted to mention that you are able to do so by using the "ADD ATTACHMENT" button in the bottom left of the reply box. You will then be able to browse for your .story file and upload from there! :)
Hiya Naito, do you mind sharing what you did?
Thanks
Michael
Hiya, just to share on this. In order to see my font for variables, in this case Dax-regular, I changed the player.css, lines 12, 13, 15 to commented out so they don't inherit font-weight, font-style, font-family. I don't know if all 3 were really necessary I could have probably done the same with just font-family, but it 'appears' to work for me. I also changed line starting 476, added a margin as you can see below, to correct the indent seen in the HTML5 version, doesn't affect Flash version. In SL2 itself I made the variable box have no internal margin (0px). Hope it helps someone, have not yet tested on other machines.
.item.vartext
{
overflow-wrap: break-word;
margin-left: -10px;
}
Thanks for popping in to share your findings and solution with the community here Michael.
Hey Michael
if this works for our clients I'm going to owe you a very big drink!!...Thanks for sharing and off to test - have a great weekend.
it seems we have this issue now as well. We use our own branded font and I assumed it was embedded. Having a workaround is nice, but since the discussion is 4 years old, I can't imagine that this is not solved in the application. Can you clarify this?
We use the variables to put in closed captions. These are displayed on screen as text.
Reference fonts are not embedded.
Hello everyone,
Currently I am facing the same "issue". If it is not possible to easily embed the font within the module, can I then change the fall back font? In our case the fall back font is Times New Roman and I would like to change it to Arial which is closer to the font we use in our eLearning modules. I am not sure if it can be changed within Storyline. I haven't found anything. Maybe it is a computer setting?
Thanks for your help.
Best
Dominik
HI Dominik!
Not that I'm aware of unless someone in the community has a suggestion.
Default system fonts will be substituted for variable text. Default system fonts may be different for each computer, tablet, or smartphone where your content is viewed.
Hi Leslie,
Thank you for your answer. I am sure we will find a solution.
Hi there,
Experiencing the same problem. Fonts applied to variable references in my published Articulate Storyline 2 output aren't the fonts I expected. I read that fonts can't be embedded in published output for variable text. And as a result, default system fonts will be substituted for variable text. Is there already a work around this?
Hi Ruben!
There is not an update at this time.
You may find that fonts applied to variable references in your published Articulate Storyline 2 output aren't the fonts you expected.
Fonts can't be embedded in published output for variable text. As a result, default system fonts will be substituted for variable text. Default system fonts may be different for each computer, tablet, or smartphone where your content is viewed.
Hi Leslie, any plans for the upcoming release of Storyline 3 to include fixing the "default system fonts substituting for variable text" issue? I know that would be a very popular fix!
Hi Jon!
Product roadmaps and releases is not something we disclose prior to, so I do not have any information to share with you regarding this.
The font issue can be fixed fairly easily in the HTML5 output, since the variable text fields are real html, not rendered on a canvas like normal text in SL
Just embed the font as for any webpage (generate from fontsquirrel for example) and add the following code to the player.css
The annoying part is that this of course doesn't work for the Flash output.
Hope that helps a bit at least.
Cheers,
David
Hey thank you,
This works fairly well. At least, I can manage of with basic of changing the font for text variable. :)
Now I just need to figure out on how to add line spacing. :D
Hi Smruti,
I know you were also discussing ideas in this forum discussion so I wanted to link to the ideas recently shared there as well.
This discussion is closed. You can start a new discussion or contact Articulate Support.