Issue 33518 - Unable to visually see forced page breaks
Summary: Unable to visually see forced page breaks
Alias: None
Product: Writer
Classification: Application
Component: ui (show other issues)
Version: OOo 1.1.2
Hardware: All All
: P3 Trivial with 12 votes (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
: 43119 65150 67344 82353 (view as issue list)
Depends on:
Reported: 2004-08-28 23:04 UTC by graaf
Modified: 2013-02-07 22:35 UTC (History)
3 users (show)

See Also:
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description graaf 2004-08-28 23:04:28 UTC
Users are unable to see where they have inserted manual page breaks. Forced
line- and column breaks are visible when '(Show) Nonprinting Characters' is
selected; page breaks are not (inconsistent, hides important information).

In MSO this is solved by showing following flag where the page break occurs:

     ------------Page Break-----------
Comment 1 Regina Henschel 2004-08-29 00:53:22 UTC
In OOo the manuel page break is shown by a thin blue line at the beginning of
the new page. Unfortunately you can hardly distinguish it from the normal gray
line. Therefore one of my first things in customizing OOo is, to set it to a
loud color. You can do that in Tools > > Appearance > 'Page and
column breaks'. Perhabs OOo should use a default color, which is more noticable.
Comment 2 graaf 2004-08-29 01:23:25 UTC
I changed the color to magenta, but couldn't see the line until I switched the
Text Boundaries on. No wonder I couldn't see it in the first place :)

I suspect many people has turned the Text Boundaries off (as I had) out of habit
(Word hasn't have them). It's nice to have them as option, but I don't use them
as I feel that they clutter the page.

Even when the feature is there, the behavior is still inconsistent with other
types of breaks:
1) Line and Column break indicators are visible only when 'Nonprinting
Characters' is selected. Page break indicators' visibility is linked with Text
2) Line and Column breaks have the indicator in the place where the break
occurs. Page break indicator is in the next page (and invisible if only the page
where the break occurs is visible)
Comment 3 michael.ruess 2004-08-31 07:46:15 UTC
MRU->BH: Page breaks should better be handled by "nonprinting characters".
Comment 4 sajer 2004-12-20 17:16:49 UTC
Please take a closer look at kaaredyrets suggestion here:

"Symbols and colours are just not enough. I think that text borders, borders 
around frames etc. could be enhanced just a little, visually... BTW, why not 
look at how it is done i MS Word, normal view: a line indicates the page break 
and in the middle it says 'page break', 'section break' using a small font. It 
is IMPOSSIBLE to misunderstand it or even not to see it."
Comment 5 lohmaier 2005-09-23 19:19:17 UTC
*** Issue 54070 has been marked as a duplicate of this issue. ***
Comment 6 hierogrammate 2005-11-28 12:14:26 UTC
I agree with the last poster. I need something more obvious that just a colored
line. The "in your face" line labeled "page break" in MS Word is a good
example.. something that can be revealed or hidden with the "Nonprinting
Characters" command. Maybe not critical, but when you are hours on end editing a
doc with sleepy eyes, loud markers like that help a lot.
Comment 7 temcat 2006-03-19 12:50:40 UTC
Agreed, Word's implementation of breaks is perfect. Why not copy it? Now I can't
see breaks because I turn off text boundaries (they distract and irritate me)
and normally use Web Layout mode (because Writer lacks Word-like Normal mode).
Comment 8 lohmaier 2006-05-19 16:54:08 UTC
*** Issue 65150 has been marked as a duplicate of this issue. ***
Comment 9 lohmaier 2006-07-14 19:43:47 UTC
*** Issue 67344 has been marked as a duplicate of this issue. ***
Comment 10 pagalmes.lists 2006-07-24 09:36:10 UTC
I something is planned about this issue, could you please also have a look at
issue 67345 ?
Comment 11 Regina Henschel 2007-10-07 14:44:40 UTC
*** Issue 82353 has been marked as a duplicate of this issue. ***
Comment 12 ace_dent 2008-05-19 10:57:46 UTC
*** Issue 43119 has been marked as a duplicate of this issue. ***
Comment 13 bettina.haberer 2010-05-21 14:59:17 UTC
To grep the issues easier via "requirements" I put the issues currently lying on
my owner to the owner "requirements".