Kym, are you using the default Articulate font or a custom font?
I'm not a font guru, but fonts like the Articulate font are either .otf (OpenType) or .ttf (TrueType) that render well. Some custom fonts not of these standards won't behave quite the way one would expect.
I agree with everyone that this is a pretty sad issue. I've developed SCORM based wrappers for Flash and HTML before and I can tell you that the issue is how Storyline re-renders the text box as it was placed on the screen. Any Flash developers out there you can try this out yourself. If you take a text box in Flash and put the X and Y coordinate on a fraction of a whole number, you will get exactly what you see in Storyline; fuzzy text.
Storyline doesn't allow users to use fractions of whole numbers in position placement but I can almost guarantee when it gets published or rendered, it moves a micron or so--resulting in the fuzzy wuzzies. I have had the most luck in Storyline using Arial 12pt and adjusting placement on a slide to find the crispest setting THEN build my master slide around those settings or I honestly revert to Articulate Presenter 2013. At least there, you are in PowerPoint and have the ability to adjust to fractions to compensate for the packaging that happens on publish. You can actually see the difference in font clarity to the same deck published through Storyline.
Font rendering and crispness, as you can see, has been a popular topic and one that we have shared with our product development team in addition to the users here who have submitted feature requests.
Are you using Storyline 1 or Storyline 2? I know Storyline 2 which was released in September handles fonts and crispness, editing, etc. better and may help provide you better results.
VETTER SOLUTIONS
4063 E. Burnside Street
Portland, OR 97214
Phone: 503-449-8173
Fax: 503-233-1652
Email: Dan@VetterSolutions.com
This e-mail is intended for the designated recipient(s) only, and may be confidential, non-public, and proprietary. Unauthorized reading, distribution, copying or other use of this communication is prohibited and may be unlawful. Receipt by anyone other than the intended recipient(s) should not be deemed a waiver of any privilege or protection. If you are not the intended recipient or if you believe that you have received this e-mail in error, please notify the sender immediately and delete all copies from your computer system without reading, saving, or using it in any manner.
Do you mean Studio 13? You posted in the Storyline forums, hence my reply. I haven't seen a lot of issues with fonts in Studio 13, although you may want to look through the forums to see if there is something that matches your scenario and reach out for help there. Also, you're welcome to share your project files (I'd suggest to start a new thread in the Studio forums) or connect directly with our support team.
Not really a fix, more of a semi-promising (and tedious) hack:
In the case of State 4, which has crisp text (see my original comment) ... I simply copied that text and pasted it in States 2 and 3 ... And lo and behold, States 2 & 3 are no longer blurry.
This begs the questions:
What was special about State 4 text that made it crisp to begin with?
What's being copied to the clipboard that makes States 2 & 3 crisp?
Thanks for sharing that here and I've included that information in the report filed with our Quality Assurance team so that they can continue to investigate.
could you please share any update for this issue? The last one is almost 6 months ago. This is a very long timeframe for a problem with the advertised HTML5 Support.
I do not have an update to share at this time as this issue is still in the hands of our QA Team. This thread is attached to the issue so that we can update when applicable.
Hi Suraj! This is still in the hands of our QA Team. I took a peek, but I've not seen where any users have shared a particular workaround. Hopefully someone in the community will be able to pop in and share.
Did you see Ryan's suggestion here? That's the only one I've seen mentioned.
137 Replies
Is there a way to edit the hover state when using a hyperlink? I can change the text colour and weight but not the background colour when hovering.
Has there been any advances in this area? Fonts are still rendering quite badly in the published version.
Kym, are you using the default Articulate font or a custom font?
I'm not a font guru, but fonts like the Articulate font are either .otf (OpenType) or .ttf (TrueType) that render well. Some custom fonts not of these standards won't behave quite the way one would expect.
hi Kevin, i am using Arial for my project, and the publish font still looks blurry. Still readable but noticeable difference.
I agree with everyone that this is a pretty sad issue. I've developed SCORM based wrappers for Flash and HTML before and I can tell you that the issue is how Storyline re-renders the text box as it was placed on the screen. Any Flash developers out there you can try this out yourself. If you take a text box in Flash and put the X and Y coordinate on a fraction of a whole number, you will get exactly what you see in Storyline; fuzzy text.
Storyline doesn't allow users to use fractions of whole numbers in position placement but I can almost guarantee when it gets published or rendered, it moves a micron or so--resulting in the fuzzy wuzzies. I have had the most luck in Storyline using Arial 12pt and adjusting placement on a slide to find the crispest setting THEN build my master slide around those settings or I honestly revert to Articulate Presenter 2013. At least there, you are in PowerPoint and have the ability to adjust to fractions to compensate for the packaging that happens on publish. You can actually see the difference in font clarity to the same deck published through Storyline.
$0.02
Hi Arthur, and welcome to the Heroes community.
Font rendering and crispness, as you can see, has been a popular topic and one that we have shared with our product development team in addition to the users here who have submitted feature requests.
If you'd like to stay up to date on future releases, versions, and updates I'd suggest to follow along with the Word of Mouth blog, our Facebook and Twitter pages.
Sorry to hear there is nothing on this...I too have been questioning the 'crispness' of the fonts I'm seeing in my finished courses.
Hi Dan,
Are you using Storyline 1 or Storyline 2? I know Storyline 2 which was released in September handles fonts and crispness, editing, etc. better and may help provide you better results.
Actually, my issue is with Articulate 2013
Dan Vetter, CPLP, President
VETTER SOLUTIONS
4063 E. Burnside Street
Portland, OR 97214
Phone: 503-449-8173
Fax: 503-233-1652
Email: Dan@VetterSolutions.com
This e-mail is intended for the designated recipient(s) only, and may be confidential, non-public, and proprietary. Unauthorized reading, distribution, copying or other use of this communication is prohibited and may be unlawful. Receipt by anyone other than the intended recipient(s) should not be deemed a waiver of any privilege or protection. If you are not the intended recipient or if you believe that you have received this e-mail in error, please notify the sender immediately and delete all copies from your computer system without reading, saving, or using it in any manner.
Hi Dan,
Do you mean Studio 13? You posted in the Storyline forums, hence my reply. I haven't seen a lot of issues with fonts in Studio 13, although you may want to look through the forums to see if there is something that matches your scenario and reach out for help there. Also, you're welcome to share your project files (I'd suggest to start a new thread in the Studio forums) or connect directly with our support team.
Fuzziness issue still present in HTML5.
It's a very odd & inconsistent bug. Wish Articulate can share why this is happening; and appropriate steps.
In my case, State 1: beautiful text... State 2: blurry text ... State 3: blurry text... State 4: beautiful text.
It is what it is?
Hi Ryan! Do you have a .story file that we could take a look at?
This isn't an isolated/exceptional case. Leslie, can you share what the support team is looking for?
Not really a fix, more of a semi-promising (and tedious) hack:
In the case of State 4, which has crisp text (see my original comment) ... I simply copied that text and pasted it in States 2 and 3 ... And lo and behold, States 2 & 3 are no longer blurry.
This begs the questions:
What was special about State 4 text that made it crisp to begin with?
What's being copied to the clipboard that makes States 2 & 3 crisp?
Find the pattern. Find the fix?
Anywho. Back to creating elearning greatness :P
Hi Ryan! Files to replicate the behavior is typically what we look for in any situation.
I'm glad that you were able to get to a workable solution.
Shape Effect > Shadow
Seems to be the culprit.
Paragraph/Sentence length also a factor, but I believe that weirdness stems from Shape Effect > Shadow.
I'm sure if the support team plays around with drop shadows, they'll be able to create blurry text in HTML5.
/Back to work.
It's a combination of character length and Shape Effect > Shadow. Will cause blurry text in HTML5.
Hi Ryan,
Thanks for sharing that here and I've included that information in the report filed with our Quality Assurance team so that they can continue to investigate.
Hello Ashley,
could you please share any update for this issue? The last one is almost 6 months ago. This is a very long timeframe for a problem with the advertised HTML5 Support.
Thank you!
Hi Evelyn!
I do not have an update to share at this time as this issue is still in the hands of our QA Team. This thread is attached to the issue so that we can update when applicable.
:/ OK, thank you Leslie for the information
Hi,
I am a story line 2 (update 7) user and i am facing the same issue of text looking a bit blurry.
i checked this whole thread, which looks like was raised 3 years back and still no resolution!
has any one found any work around for the same, till Articulate fixes this bug?
Hi Suraj! This is still in the hands of our QA Team. I took a peek, but I've not seen where any users have shared a particular workaround. Hopefully someone in the community will be able to pop in and share.
Well i did see his suggestion, but i am not using shadows for my text still it renders blurry in html5 output.
It was worth a shot Suraj :) Darn!
This discussion is closed. You can start a new discussion or contact Articulate Support.