Bug 63662

Summary: "Manual Column Break" is visible onscreen even when "nonprinting characters" is off
Product: LibreOffice Reporter: haim kilov <haimk>
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: NEW --- QA Contact:
Severity: normal    
Priority: medium CC: cno, jmadero.dev
Version: 3.6.0.0.alpha1Keywords: regression
Hardware: All   
OS: All   
Whiteboard: NeedsDevEval
i915 platform: i915 features:
Attachments: The text "Manual Column Break" is visible onscreen even when "nonprinting characters" is off. See the screenshot. OpenOffice treats the odt file correctly. (This is the odt file)
This is the screenshot.

Description haim kilov 2013-04-17 23:00:28 UTC
Created attachment 78158 [details]
The text "Manual Column Break" is visible onscreen even when "nonprinting characters" is off. See the screenshot. OpenOffice treats the odt file correctly. (This is the odt file)

The text "Manual Column Break" is visible onscreen even when "nonprinting characters" is off. See the screenshot. OpenOffice treats the odt file correctly.
Comment 1 haim kilov 2013-04-17 23:01:57 UTC
Created attachment 78159 [details]
This is the screenshot.
Comment 2 Joel Madero 2013-04-18 01:34:36 UTC
Thank you for reporting this issue! I have been able to confirm the issue on:
Version 3.6.5.2 
Platform: Bodhi Linux 2.2 x64
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 
As I've been able to confirm this problem on an earlier release I am changing the version number as version is the earliest version that we can confirm the bug, we use comments to say that the bug exists in newer versions as well.

Marking as:

New (confirmed)
Trivial - doesn't prevent high quality work nor slow it down, just a trivial bug
Lowest - default for trivial bug, appropriate here

Keywords - 

Whiteboard Status - ProposedEasyHacks

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 
LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link:
https://wiki.documentfoundation.org/QA/BugTriage

There are also other ways to get involved including with marketing, UX, documentation, and of course developing -  http://www.libreoffice.org/get-help/mailing-lists/. 

Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material
Comment 3 haim kilov 2013-04-18 01:55:28 UTC
I would disagree with the "lowest" priority and with the statement that the bug "doesn't prevent high quality work nor slow it down". While the bug is indeed trivial, a (non-IT) client who looks at the screen representing his texts and sees "Manual Column Break" will be astonished and possibly annoyed. Client's happiness is important! [Telling the client that this will not be visible in the printout might make him even more annoyed.]
Comment 4 Joel Madero 2013-04-18 04:34:35 UTC
I suspect that anyone using the feature would be at least quasi tech knowledgeable. But, I can see your point, raising it to minor - low priority.


Minor - can perhaps slow down or confuse users but hopefully this would be a one time confusion (once they saw that it didn't print this way they would know it's quite a minor irritation).

Low - default for minor bugs
Comment 5 Joel Madero 2014-02-27 22:55:19 UTC
In order to limit the confusion between ProposedEasyHack and EasyHack and to make queries much easier we are changing ProposedEasyHack to NeedsDevEval.

Thank you and apologies for the noise
Comment 6 Cor Nouws 2014-04-01 12:48:01 UTC
Hi,

I hear people complaining about this. It is simply stupid when you have to read text that has "manual column break" displayed though :)

Was OK in 3.5. Fist bad is 3.6.0alpha1 > regression
Setting severity & priority to normal
Comment 7 kengraebe 2014-08-15 21:32:05 UTC
wouldn't everyone be happy if show non printing characters used other than a paragraph symbol to show the LOCATION of a unique character for a line, column &
page break. i would as i have huge problems with multiple tables within frames within each of 3 columns. it would save me the trouble of filing a bug report or enhancement request.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.