Testing Evince

Test Documents

There is also bug 300948 looking for test cases for Evince which could go here.

PDF files

• Acrobat browser test suite contains PDF documents testing all sorts of PDF features

Some big ones:

• The Java Language Specification, Third Edition - 684 pages and 5.9 MB

• PostScript Language Reference Manual - 772 pages and 3.9 MB

• PDF Reference, Third Edition, Version 1.4 - 978 pages and 8.9 MB

• PDF Reference, Fifth Edition, Version 1.6 - 1236 pages and 8.8 MB

• Leo Tolstoy: War and Peace - 2882 pages and 5.6 MB

Only one page, but with a 5MB image included:

• lemon_jelly.pdf

This one does work with 0.1.9, but not with 0.3.0, it's got a nice amount of textgroups etc.

• Powerpoint slides in pdf format 5 pages and 387 KB

Font is correct when viewing, but becomes fixed-width when printing. Gnome PDF Viewer prints correctly.

• http://www.softeng.uwaterloo.ca/Current/WKRPT_checklist.pdf

Uses a lot of type 3 fonts (one for each gliph, I think). Very heavy to open and view. (see bug 4332)

• http://prdownloads.sourceforge.net/aglets/manual.pdf?download

Displays properly for the first 6 pages, then it takes a while to render the rest. It looks like the lines on the tables are off as well (see the top of page 7). This is with 0.4.0. I just tested this with 0.5.2 (poppler 0.5.1) and all problems seem to have been fixed.

• http://www.cs.berkeley.edu/~tygar/papers/Keyboard_Acoustic_Emanations_Revisited/ccs.pdf

Using Javascript for animation.

• http://www-user.uni-bremen.de/~skupin/pdfanim/Demos/

• http://www-user.uni-bremen.de/~skupin/pdfanim/Demos/LunarEclipse.pdf

• http://www-user.uni-bremen.de/~skupin/pdfanim/Demos/LorenzAttractor_NoDocJs.pdf

A PDF that uses layers to provide some possibility of customization. Without layers, text appears on top of other text and is unreadable.

• http://www.rpgsheets.com/data/MI_DnDCharSheet23.pdf

A lot of PDF forms to test (see ../Forms):

• http://www.irs.gov/pub/irs-pdf/

DjVu files

There is a large pool of djvu files at http://www.numdam.org ; I'm gonna test a few of them and report here the ones giving issues, if any (where I is Snark on #gnomemeeting).

Apps to inspect the internals of a PDF file

These apps are very useful debugging tools, as they let you explore the internal PDF objects and content streams of a PDF file. They are open source and published on flathub so it's easy to install them.

• https://flathub.org/apps/details/com.itextpdf.RUPS

• https://flathub.org/apps/details/net.sourceforge.Pdfedit

suggestion

Hi, I would suggest an infrastructure where users simply can upload PDFs with category:

• Evince crashes
• Garbage
• Some errors

The problem I see is, that users are supposed to differentiate what is Evince bug and what is a poppler bug. And it is expected that the user if necessary files two bug reports (one again for poppler). I think it should be sufficient if users upload problematic PDFs. I think Bugzilla does not work well for this. And the developers could look in this PDF repository. Then more users would give feedback. -- ThiloPfennig 2005-10-28 16:15:09

The developers are actually the ones who differentiate what is an Evince bug and what is a Poppler bug, the users usually just file bugs against Evince. Once the developers differentiate they inform the users by sending them to the Poppler Bugs page which tells them how to file a new bug against Poppler. It's a problem of using 2 different bugzillas and there isn't much we can do about it. We can't have the developers searching poppler bugzilla for every bug that's filed against Evince otherwise they wouldn't have time to develop and fix bugs. It would be nice if we had some people who were doing the job of coordinating between the two bugzillas, then there wouldn't be an issue. If you wouldn't mind doing the coordination, all that is required is to have an account on both bugzillas and just go for it! -- BryanClark