Problem with Formatting Text Variable
I'm trying to use a text variable in the middle of a sentence but any formatting that I set for the text box does not hold. It reverts to a basic text format (looks like Articulate or Articulate Narrow) even though the text box properties indicate the text font should be Tahoma (or other type of font I select.)
Has anyone had this problem? I would love to use the text variable in this course but if it's a bug then I can hold off.
I've attached the .story file which shows the issue on the last layer of the 2nd slide. You have to preview the file in order to see the problem - it looks correct when viewing it in Storyline.
Thank you!
Regards,
Stephanie Case
43 Replies
Hi Christoffer,
This issue still exists in terms of how the text entry and the text references are not able to embed the fonts but will be based on the fonts installed on the users system. This is something that our team has shared is by design based on how we're unable to embed the fonts since the user will need to enter text into them.
You're welcome to follow the steps of other users in this forum discussion, and share your thoughts on this as well in the form of a feature request here as those go directly to our product development team.
I am having the same problem like you all.
Is there any notice of the Articulate STAFF? Guys?????????
Hi Marilu,
Can you share a bit more about the problem you're running into? The issue with text entry and variable reference fonts still exists as those fonts aren't embedded into the output and are based on a users system since they need to input the text. That is not something that has changed yet in Storyline 2 or our newest release of Articulate 360 based still on the individual users system to enter the text. Let us know if you're running into something different and we're happy to take a look at it.
Hello friends!!!
I had a text entry that the user needs to fill up.
But when at the last page I put the resume of the answers of the users, the
entry appear with a font I didn´t use and in a very little size.
I am using %nameofentry% like the tutorials said, but still having the
problem....
Hi Marilu,
Thanks for sharing some more detail with us here! Are you seeing this when you test in the preview of your course or when users actually take a look at the published output? We're not able to update the variable reference (the area where we're showing what a user typed in) dynamically so if they type more than you left space for the text will shrink automatically to ensure we're displaying all the text there. If you used a custom font when creating the course and it's not a standard/system font for that user - we're going to default to a system font and so again things may look different. Since we're relying on the users system and settings, we've got to use their fonts for those things as well because we can't embed them.
Hope that helps clarify and if you're still needing help just let us know!
This has now become an issue for me using Articulate 360 and adding a text variable to draw in users name throughout the module. It really needs to be looked at and fixed. I use a sans font and it looks like it is reverting to Times New Roman for those text entries with the text variable.
Hi there Juliet, sorry you're running into this. Can you tell me what font you're using? I created a quick sample using Calibri here for you to test. I'd like to test your font, as well.
Also, are you on the latest update of Storyline 360? We just released an update on April 18th that fixed some font issues, so you'll want to install that update if you haven't already.
Hi Alyssa, thanks for your reply. I am using Open Sans which works for users even when they don't have the font installed on their comp, except where I am pulling in the text variable. I have just seen the update this morning so have installed it and will test output of my module to see if it fixes the text variable font issue. Thanks for your support.
The update didn't make a difference to this text variable format issue.
Thanks for the update, Juliet. I've opened a case for you (01062837) so we can get to the bottom of this. Be on the lookout for an email from my team shortly!
Thanks kindly Alyssa; your support is much appreciated.
Happy to help, Juliet. I see you're working with Renato in your case--I'll follow along there!
Thanks Alyssa, funny thing is I tested my published output this morning on someone else's comp (who does not have open sans type downloaded on their comp) and it worked perfectly as it should so at least I know it is working as expected for some.
That's good to hear, Juliet. We can take a closer look at why this is happening on your computer, if you'd like. Shoot us the details of your set up and a sample file by clicking here, and we'll be in touch shortly.
Was there ever a solution for this? I'm still having this issue 4 years later.
Hi, Sharon. I'm happy to step in!
First, I'm having trouble recreating any formatting issues in Storyline 360 Update 48. The text variable takes on the font that's applied to the textbox. Here's a short video demo.
If I take it out of my big project, I can't duplicate it either. It seems the bigger my project gets, the more things get wacky. Maybe there's a memory leak that most people don't experience because they have smaller project? I'll keep trying to isolate it.
Thanks,
Sharon
Hello Sharon!
I see that you've reached out to our Support Engineers and worked with my teammate, Georvy! I see that we've logged this as a software bug. Thank you for your help in troubleshooting this issue. We'll update this discussion when we've shipped the fix for this bug!