Bug 42617 - FORMATTING: Non-printable characters cannot be turned on
Summary: FORMATTING: Non-printable characters cannot be turned on
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.4.3 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-05 02:25 UTC by szebenyib
Modified: 2011-11-05 09:22 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
An illustration of the characters not appearing. (120.89 KB, image/png)
2011-11-05 02:25 UTC, szebenyib 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description szebenyib 2011-11-05 02:25:15 UTC 
Created attachment 53177 [details]
An illustration of the characters not appearing.

Problem description:
Cannot make non-printable characters visible


Steps to reproduce:
1. Click on the inverted 'P' icon.
2. Or pressing Ctrl+F10

Current behavior:
I cannot see the whitespace characters or end of line markers (those inverted P-s)
Expected behavior:
They should be visible.
Platform (if different from the browser): 
Arch Linux              
Browser: Opera/9.80 (X11; Linux x86_64; U; hu) Presto/2.9.168 Version/11.52
Comment 1 Korrawit Pruegsanusak 2011-11-05 08:30:25 UTC 
[NOT REPRODUCIBLE] LibreOffice 3.4.3 english-locale, Ubuntu 11.10

Maybe locale/platform specific?
Comment 2 Korrawit Pruegsanusak 2011-11-05 08:48:53 UTC 
Maybe duplicate of Bug 40482 ?
Comment 3 szebenyib 2011-11-05 09:09:41 UTC 
I had to switch on everything in Tools > LibreOffice Writer > Formatting aid > check Paragraph ends. That has sovled it, but who has switched it off? I cannot remember when they have disappeared, should it happen again I will notice that immediately. Thanks for that post of the other bug, without it I would have a useless editing tool. Thank you!!
Comment 4 Korrawit Pruegsanusak 2011-11-05 09:22:40 UTC 
My pleasure :)

Anyway, if it happen again, could you please check if it's same as bug 40482?
1. if it's same, maybe you can post your comment *there* (not here)
2. but if it isn't the same, you may report the new bug and describe what did you do to get this problem occur again

Thanks!