| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
font logic on the PDF side and freetype rendering on the fitz side.
|
|
|
|
|
|
|
|
|
|
buffer, it allocates a dynamic string. Unfortunately it still printed the static string. This fixes disappearing objects in the pdftool show command.
|
|
|
|
"'i' before 'e' except after 'c'," goes the rhyme.
|
|
As far as I can tell, restrict only matters on the declaration side and
doesn't mean anything in a cast. Unlike const. Flagged by Coverity.
|
|
instead. Workaround for broken LaTeX or PDF PT 2.37 (pdf-tools.com) generated files.
|
|
|
|
|
|
|
|
|
|
|
|
Header changes which were omitted in the original patch.
|
|
Allow passing const data into the api without generating warnings.
|
|
Currently the implementation of 'mupdftool draw' looks for a .pdf file
extension to distinguish filename arguments from page range arguments.
Prior to this patch 'mupdftool draw FILE.PDF' would print the usage
since no filename was recognized. This commit adds the upcase version.
Really, something more robust should be used, like looking for valid
page ranges, and testing arguments for existance in the filesystem.
|
|
I find this useful when tracing through the code.
|
|
The original patch adding v4 support forces the dict version back to 2
after parsing some v4 features, despite later range checks for v
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
