Created attachment 1762906 [details] Affected PDF When printing the attached document from evince, I get rectangles instead of several letters with accents. If I open the pdf in fontforge, I get the selection from following fonts: NPNKSU+LiberationSerif CIYLSW+LiberationSerif-Bold OGDMVH+LiberationSerif LKUZVO+LiberationSerif-Bold All of them get a warning: In GID 0 the advance width (748) is greater than the stated maximum (0) Subsequent errors will not be reported. If I print from Libreoffice Draw, the accents are correct. My printer is HP LaserJet M1536dnf, using CUPS temporary queue in GTK dialog in Evince, but I got the same results with a permanent queue installed by '-m everywhere'. Would you mind looking into it?
Created attachment 1762907 [details] PDF which comes to CUPS Ah, sorry, I used this PDF when investigating fonts - it's the PDF which evince sends to CUPS.
Hi Zdenek, I can not reproduce the issue yet but it would help me to know which letters are wrong. My printer prints it without issues via the temporary queue (HP LaserJet Pro MFP M127fw).
It would also help to know which filters were applied. I tried sequence of "pdftopdf, pdftops, hpps" so far and it still shows all the glyphs.
Hi Marek, thanks for looking into it! (In reply to Marek Kašík from comment #2) > Hi Zdenek, > > I can not reproduce the issue yet but it would help me to know which letters > are wrong. The garbled letters are žš (in all versions - upper and lower cases, bold and normal). I'll attach a scan. (In reply to Marek Kašík from comment #3) > It would also help to know which filters were applied. I tried sequence of > "pdftopdf, pdftops, hpps" so far and it still shows all the glyphs. The only filter used is pdftopdf and a pdf is sent to the printer.
Created attachment 1763615 [details] printed doc
(In reply to Marek Kašík from comment #3) > I tried sequence of "pdftopdf, pdftops, hpps" so far and it still shows all the glyphs. The issue seems to be connected to PDF format, so if you convert it to postscript the issue isn't triggered. I checked the cups log when printing from libreoffice - the same filter is used, but the file sent to CUPS has only two fonts defined according fontforge.
Created attachment 1763624 [details] PDF from Libreoffice
Created attachment 1763700 [details] modified pdf Hi, Thank you for the scan and the libreoffice pdf. Maybe I've found the cause of this bug. The font descriptors used for the fonts for which the printer does not print the characters have Flags set to 32 which means that the characters there are all from "Adobe standard Latin character set" (which includes the žšŽŠ). The font descriptors with characters which have caron but are not in the Adobe standard Latin set have Flags 4. Libreoffice created font descriptors with Flags == 4 only. Could you try to print the attached pdf in which I've changed the flags to 4? If this would be the case then it would mean that a consumer of the pdf does not have correct table for the Adobe standard Latin set and rejects the žšŽŠ.
Hi Marek, I'm not sure what are the expected results of printing the modified document or if I should print via Evince again, so I'm going to attach three scans. One is from printing the modified pdf via 'lp' command (to prevent cairo's meddling with your changes) via permanent queue which is created by CUPS ppd generator. The PPD generator is the same as a temporary queue uses, so the result should be the same as if you print it via temporary queue, but without cairo's meddling - it has žšŠŽ as rectangles too and in addition a dash and a apostrophe are rectangles too. The next scan is for the comparison with the first and to verify how your changes impacted the pdf - it is again from a permanent queue with cups PPD generator, but now with original PDF - and everything is printed ok. So to sum it up - modified pdf was printed out badly in comparison to original pdf via lp command and the same queue. The last scan is a printout of modified pdf via evince with cairo in the game - the output is the same as it is in comment #5.
Created attachment 1763952 [details] printed modif pdf - lp, permanent queue, -m everywhere
Created attachment 1763953 [details] printed orig pdf - lp, permanent, -m everywhere
Created attachment 1763954 [details] printed modif pdf - evince, temporary
Thank you for the results. The missing dash and apostrophe is interesting result (which I was actually expecting before but they were printed correctly). I'll return to this once I'll have some time.
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.