GNOME Bugzilla – Bug 742561
Unable to print djvu file to PDF file
Last modified: 2018-05-22 16:03:23 UTC
The attached file can only be printed to a PS file (or a physical printer). This takes only a few seconds, however the resultant PS file then takes 1 hour and 17 minutes for either Evince or ps2pdf to convert to a PDF file. This is too long. If one opens this resultant PDF In Windows Vista and prints to XPS via Adobe Reader X, that takes ~10 minutes. If one opens the resultant PDF in Evince and attempts to print to file (PDF) the preparing to print message took minutes to make 1 page of progress. However, it ultimately finished within 10 minutes. It would be good if evince could directly convert djvu into PDF. After all, PDF is THE standard format for printable documents under all operating systems. I have filed bug 742559 about the alternative solution of fixing the awkward PS file that is generated.
This recent (discussion with patches) about JBIG2 support in CairoOutputDev might help: http://lists.freedesktop.org/archives/poppler/2015-January/011204.html (although it is specific to Poppler)
I should have mentioned in the above comment that the djvu file, according to djvudump(1), appears to be just one bilevel JB2 image per page. Unfortunately, it turns out that djvu’s JB2 is not (quite) Jbig2. It was the original proposal for jbig2, but the latter is different. In bug 742559, James Cloos says, "Since Evince needs to decompress the page to view it, it would be best if it were to do such decompression and re-compress when using cairo to generate pdf or ps. At least for bi-level djvu pages." "OTOH the current ps is fine for printing. Perhaps the above only should be done when converting to pdf?" Also, I've noticed that the file did not attach as it is too large. It is available at https://bugs.launchpad.net/ubuntu/+source/evince/+bug/525161/+attachment/4284552/+files/Grammar%204.djvu
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/evince/issues/549.