I have a course with large chunks of texts that need to be justified, and one-letter words cannot be at the end of the line. In HTML I did this using non-breaking spaces after them, I wish to do the same in Storyline, but inserting a nbsp does not work, the word stays at the end of the line. Are the any ways to solve this problem?
It is frustrating that simple requests like this, take so long to implement.
Course Playback Speed Control, Streaming Video, Accessible Quiz Review, Accessible Question Feedback, Video Transcripts, Multiple Audio Tracks for Videos and Multiple Closed Captions (https://articulate.com/support/article/Articulate-360-Feature-Roadmap 21th December 2022) are great, but Articulate would help me much more with:
A nobreak space
Possibility to add images in table cells
Possibility to add hyperlinks in table cells
All the other competitive tools in the market have these options.
I'll upvote also the use of non-breaking spaces in Storyline. This is very useful, especially in french language, where we need non-breaking spaces, for instance before question marks, exclamation points, quotation marks, so as they are kept with the preceding word.
- close caption (audio/video) - slide names in the player menu - Accessible text - Notes - export to xliff
storyline player uses html text for this text types, so it's not a problem for the browser to do this
for the normal display text storyline uses svg text (= single line text without linebreak)
if you publish a course, every paragraph is splitted into single lines and for EYERY char the x, y position is calculated (-> result in html5/data/js/paths.js for the complete course)
the publishing algorithm does not pay attention to non breaking space
@articulate please update your publishing algorithm, you have only change your definition what a word is
now: xxxx xxxx -> 2 words new: xxxx[nbsp]xxxx -> 1 word
additionally only a keyboard shortcut would have to be defined how to enter [nbsp]
if you should revise the text parser, it would be nice if you could integrate the "optional hyphen (­)"
in german there are some very long words, e.g. - Grundstücksverkehrsgenehmigungszuständigkeitsübertragungsverordnung - Rindfleischetikettierungsüberwachungsaufgabenübertragungsgesetz
Thanks for your thoughts on this! Supporting non-breaking spaces have already been reported as a bug in the software. I'm going to add your voice to the report. If there's any news regarding this bug, this conversation will be updated.
32 Replies
Hello Caroline!
Thanks for reaching out. We do not have any updates at this time. We'll be sure to update this thread with any news so you're in the loop!
You can see what we are currently working on in our Feature Roadmap.
Have a nice afternoon!
It is frustrating that simple requests like this, take so long to implement.
Course Playback Speed Control, Streaming Video, Accessible Quiz Review, Accessible Question Feedback, Video Transcripts, Multiple Audio Tracks for Videos and Multiple Closed Captions (https://articulate.com/support/article/Articulate-360-Feature-Roadmap 21th December 2022) are great, but Articulate would help me much more with:
All the other competitive tools in the market have these options.
I'll upvote also the use of non-breaking spaces in Storyline. This is very useful, especially in french language, where we need non-breaking spaces, for instance before question marks, exclamation points, quotation marks, so as they are kept with the preceding word.
just tested - Non Breaking Space is ok for
- close caption (audio/video)
- slide names in the player menu
- Accessible text
- Notes
- export to xliff
storyline player uses html text for this text types, so it's not a problem for the browser to do this
for the normal display text storyline uses svg text (= single line text without linebreak)
if you publish a course, every paragraph is splitted into single lines and for EYERY char the x, y position is calculated (-> result in html5/data/js/paths.js for the complete course)
the publishing algorithm does not pay attention to non breaking space
@articulate
please update your publishing algorithm, you have only change your definition what a word is
now: xxxx xxxx -> 2 words
new: xxxx[nbsp]xxxx -> 1 word
additionally only a keyboard shortcut would have to be defined how to enter [nbsp]
this should not be a major effort
@articulate
if you should revise the text parser, it would be nice if you could integrate the "optional hyphen (­)"
in german there are some very long words, e.g.
- Grundstücksverkehrsgenehmigungszuständigkeitsübertragungsverordnung
- Rindfleischetikettierungsüberwachungsaufgabenübertragungsgesetz
Hi Jurgen,
Thanks for your thoughts on this! Supporting non-breaking spaces have already been reported as a bug in the software. I'm going to add your voice to the report. If there's any news regarding this bug, this conversation will be updated.
First raised almost 11 years ago. Could this be a record for Articulate?! 😂