Apache OpenOffice (AOO) Bugzilla – Issue 9727
Stretchy unbreakable space
Last modified: 2013-08-07 14:41:36 UTC
A fixed width unbreakable space is available and can be inserted with ctrl+space. I would like added a stretchy unbreakable space. (In troff this is done with: \~ ) No, that wasn't a crooked smily. In a justified row of text where just one word is separated by an unbreakable space the non-stretchy unbreakable space offered causes uneven spacing of the words. I want the word spacing to be as for the normal spaces. I use this sometimes when words form a single token but do not need the close couple that the unbreakable space gives. Also when I want to force a word to the next row to fill a poorly justified row of text, I would put a stretchy unbreakable space where the line is broken forcing a word to fill the space on the row below. Suggest this is inserted with ctrl+shift+space.
HI->FL: A case for the user experience.
Today I am not sure if it makes sense not to expand such a protected space at all, because it is protected from being wrapped in between, not more. I will investigate.
What do you think about my previous comment? Please fix this one, if you can agree . Thank you!
Frank, I'm not sure I understood your comments. I'm also unsure who "you" is. Please will you clarify. Is my initial request understood? James Lee.
FME->FL: Two points to consider: 1. We would change the layout of existing documents 2. MS Word does not expand these nonbreakable spaces in justified alignment either. Back to you.
> 1. We would change the layout of existing documents NO! I didn't say make the existing unbreakable space stretchy. I said create a new entity which is a stretchy unbreakable space. (Just as troff has both, oh, and troff has several partial width spaces too.) This is very different because of course changing the existing unbreakable space would upset existing documents and shouldn't be done. > 2. MS Word does not expand these nonbreakable spaces So that makes it right? ;-)
FL: Key argument against changing current behavior is not to change existing docs and of course import of Word documents. Not changing the current behavior means to add a new feature and for that it is too late -> retargeted to feature for OOo 2.0
This and issue 3243 would be a major improvement from typographical point of view.
Double: 20879 *** This issue has been marked as a duplicate of 20879 ***
.