When View -> Non-printing Characters is enabled in Writer, the non-printing characters in question are rendered in the font of the text to which they belong. However, if the font in question doesn't contain the necessary characters, the non-printing characters are invisible whether or not View -> Non-printing Characters is enabled. For instance, on OSX, the font "Baoli SC" does not contain a paragraph mark symbol (U+00B6 PILCROW SIGN). To reproduce: 1. Open the attached document 2. Ensure View -> Non-printing Characters is enabled Notice that the first paragraph (font: Baoli SC) has no paragraph mark, while the second paragraph (font: Hiragino Sans GB) does.
Created attachment 104703 [details] Document which demonstrates the issue
Created attachment 104704 [details] Image showing the missing paragraph mark
Another example: "Hoefler Text" has the Pilcrow sign character, but not the bullet character used to denote whitespace
If a font does not contain standard characters, the issue is on the font designer side. So closing as NotOurBug. Feel free to reopen if you think I am missing something. Best regards. JBF
The two fonts I picked are standard fonts on OSX, and where there are two it's very likely that there are others. Not every font covers every character of English/European text, especially in the case of CJK (such as the example I gave of "Baoli SC") and CTL fonts. The bug is that OL assumes that the display of non-printing characters can be achieved through any random font. For ordinary text, the font fallback mechanism would take care of this, but it seems this is not applied for the non-printing characters. There are two plausible solutions: 1. Pick a standard font (on each platform?) to render the presence of non-printing characters or 2. Allow the font fallback mechanism to also apply to the non-printing characters
Other standard CJK fonts (specifically Chinese) on OSX which do not contain the Pilcrow sign: Songti SC Black Xingkai SC Light Xingkai SC Bold Yuanti SC Regular Yuanti SC Bold
The "standard font" option is possibly already applied for linefeeds (rather than paragraph breaks) that are made visible. The linefeed character always looks the same regardless of the text font or character size
Created attachment 104791 [details] Font test sheet showing the issue in more fonts
Created attachment 104792 [details] Image of font test sheet
Hi Kevin Suo, What do you think about this bug report ? Best regards. JBF
Created attachment 104889 [details] Screenshot: Reproduce with "华文新魏" font I do not reproduce with the original attachment 104703 [details], becaue I do not have the Baoli SC font installed so the font was fallback to Simsun. However, I do reproduce the missing paragraph mark when I changed the font to "华文新魏". See screenshot. I agree with Matthew Francis that for non-printing chars, the font should always fallback to western font (the most appropiate should be the libreoffice-built-in fonts like libration fonts etc.) Set to NEW.
(In reply to comment #11) > I agree with Matthew Francis that for non-printing chars, the font should > always fallback to western font (the most appropiate should be the > libreoffice-built-in fonts like libration fonts etc.) Note that if this is handled purely as an issue of fallback, the Pilcrow sign (paragraph) will still be substituted with something random under some symbol fonts - see "Bodoni Ornaments ITC TT" and "Symbol" in the later test image It might not be a very interesting corner case, but possibly worth thinking about anyway
Created attachment 104903 [details] Screenshot: Difference in size of non-printing characters Attaching one more image as a reminder that there is currently also an inconsistency between the size of the linefeed and paragraph markers The space bullet and Pilcrow sign are rendered at the size of the text - even to the point that they wander off the edge of the page entirely when the font size is large enough The linefeed marker is, in contrast, resolutely small at any font size Linefeed and paragraph at least probably want to be at the same scale, though which option is better I'm not sure. Something to consider if the rendering is changed.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.0.0.5 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-09-03
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
Dear Matthew Francis, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Same with Font Wingdings. Pilcrow is a star, space has no symbol. Version: 6.3.6.2 (x86) Build ID: 2196df99b074d8a661f4036fca8fa0cbfa33a497 CPU threads: 4; OS: Windows 6.1; UI render: default; VCL: win; Locale: es-MX (es_MX); UI-Language: en-US Calc: threaded
Dear Matthew Francis, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug