created for each input file, with the contents of the file copied into the content stream. Special comments in the input files are parsed to define the page dimensions and font and image resources. Example available at: https://ghostscript.com/~julian/ mupdf-bindings/ • All content is generated from the comments in MuPDF header files. • This documentation is generated from an internal development tree, so free-standing wrappers. – Various improvements to enums and non-copyable class wrappers. – Use /** ... */ comments in generated code so visible to Doxygen. – Improvements to and fixes to reference counting. ∗

created for each input file, with the contents of the file copied into the content stream. Special comments in the input files are parsed to define the page dimensions and font and image resources. Example available at: https://ghostscript.com/~julian/ mupdf-bindings/ • All content is generated from the comments in MuPDF header files. • This documentation is generated from an internal development tree, so free-standing wrappers. – Various improvements to enums and non-copyable class wrappers. – Use /** ... */ comments in generated code so visible to Doxygen. – Improvements to and fixes to reference counting. ∗

created for each input file, with the contents of the file copied into the content stream. Special comments in the input files are parsed to define the page dimensions and font and image resources. Example available at: https://ghostscript.com/~julian/ mupdf-bindings/ • All content is generated from the comments in MuPDF header files. • This documentation is generated from an internal development tree, so free-standing wrappers. – Various improvements to enums and non-copyable class wrappers. – Use /** ... */ comments in generated code so visible to Doxygen. – Improvements to and fixes to reference counting. ∗

created for each input file, with the contents of the file copied into the content stream. Special comments in the input files are parsed to define the page dimensions and font and image resources. Example available at: https://ghostscript.com/~julian/ mupdf-bindings/ • All content is generated from the comments in MuPDF header files. • This documentation is generated from an internal development tree, so automatically handle reference counting so class instances can be copied arbitrarily. • C header file comments are copied into the generated C++ header files. • Compile and link the generated C++ code to create

just like normal documents. See section Supported Input Image Formats in chapter Pixmap for more comments. 35 PyMuPDF Documentation, Release 1.24.2 6.2 Opening a Document To access a supported document given to pages /Outlines 3835 0 R % points to outline tree >> Note: Indentation, line breaks and comments are inserted here for clarification purposes only and will not normally appear. For more information Document. chapter_count is 1, and pages can also be loaded via tuples (0, pno). See this3 footnote for comments on performance improvements. reload_page(page) • New in v1.16.10 PDF only: Provide a new copy

types just like normal documents. See section Supported Input Image Types in chapter Pixmap for more comments. © Copyright 2015-2018, Jorj X. McKie. Last updated on 13. Jan 2018. Created using Sphinx 1.6.6 impossible, we feel that we at least should provide some quantitative information to justify our bold comments on MuPDF’s top performance. Following are three sections that deal with different aspects of performance: be used as iterators, the benefit of this class was too low to maintain it. See the following comments. loadPage(n) / doc[n] now accept arbitrary integers to specify a page number, as long as n < pageCount