Issue 19716 - wrong Line break at special characters
Summary: wrong Line break at special characters
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 1.1 RC4
Hardware: PC All
: P4 Trivial (vote)
Target Milestone: ---
Assignee: stefan.baltzer
QA Contact: issues@sw
Keywords: oooqa
: 22118 24383 25202 26520 29319 35621 (view as issue list)
Depends on:
Reported: 2003-09-17 17:59 UTC by tnd
Modified: 2013-08-07 14:41 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Should not be a line break in "102(e)" (10.03 KB, application/vnd.sun.xml.writer)
2004-10-12 22:59 UTC, edsuom
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description tnd 2003-09-17 17:59:25 UTC
This is an incompatibility between Writer in OOo 1.0.x
and 1.1.x

1. Open new text document (i. e. start OOo Writer)

2. Enter one character often enough to fill more than
   one line of text, e. g. "a" a hundred times.

3. Enter any brace character somewhere
   in the middle of it on the _first_ line of text.

This should look like this: "... aaaaaaa]aaaaaaa ..."
but it doesn't. Instead, there will be a line break
before or after the brace character: "... aaaaaaa]
aaaaaaa ..."

This behaviour can be considered a major bug since
there are many fonts with ligatures like "ffl" in
place of special characters like "]": and
many other sources

Idea for bugfix: Writer should only insert line
breaks at whitespace characters --- as it did in
all 1.0.x versions.
Comment 1 utomo99 2003-09-18 04:58:13 UTC
I can Reproduce the problem on 
OpenOffice 1.1 RC4(default Install, US), Win XP Pro Sp1. 
(And MS Office XP Sp2). 
It is real problem

By inserting [ or ] or ( or ) it will make next char become in the
next line 
Comment 2 utomo99 2003-09-19 03:35:27 UTC
added oooqa
Comment 3 h.ilter 2003-09-23 09:21:31 UTC
HI->FME: Also reproducible with current version.
Comment 4 frank.meies 2003-09-23 09:33:28 UTC
FME->KHONG: Looks like a breakiterator issue. Did we change the line
break rules for thi case?
Comment 5 karl.hong 2003-09-24 23:21:13 UTC
Yes, we use ICU line breakiterator for OOo 1.1. In OOo 1.0, we use our own 
simple break rule.

Comment 6 stefan.baltzer 2003-10-30 14:10:37 UTC
SBA: I disagree calling a wrong line break in a
hundred-identical-letter-word a "major issue" of a Word Processor. It
is neither a loop or crash => Prio changed to P4.
Even in languages without ligatures, writing something like formulas
or  meaningful strins like "my (uni)verse" and don't expect a break at
the brackets. So the target OOo 1.1.1 is fine because this used to work.
Comment 7 Martin Hollmichel 2003-11-03 14:24:12 UTC
adjusting target milestone to 2.0 since prio 4.
Comment 8 karl.hong 2003-11-12 23:25:24 UTC
*** Issue 22118 has been marked as a duplicate of this issue. ***
Comment 9 karl.hong 2003-12-03 19:30:05 UTC
fixed in cws i18n09.
Comment 10 karl.hong 2003-12-17 23:26:21 UTC
verified in i18n09.
Comment 11 lohmaier 2004-01-15 21:10:41 UTC
*** Issue 24383 has been marked as a duplicate of this issue. ***
Comment 12 stefan.baltzer 2004-02-04 18:25:55 UTC
SBA: Verified in CWS i18n09. Set to fixed.
Comment 13 stefan.baltzer 2004-02-04 18:26:21 UTC
SBA: Set to verified.
Comment 14 lohmaier 2004-02-12 17:44:33 UTC
*** Issue 25202 has been marked as a duplicate of this issue. ***
Comment 15 mci 2004-04-28 10:26:47 UTC
*** Issue 26520 has been marked as a duplicate of this issue. ***
Comment 16 lohmaier 2004-05-18 21:33:35 UTC
*** Issue 29319 has been marked as a duplicate of this issue. ***
Comment 17 stefan.baltzer 2004-05-24 17:54:39 UTC
SBA: OK in build 680_m39. Closed.
Comment 18 edsuom 2004-10-12 22:51:31 UTC
I think this issue deserves much higher priority. Because of it, OOo all too
often decides to put a line break between a number and a left parenthesis. In my
legal-type writing, there are a lot of such cases: 35 U.S.C. 102(b), Fig. 1(b),
etc. When it does, there is absolutely no way for me to prevent the line break
except forcing a line break before the number, and that prevents the right edge
of the paragraph from lining up properly with the justified formatting that I use.

See attached example file.
Comment 19 edsuom 2004-10-12 22:59:00 UTC
Created attachment 18326 [details]
Should not be a line break in "102(e)"
Comment 20 lohmaier 2004-10-16 17:31:49 UTC
*** Issue 35621 has been marked as a duplicate of this issue. ***