Crispness of edges of fonts in Storyline?
Nov 22, 2012
By
Eric Stephan
I am wondering if the modules that we are making with Storyline are having the fonts have edges that appear just a bit fuzzier than is normal.
Can you tell me -- if you look at the title slide of this module -- look at the black words
Evaluation for Education Programs
and also
Module 2
Module is at: http://tinyurl.com/cvrep2e
Do the font edges seem fuzzy to you? And if so, is that pretty much normal for Articulate, or can it be improved?
BTW, the chosen font is the default one called "Articulate."
Any thoughts or suggestions on that? THANKS! --eric
137 Replies
Ooooo, the variable thing really works. Sadly, I have a lot of text boxes that are on top of background artwork or on transparent boxes. But at least this is a work around for certain circumstances.
Thanks, Dan. I should have taken the time to read the previous posts properly. When I saw all of that code, I assumed there was some digging around we had to do.
I suppose the best thing to do is to called your variable something like 1 so that you only have to leave room for %1%.
I'll echo Rob's sentiments and urge Articulate to get a proper fix for this as soon as ...
I'm already starting to find a couple of issues with the "insert variable" workaround, sadly. It seems to work best when you have a single paragraph text box and plain text.
When I tried it out in text boxes that had a few paragraphs, different colours, bullets etc., I was seeing a variety of different issues such as the colours of bullets changing, erratic vertical alignment, and the size of text reducing.
You are right James. I reuploaded the font-test and added bullet points and some text-animaton.
The flash-output is quite good. The HTML5 doesn't convince me.
There is, among other, a bug concerning the font-size:
"<font face="Arial" color="#000000" style="font-size:15,52px">"
I tried to change the value with Firebug. Deleting ",52" solves the problem. Of course that's not really a solution.
That does help the quality of the text, except when I tried it the player buttons were reduced in size. Can they be returned to "normal" size?
Is there any update on a fix for this issue? I have just submitted a course for a client review, which they sent out to a focus and the fuzziness of text rendering was commented on by just about everyone.
It's a bit deflating, to say the least.
Really sorry to hear about the frustration, James. This issue is still under active investigation, and I'll continue to monitor it and report any updates.
I'm afraid we use our own bespoke navigations buttons so I'm not sure if the built in player buttons can be resized.
Having tried a few different things which all had draw backs, we've settled on choosing fonts that look the sharpest with the limitations. Google Open Sans font isn't too bad:
http://www.google.com/fonts/specimen/Open+Sans
Richard
www.unicorntraining.com
Thanks Peter. Fingers crossed!
Eric - I am unable to look at your web page, but I don't think that is the issue.
I did a test using the same fonts on both Storyline and Studio, and they look a lot clearer on Studio.
Hail Heros!!
This is my first post as I learnt a lot about the Storyline from this forum and it is of great help simply because of you all. Much appreciated.
Now my question to the dev team, is this bug fixed yet? Our client is not happy with the font rendering/sharpness.
I really hope to see a fix rather than a workaround.
Thanks in advance.
Hi Phil and welcome to E-Learning Heroes! Glad to hear that forums have been some assistance to you
This issue is actually still open and in the hands of our QA Team. I have no update to provide at this time, but I am going to make a note that another user is inquiring.
Thanks Leslie! by any chance if you can provide me an ETA, would be much appreciated.
Hi Phil! Unfortunately, I cannot offer any type of timeline.
This is a big issue with the HTML5 output and we would also appreciate it if escalated and resolved as soon as possible - very disappointing creating projects for clients to view and the first thing they see is fuzzy text
Its kind of frustrating that this issue has existed since the initial release (I believe over a year ago now) and its still not resolved.
If you would like to submit a case to support to verify that this is your issue, please do so. I have updated the QA Team and referred them to this thread in the meantime.
Yes I have just submitted a case but I have to agree with Rob, it's been practically a year now :(
Thanks Paul! I see where you submitted your case (00364890) and you should be hearing from someone soon.
Yes I agree with Rob too, been waiting for this for ages now, really frustrating issue.
Wev'e actually recently ended up going Captivate 7 as a direct result of this issue due to it having crisp text on render. Too many clients were complaining about the fuzzy text on projects we had done in Storyline.
Really hope this gets sorted as i actually prefer authoring in Storyline.
Hi guys.
This is an issue we are certainly aware of and we are looking to see what we can do to improve text crispness. We will keep you posted if there are any updates regarding this.
Hi guys,
I have just downloaded latest update 4: 1311.1422
I am just wondering if this issue is fixed or still unresolved. This issue is keeping me away from using Storyline as my client didn't like the text. very frustrating..
Good Morning, Phil.
There have been no changes to Storyline's text output in Update 4.
Having said that, the more examples of the problem we can share with the Articulate Quality Assurance Team, the more likely we are to be able to identify a path forward. Could you please share a copy of your .story project file with us, or perhaps a screenshot or two that clearly illustrates your client's complaint? Thanks!
Hi Justin,
here is a screenshot. it can be easily reproduced as publishing any text will result in this..
you will observe that the editor is showing the text, crispy and clear where as published text is a bit hazy.
Thanks for clarifying your client's complaint, Phil.
I will certainly pass this information on to QA. Thanks again!
This discussion is closed. You can start a new discussion or contact Articulate Support.