On Debian Wheezy with Libreoffice 3.4.3 Build 302.
Nonprinting Character Button (Ctrl+f10) not working
This button is located in the Standard Toolbar and has the pilcrow for an icon.
I was given a file of poetry to format that had been "pre-formatted" using multiple spaces and carriage returns. (not tabs, styles, or forced page breaks). Somehow in toggling the Nonprinting Character Button on and off, it got stuck in the off position. Neither pressing the button or Ctrl+f10 show the nonprinting characters.
Using apt-get I "purged" libreoffice and libreoffice-writer and then installed them fresh. For some reason the nonprinting character button is still not working.
tags: hidden, view, paragraph mark, invisible
Tools > Options > Formatting Aids shows a list of nonprinting characters to display.
Somehow in toggling the nonprinting character button on and off (while zooming in and out), the carriage return, tab and space characters were deselected, without me actually going to the Formatting Aids menu and deselecting them.
(In reply to comment #1)
> Somehow in toggling the nonprinting character button on and off (while zooming
> in and out), the carriage return, tab and space characters were deselected,
> without me actually going to the Formatting Aids menu and deselecting them.
Maybe duplicate of Bug 40482. Check if happens while printing or exporting in PDF in your case.
NOT reproduced with
Ubuntu 10.04.3 x86
Linux 2.6.32-35-generic Russian UI
Can you try with 3.4.4?
> Ctrl+f10 not working
It is not a bug. On Linux so should be
> Nonprinting Character Button not working
Try View->Nonprinting characters
> "pre-formatted" using multiple spaces
Use Edit->Find&Replace and there in field "Search for" enter two spaces and in field "Replace with" enter one space and press "Replace all" several times until all duplicate spaces disappears.
Yes. It happened to my also.
Unistalling it will not work, because the "config" is still save.
I think it happens before, but in 3.4.5 an onwards, it does not happend (not sure).
Close completely libreoffice.
Then you got a folder named "user".
Erase it, or rename it "user.back"
Open again libreoffice.
You get it working again.
I dont know why it happens. I only know how to patch it...
Im not a developer, just a dude ;P
Thanks for additional testing. So, I have some questions:
- not seen all non-printing characters or only spaces?
- it not works on 3.4 and 3.5?
- it installed from libreoffice.org or from distro repo?
- which distro used?
- it reproducible on another computer?
I can confirm Nonprinting characters are not shown in OSX version of Writer 220.127.116.11 and seems that they are not working.
The issue is that by default all nonprinting characters except Hidden Text are disabled in preferences/writer/Formating Aids.
Perhaps it would be better to enable spaces, tabs, breaks by default.
Thanks for additional testing
Resetting the version number to 3.4.3, like in original description. Please note that the 'Version' field should contain the FIRST version in which the bug appears (is known to appear), and NOT the last one!
I think this issue is really a duplicate of bug 40482, which was fixed in 3.4.4 or 3.4.5. Some arguments:
* Original report was for LibreOffice 3.4.3.
* Not reproducible in LibreOffice 3.4.4 according to comment #3.
* "in 3.4.5 an onwards, it does not happen" according to comment #5.
The only comment which mentions this issue *after* the fix is comment #7 (Writer 18.104.22.168). But Borut Cadez gives an explanation himself: "The issue is that by default all nonprinting characters except Hidden Text are disabled in preferences/writer/Formating Aids." This means, the issue seen by Borut Cadez is an issue about "default" settings, not about the command 'Nonprinting characters' not working. Changing the default settings would be another issue, and an enhancement request, not a bug report. (Sidenote: IIRC, the default settings of LibreOffice 3.5.3 do enable spaces, tabs, breaks by default, so the suggestion of Borut Cadez don't even need an enhancement request.)
Therefore, closing this bug as duplicate of bug 40482.
If you find reasons which show that this is a different issue, or if this issue is still reproducible for you with LibreOffice 22.214.171.124 or better, feel free to reopen this bug report.
*** This bug has been marked as a duplicate of bug 40482 ***