Unfortunately, the situation is by no means fixed in Jaunty RC. Opening Simon's good.pdf (https://bugs.launchpad.net/ubuntu/+source/evince/+bug/227186/comments/7) and printing it to pdf with Jaunty RC's evince takes approx. 0.9 sec CPU time and the produced output pdf is approx. 7kB.
Opening Simon's wrong.pdf (https://bugs.launchpad.net/ubuntu/+source/evince/+bug/227186/comments/8) and printing it to pdf takes approx. 1.6 sec CPU time and the produced output pdf is 1.5MB (yes, _mega_bytes). Neither evince nor gv could open the resulting pdf. The difference in CPU usage seems not much, but the documents in question are quite short. Making a 10 pages long document from Simon's tex source with some copy-pasting and printing it to pdf will take approx. 1 sec CPU time without T1 fonts and 6.5 sec with T1 fonts, and the resulting pdfs are 20kB vs. 16MB. The CPU usage is even worse when opening the print preview. In case of Simon's pdf, it takes 1 sec CPU time to open good.pdf and display its print preview, but takes 21 sec to do the same with wrong.pdf. With the 10 pages long document it's 2 sec vs. 223 sec. The print preview looks as expected for the documents without T1 fonts, but looks terrible with T1. -- Evince doesn't print PDF files https://bugs.launchpad.net/bugs/227186 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
