Download it now!
Bug 102350 - Formatting Marks: Default settings
Summary: Formatting Marks: Default settings
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected)
Hardware: All All
: medium enhancement
Assignee: Not Assigned
Depends on:
Blocks: Options-Dialog Formatting-Mark
  Show dependency treegraph
Reported: 2016-09-22 04:21 UTC by Yousuf Philips (jay) (retired)
Modified: 2020-03-09 13:28 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Yousuf Philips (jay) (retired) 2016-09-22 04:21:53 UTC
By default LO shows the following formatting marks ( Tools > Options > LibreOffice Writer > Formatting Aids > Display of )

* Paragraph end
* Soft hyphens
* Spaces
* Non-breaking spaces
* Tabs
* Breaks

and hides

* Hidden text

I think that non-breaking spaces and soft hyphens should be hidden and hidden text should be shown. The display of non-breaking characters and soft hyphens as gray highlights causes more harm than benefit in its current broken state (bug 58434) and without hidden text enabled, hidden text would never be visible to users until they first new to enable this in the options dialog.
Comment 1 V Stuart Foote 2016-09-22 14:21:30 UTC
Would agree if bug 58434 gets resolved. Otherwise the current defaults work--really is no need to show hidden text by default, advanced users likely to use it will know to set it enabled.
Comment 2 Timur 2016-09-22 14:45:44 UTC
Since reported already confirmed his own bug (which is not favorable), I can't but support this. 
With Hidden text checked in Formatting Aids, it's still not shown, unless we use NpC (just created acronym that stands from Non-printing Characters).
MSO also works like that, NpC turns all on, and that you can change (in 3 clicks, while LO options take 5)
Primary concern should be non-advanced users, which would hardly figure all this out. So, it's easier to have it checked and let those advanced to uncheck this.
Comment 3 Xisco Faulí 2020-03-09 13:28:24 UTC
Please add keyword 'needsUXEval' and CC '' if input from UX is needed.