Apache OpenOffice (AOO) Bugzilla – Issue 84376
No Line break possible between a word and dots having non-breaking space in between
Last modified: 2013-08-07 14:44:35 UTC
(NOTE: this is against the released 2.3.1; the Issue Tracker scroll list is out of date.) Prior to 2.3.1, line breaks would occur both before and after an ellipsis; that is, the ellipsis was treated like a word. In 2.3.1, a line break will no longer occur before an ellipsis, only after one. Unless this behavior is intended, I suggest the keyword, "regression". This behavior may be a side effect of the solution for Issue 81448. Small doc attached, with ellipsis, for playing with. /tj
Created attachment 50189 [details] Ellipsis to play with
MRU->KHONG: see attached document. when addign some characters to the first line you will notice that there is no break possible btween "But" and the three dots (which are connected with non-breaking spaces). This worked fine last in OO 2.2.
This is intented behavior, the ellipsis is considered as punctuation, and should not appear in the beginning of a line. I checked MS office 2003, it has same behavior.
Thanks for trying, and having tried, to do the right thing. The problem is that a construction like, "I thought . . . somehow" can't be broken for thirteen characters, which can leave a very ragged right margin. AFAIK, the four-dot ellipsis is always terminal punctuation for a paragraph, so the ragged margin on the next-to-last line isn't really a problem; however, the three-dot ellipsis can occur right in the middle of the word flow. I suggest that finer discrimination among punctuation is required. For instance, opening quotes (double and single), apostrophes, and the Spanish inverted question-mark are all punctuation that regularly appear at the start of a line. (BTW, em-dash is eligible for line-break-before, and hence can appear at the start of a line, in 2.3.1 and previous versions; I use enough of those to know. I haven't checked out the en-dash, with or without spaces around it.) The deciding factor seems to be the presence of a space before the punctuation; typically, from the end of the previous sentence or paragraph. Punctuation so delimited may start a line, and the ellipsis qualifies under this rule. W/r/t MS Word's behavior, we don't want to create conversion problems, but we won't be able to please everyone, no matter what we do. For those who crave Ms-like formatting behavior for an ellipsis, it is almost trivial to prevent a line-break, by replacing the leading, ordinary space with a non-breaking space. This will survive back-and-forth conversions, too. For the rest of us, the problem is much harder. Forcing an optional line-break would require something like a "soft space" of zero width, analogous to a "soft hyphen". (If we have such a thing, it isn't on the Insert > Formatting Mark menu; if we don't, do we really need one?) It seems a little silly, to use it with a perfectly good, ordinary, breaking space right there, but . . . . /tj
Note: As a workaround, there is an option to force line break :-) In Thai language, there is no such thing as spaces, therefore formatting text depends on a bigger set of "special marks": - Tools-Options-Language settings-Languages - check "CTL support" - OK -> Then you have "Insert-Formatting mark-no-width-optional break"
Will not fix in 2.4. Need better solution.
Reset assignee on issues not touched by assignee in more than 1000 days.