Non-breaking spaces in Rise?

Hi, 

Is there any news about this Non-breaking spaces correction in Rise? 

Thank you 

I am attempting all the workarounds suggested but this is making the use of Rise 360 inefficient because of the additional time needed for our translated courses. We need to translate every course into French and non-breaks are essential to translation. Making a comment to get alert when this is fixed.

3 years later and still nothing?

Hi, is there any update on this? In Czech language, typography rules don't allow single character 'words' at the end of the line. In HTML "&nbsp" entity inserted after the 'word' solves it. If we could get this at least in form of a button on the text edit context menu that would inject it as a hidden character, it would be awesome.

Very disappointed with Rise 360 developer.

Adding my vote for this as well. Our use case (in addition to French language punctuation) is for measurements. Things like 50 m or 31 cm should not break across lines. It would be nice to be able to add the NBS as we do in Word. Thanks!

Hello! This is a feature that would be helpful for me too! We work a lot in French as well.

Following this thread for updates!

Thank you.

I found another workaround (based on Arith's suggestions). This works for me in Chrome:

1. Right-click the paragraph where you want a no-breaking space. 
2. Click Inspect to bring up the inspector in your browser. 
3. Right-click the <p> tag that contains your text, then click Edit as HTML. 
4. Replace the existing space with the HTML character code for no-breaking space, that is: &nbsp; 

This seems to work reliably and the no-breaking space is still there after I reload the page. 

I also noticed that if you add more than one space in your text, Rise replaced all but one of those spaces with no-breaking space. So even if HTML has built-in protection against double spaces, Articulate has worked hard to allow you to make those typos. 😁

Thanks for the workaround! It'll be interesting to see what happens to those spaces when we send the course for translation. But I figure I'll cross that bridge when I get there. 😁

Really hope the bug is resolved soon
! 

Thanks for the workarounds, need this function too!