I just recently updated to Update 6. Something appears to have broken.
Previously, I could embed a variable in a text box, assign a different color to the variable, and it would display the variable value in the assigned color.
Now the variable font color remains white.
Any suggestions on how to fix this would be appreciated. The attached story file should demonstrate the issue.
Thanks for sharing the file here. I took a look and saw the behavior on your slide, but could not tell where the variable was being adjusted - I added a new slide with a text entry variable on the slide, and the colors for that appear as normal.
I'd like to confirm that you're working on project files as described here:
Work on your local drive (your C: drive).Working on a network drive or a USB drive can cause erratic behavior, includingfile corruption, loss of audio, and other unexpected behavior.
You should also make sure the directory pathto your project files and your published output is less than 260 characters(for example C:\Articulate).
Avoid using special characters, accents orsymbols in your file names.
Sorry for the delay - and I appreciate the additional images here. I tested this again using Update 6 and Update 5, and based on your additional examples I was now able to replicate the behavior using Update 6. I've shared this with our QA team for additional review, but I do not have a time frame to offer in regards to a fix, so in the meantime I'd suggest to continue using update 5.
Once I have additional information to share I'll post it here.
We always recommend the latest update due to bug fixes, etc. If you feel as if you need a previous version, we would ask that you reach out to support to help determine the best resolution for you. Thanks!
In Storyline 2 there seems to be formatting issues when a font is set in a variable. It looks like the issue only appears in languages such as Japanese, Chinese (Simplified and Traditional). Please see attached Storyline file & publish for reference.
(The text on top is shows how the correct font "MS PGothic" should look.)
Any insight on how to fix this would be greatly appreciated.
That font looks a little pixelated even before showing the variable reference and may be displaying oddly based on the % included which previously users had utilized to show the text in a crisper way. Have you tried in a few other fonts? I seem to remember the SimSun font being a good one for Chinese/Japanese characters.
Sorry for any confusion - yes, the % sign is needed to reference the variable, but it does adjust the crispness of the text slightly and is something that other users have implemented (in terms of including a fake variable reference) to ensure there was consistent text across the slide(s) and using the variable in this case you can see the change to the text on the slide stage even prior to publishing.
I was not aware that SimSun was exclusively a Chinese font, based on some previous issues we had with Japanese and Storyline 1 where Windows was defaulting to SimSun, although it displayed fine in the published output.
Looking at your slide again, with that font setting and text in English as a comparison it seems that the variable reference for English text and the same text outside of a variable reference also do no match - so it may be something specific to that font as well. Previously we've recommended Arial MS Unicode as a font option for Japanese or Chinese characters.
Hi, I'm also on SL1 Update 8 and I'm having the same issue - whole text box reverting to black text when a variable is in the sentence (although I'm convinced that I have had different font colours in the same text box as variables before). I am about to submit a support case to go to a lower update version, but is this going to be looked at in a future update? My organisation has no plans to upgrade to SL2 any time soon.
I have used a work around of having the variable in a separate text box, and I have left a gap in the sentence in the first text box and put the variabletext box over the top (as suggested in a different post), but... as the variable text will change length depending on what the user inputs, it's very difficult to judge the gap I need to leave for it. Really could do with being able to just change the font colour of it in the same text box.
Yes, this is still an issue that exists in Storyline 1 Update 8. I don't have any additional information in regards to if it'll be fixed, so we'd suggest continuing to use the workaround in the meantime.
If you'd like to connect with our Support team, please feel free to reach out to them here and I'll also be sure that this thread is included in the report we filed with our team so that if there is any additional information to share we'll be able to post here.
18 Replies
Hi Chris,
Thanks for sharing the file here. I took a look and saw the behavior on your slide, but could not tell where the variable was being adjusted - I added a new slide with a text entry variable on the slide, and the colors for that appear as normal.
I'd like to confirm that you're working on project files as described here:
Hi Ashley,
This is a weird issue. Please see the updated story.
Images showing behavior below...
This is what it looks like when it runs, please note the underlined sections
Thanks,
Chris
Hi Ashley,
I did an uninstall and reinstall of Update 6, and the problem persisted.
So I re-installed Update 5, and the font colors look correct again.
Hi Chris,
Sorry for the delay - and I appreciate the additional images here. I tested this again using Update 6 and Update 5, and based on your additional examples I was now able to replicate the behavior using Update 6. I've shared this with our QA team for additional review, but I do not have a time frame to offer in regards to a fix, so in the meantime I'd suggest to continue using update 5.
Once I have additional information to share I'll post it here.
Hello,
I have got the same problem. Where can I download Update 5?
Thanks, Martin
Hi Martin!
We always recommend the latest update due to bug fixes, etc. If you feel as if you need a previous version, we would ask that you reach out to support to help determine the best resolution for you. Thanks!
Hi there. I was wondering has there been a solution to this? Apart from reverting back.
Hi Diarmaid,
This issue is still with our QA team for review, but we'll be able to update you here if there is any additional information.
Can you tell me whether there is a solution for this?
I'm on update 8 and after hours of trying to figure out why the color wasn't showing, I figured out it was because of the variable in the text.
Hi Marcus,
This issue still is present in Storyline 1 Update 8, although I do see it noted that the behavior does not persist in Storyline 2.
Hi,
In Storyline 2 there seems to be formatting issues when a font is set in a variable. It looks like the issue only appears in languages such as Japanese, Chinese (Simplified and Traditional). Please see attached Storyline file & publish for reference.
(The text on top is shows how the correct font "MS PGothic" should look.)
Any insight on how to fix this would be greatly appreciated.
Thank you,
Jennifer
Hi Jennifer,
That font looks a little pixelated even before showing the variable reference and may be displaying oddly based on the % included which previously users had utilized to show the text in a crisper way. Have you tried in a few other fonts? I seem to remember the SimSun font being a good one for Chinese/Japanese characters.
Hi Ashley,
I'm confused, I thought you had to use the % in order to display the variable.
SimSun is a Chinese font and is equivalent to a serif font and the client wants sans-serif. MS PGothic is the sans-serif font for Japanese.
Hi Jennifer,
Sorry for any confusion - yes, the % sign is needed to reference the variable, but it does adjust the crispness of the text slightly and is something that other users have implemented (in terms of including a fake variable reference) to ensure there was consistent text across the slide(s) and using the variable in this case you can see the change to the text on the slide stage even prior to publishing.
I was not aware that SimSun was exclusively a Chinese font, based on some previous issues we had with Japanese and Storyline 1 where Windows was defaulting to SimSun, although it displayed fine in the published output.
Looking at your slide again, with that font setting and text in English as a comparison it seems that the variable reference for English text and the same text outside of a variable reference also do no match - so it may be something specific to that font as well. Previously we've recommended Arial MS Unicode as a font option for Japanese or Chinese characters.
Hi, I'm also on SL1 Update 8 and I'm having the same issue - whole text box reverting to black text when a variable is in the sentence (although I'm convinced that I have had different font colours in the same text box as variables before). I am about to submit a support case to go to a lower update version, but is this going to be looked at in a future update? My organisation has no plans to upgrade to SL2 any time soon.
I have used a work around of having the variable in a separate text box, and I have left a gap in the sentence in the first text box and put the variabletext box over the top (as suggested in a different post), but... as the variable text will change length depending on what the user inputs, it's very difficult to judge the gap I need to leave for it. Really could do with being able to just change the font colour of it in the same text box.
Thanks
Hi Laura,
Yes, this is still an issue that exists in Storyline 1 Update 8. I don't have any additional information in regards to if it'll be fixed, so we'd suggest continuing to use the workaround in the meantime.
If you'd like to connect with our Support team, please feel free to reach out to them here and I'll also be sure that this thread is included in the report we filed with our team so that if there is any additional information to share we'll be able to post here.
Hi,
I have put in a support case (Case #00606112). I really hope this does get an update soon.
Thanks for your help
Thanks Laura - and I'll keep an eye on your case too.
This discussion is closed. You can start a new discussion or contact Articulate Support.