Forum Discussion

StefanMachura1's avatar
StefanMachura1
Community Member
13 years ago

Non-breaking spaces in text.

Hi,

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?

38 Replies

  • ChrisDorna's avatar
    ChrisDorna
    Community Member

    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.

    It's the little things that matter
    Low hanging fruit
  • 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?! 😂 

  • Well, yeah, I somehow love those long waits for simple things, but isn't this few years a plenty time to introduce something that exists with computers since the beginning? 

  • ChonnikanP's avatar
    ChonnikanP
    Community Member

    Having the latest version installed, and there's still no workaround on non-breaking spaces. So far, inserting non-breaking spaces using Alt+0160 still does not work (or could work for some users, but cannot be considered a proper solution).

    I would love to know if there are any alternative solutions or updates planned to address this issue.

    • BrettRockwood's avatar
      BrettRockwood
      Community Member

      I hope this isn’t Lucy pulling the football away as Charlie Brown tries to kick it. 🙂 I’ve been waiting 13 years and am afraid to check for fear of being disappointed.

    • StevenBenassi's avatar
      StevenBenassi
      Staff

      Hi BeverleyCuria​!

      Happy to help!

      Articulate Studio 360 has reached its end of support. While the individual applications within Studio 360 are still functional, they are no longer receiving updates. 

      The users in this discussion are affected by a known Storyline bug we're tracking. This bug prevents non-breaking spaces from functioning, within Storyline 360. If you're also experiencing this issue in Storyline, you may find the following workarounds helpful:

      • Have the text set up in a separate program, like Microsoft Word. Take a screenshot and insert that into Storyline as a graphic.
      • Create your text in HTML pages, and insert it into Storyline, as a local Web Object.
      • Type SHIFT+ENTER where you want the line to break. That will insert a soft return (i.e. start a new line without starting a new paragraph).

       

      Please let me know if you have anymore questions!