To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84376
------- Additional comments from [EMAIL PROTECTED] Wed Dec 12 10:45:46 +0000 2007 ------- 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 --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
