Getting involved

If you want to log a bug or feature request, use issue tracker.

If you want to discuss Sumatra, use forums.

If you want to contribute translation, read guide to translating SumatraPDF.

Contributing code

If you want to join Sumatra development and contribute some code, the process is simple:

  • write a patch against the latest sources
  • post a patch somewhere on-line e.g. on pastie.org
  • create a new bug in issue tracker and post a link to the patch (unfortunately can't attach patches to bugs because I'm over attachment quota)
  • make sure to describe what the bug is trying to fix and why (not every change is good)
  • you might post to forum that you've wrote a patch
  • I'll review the patch and either incorporate it into sources (if I think it's good) or describe how it needs to be improved before it can be incorporated into sources
You can work on anything you want, but most valuable contributions are those that implement one of the feature requests already in the tracker.

Getting the sources

The sources are hosted on Google Code (latest checkins, bug tracker). You can also see stats by ohloh.

Sumatra consists of:

  • mupdf pdf parsing/rendering library with a few improvements
  • Windows UI code that uses mupdf for rendering PDFs to a bitmap and showing it on screen

You'll need Visual Studio 2010 or 2008 to build. A free Express Edition for C++ will work.


Sumatra is written by Krzysztof Kowalczyk