Offset Bold Text in Storyline
Feb 05, 2015
Can anyone explain WHY text in Storyline becomes offset (out of alignment) when Bolding? Typically, I will notice the text is out of alignment in development mode but looks okay in Preview mode or once published. However, the project I am currently working on, the offset text is WORSE in Preview mode than in development mode.
Is there anyway to fix this. (See attachement for example.)
Thanks!
Kim
8 Replies
Hi Kim
it appears to be a bug particularly if using custom font which I am...client very unhappy we have had to rework screens so that bold and regular font are never on the same line.
As far as I know it's with the QA team but there is no resolution yet...I feel your pain!
Thanks for the reply!
The font I'm using on this particular project is Century Gothic and this is the one that is offset in Preview but appears to be pretty closet to alignment in Development. However, I typically use Arial font (which I don't consider a custom font) and usually the Arial will show offset in Development but NOT in Prevew/Production - totally the opposite as this project.
In any case, I find this VERY frustrating. We used to use Articulate Engage and it did the SAME thing with the fonts offset when bolded. I wish this could be fixed!
Hi Kimberly!
Wendy is correct, this is something that our QA Team is working on. I will add this thread for their reference as well and update when applicable.
Any update on this issue Leslie?
Hi John! I do not have an update to provide on this issue at this time, but as I mentioned before this thread will be updated when applicable.
OK...thanks Leslie...do you have a list of 'safe' fonts to use? I guess Articulate is one but Calibri also seems to be fine.
I do not John since this is still being investigated. No official documentation has been created as of this time.
Hi All!
Articulate Storyline 2 Update 5 is now available for download. It includes WCAG 2.0 support, several new accessibility features, better HTML5 performance, and bug fixes. Click here for details:
This discussion is closed. You can start a new discussion or contact Articulate Support.