This bug is reported in German LO-user-list the second time. Create a new document. Write Text down and fill one page by copying. All the characters must be black. Export this page to MyDoc.pdf Start gs -q -o - -sDEVICE=inkcov MyDoc.pdf on konsole. It will give something like 0.10067 0.10067 0.10067 0.10067 CMYK OK Cyan, magenta and yellow are also part of the document. So if you give this document to a print-shop you have to pay and will get a colored print instead of a print, which contains only black. Tested here with LO 6.4.4.2 on OpenSUSE 15.1 64bit rpm Linux
I can confirm the buggy behavior with LO 6.4.4.2 (x64) on Windows 10. If I write a text with Writer whose font color is either set to ›Automatic‹ or ›Black‹ and then create a PDF file from it, the apparently black text is not black, but is rasterized in RGB colors.
This bug bothers me as well. It has been around forever. This causes black text to be ~90% black when printed from PDF, which is mostly visible from jagged edges of characters, makes a 600 dpi printer look like 150 dpi. For a workaround you can print to PDF, choose "Grayscale" colors from printer options. In this case a PDF with text as CMYK black turns out. This obviously works only with grayscale documents. I will attach example PDF files and also corresponding color inspector screenshots from Adobe Reader Professional.
Created attachment 173751 [details] Example document, just some text
Created attachment 173752 [details] Printed using PDF printer with colors (turns out gray)
Created attachment 173753 [details] Printed using PDF printer with grayscale (turns out real black)
Created attachment 173755 [details] Color inspector on text printed as colors
Created attachment 173756 [details] Color inspector on text printed as grayscale
Dear Robert Großkopf, 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
Bug is still the same in LO 7.6.0.1 on OpenSUSE 15.4 64bit rpm Linux.