Issue 89044

Summary:

undesired line break created between bracket and as-character-anchored object

Product:

Writer

Reporter:

owqcd <oc-spam66>

Component:

formatting

Assignee:

AOO issues mailing list <issues>

Status:

CONFIRMED ---

QA Contact:

Severity:

Trivial

Priority:

CC:

hedges, issues, rb.henschel

Version:

OOo 2.4.0

Target Milestone:

---

Hardware:

All

OS:

All

Issue Type:

DEFECT

Latest Confirmation in:

---

Developer Difficulty:

---

Attachments:

Description	Flags
Document showing undesired line break problem	none

Description owqcd 2008-05-05 22:01:27 UTC

Hello,

in a oowriter text, when I write a mathematical formula inside parentheses, line
breaking can occur between the opening parenthesis and the formula. This is
ugly. How can it be prevented ?

Regards

O.C.

Note : the formula is anchored as a character

Comment 1 michael.ruess 2008-05-06 10:15:01 UTC

MRU->AMA: If you have an object like in the attached sample, a line break will
be generated between it and the surrounding brackets. Such objects should alway
break together with brackets, means a character-anchored object should be
treated as text.

Comment 2 michael.ruess 2008-05-06 10:51:08 UTC

Created attachment 53410 [details]
Document showing undesired line break problem

Comment 3 michael.ruess 2008-07-16 12:33:08 UTC

*** Issue 91698 has been marked as a duplicate of this issue. ***

Comment 4 hedges 2011-06-09 12:54:15 UTC

This is not just a problem with mathematical formulas.  It happens with any plain text.  Closing parentheses, braces or brackets should never break the line if they follow a visible character.  A line starting with a closing paren looks really bad, and correcting a document with that problem with shift-enter is time-consuming and difficult, because then if I edit text somewhere else and it flows, the break looks worse.  Thanks!

Comment 5 hedges 2011-06-09 12:56:51 UTC

test - for some reason after putting in a comment it showed me a different bug

Comment 6 Regina Henschel 2011-07-04 08:11:39 UTC

To me it seems the same problem as issue 26448.