Issue 11748 - line breaks wrong with smart quotes
Summary: line breaks wrong with smart quotes
Status: CLOSED FIXED
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: 644
Hardware: Other Other OS
: P2 Trivial (vote)
Target Milestone: ---
Assignee: michael.ruess
QA Contact: issues@sw
URL:
Keywords:
: 12977 (view as issue list)
Depends on:
Blocks:
 
Reported: 2003-02-22 15:58 UTC by ingenstans
Modified: 2013-08-07 14:43 UTC (History)
4 users (show)

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


Attachments
Example winword .doc file (24.00 KB, application/octet-stream)
2003-03-18 16:40 UTC, caolanm
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description ingenstans 2003-02-22 15:58:28 UTC
When a line ends with a full stop, a question mark, or an exclamation point 
followed by a double closing quote character, it can break between the 
punctuation marks, like this:




"Do you love her?


"




"Yes. I love her.


"




"You unutterable bastard!


"




I know that in general it's right to break lines after punctuation; but this is 
wrong. 




Should a full stop be a line-break character when it is followed by anything 
other than a space? I'm not sure that it should be. Think about alt.pedantry.


linebreaks




or www.openoffice.


org




Neither looks right. In any case, the quotes example is definitely wrong, and 
should be fixed before release. I don't remember it happening in earlier 
versions of the software so this is probably a regression thing with 644.
Comment 1 h.ilter 2003-02-28 14:39:17 UTC
MRUs area.
Comment 2 ingenstans 2003-03-01 20:18:17 UTC
still there in 644_m4. This only shows up when there is a punctuation 
mark before the quote. words that don't end in puctuation wrap as they 
should, with the whole word, and both quotes, moving own to the next 
line. 
Comment 3 michael.ruess 2003-03-07 13:31:08 UTC
MRU->FME: I also think, that the line shouldn't break between the
interpunction and the quote. A case for the break iterator?
Comment 4 frank.meies 2003-03-10 07:30:34 UTC
FME->Karl: Break iterator issue.
Comment 5 caolanm 2003-03-18 16:40:41 UTC
Created attachment 5133 [details]
Example winword .doc file
Comment 6 caolanm 2003-03-18 16:45:24 UTC
Break Iterator is breaking on fullstops not followed by whitespace in
6.1/1.1 candidate. It did not in 6.0. i.e. in the attached .doc add
content before the final hyperlink it will break on /regression
fullstops in 6.1/1.1 and will not in 6.0/1.0. A regression and a very
important incompatability with both older versions and microsoft work.

cmc->mru: This is an important one for interoperability/regression.
Comment 7 ingenstans 2003-03-18 18:06:30 UTC
Might this be related to #12221 and #12036, which were also apparently 
breakiterator regression bugs? I had mail this morning saying both had 
been fixed, and that they had been broken by a fix made to somehting 
on the internal bug database.


Comment 8 karl.hong 2003-03-18 19:37:15 UTC
No, this bug is different from i12221. It is due to the new ICU line 
break iterator problem.
Comment 9 frank.meies 2003-03-26 14:43:03 UTC
FME->Karl: Please also consider text like this: 
c:\mypath\myfile.sxw
Comment 10 caolanm 2003-04-03 08:15:36 UTC
*** Issue 12977 has been marked as a duplicate of this issue. ***
Comment 11 karl.hong 2003-04-08 01:43:44 UTC
I make those puctuations, like period, question mark, colon, etc. as 
part of words, which cause them only can be broken by following space.
Comment 12 frank 2003-04-23 14:10:21 UTC
Reassigning for QA
Comment 13 michael.ruess 2003-04-23 16:34:00 UTC
Checked fix in CWS apps61beta2.
Comment 14 michael.ruess 2003-04-23 16:34:29 UTC
Verified. Fix will be included in OO 1.1 Beta2.
Comment 15 michael.ruess 2003-05-14 08:38:30 UTC
closed.
Comment 16 vliscony 2003-05-22 20:01:56 UTC
I just installed 1.1beta2 and tried this again. those closing quotes 
after a punctuation keep dropping to the next line.
Comment 17 vliscony 2003-05-22 20:30:12 UTC
correction; it is working correctly now. 1.1beta2 is not too clearly 
marked, so I thought I was using it, but I wasn't.
thanks for the progress.