polyfile
pdf-issues
| polyfile | pdf-issues | |
|---|---|---|
| 2 | 2 | |
| 323 | 62 | |
| 0.6% | - | |
| 7.6 | 8.8 | |
| 2 months ago | 6 days ago | |
| Python | ||
| Apache License 2.0 | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
polyfile
- Blind Spots: Automatically detecting ignored program inputs
-
Show HN: I am building a new Python library to read/write PDF files
Be careful with PDF! There are many ambiguities in the specification that are implemented differently between parsers, as well as implicitly accepted malformations that almost all parsers will silently accept without warning. It is very easy to accidentally produce so-called file format schizophrenia: When the same file is rendered differently between two parsers. For example, with PDF, what if you have a PDF object stream that has a length that doesn't agree with the position of its `endstream` token? What if you have a PDF dictionary with duplicate keys? Do you use the value of the first key or the second? What if you have two, valid PDFs concatenated one after the other? Do you render the first or the second? What if an object in the XREF table has an incorrect offset?
Shameless plug: I am one of the maintainers of PolyFile, which, among other things, can produce an interactive HTML hex editor with an annotated syntax tree for dozens of filetypes, including PDF. For PDF, it uses a dynamically instrumented version of the PDFminer parser. It sounds like it might satisfy your use case.
https://github.com/trailofbits/polyfile
pdf-issues
-
Show HN: I am building a new Python library to read/write PDF files
Merely for your consideration, if those were actual issues on that repo, (a) it would allow adding labels to them (as in https://github.com/pdf-association/pdf-issues/issues?q=is%3A... ) (b) folks could comment, acting as a low-rent stackoverflow, and (c) it would allow anyone to contribute new ones versus the "PR against README.md" situation right now
That also more closely matches the mental model of those items: bugs against the specification, whether the official PDF Association agrees that they are or not
-
What to showcase on my github?
https://github.com/pdf-association/pdf-issues https://www.iso.org/standard/75839.html
What are some alternatives?
PyMuPDF - PyMuPDF is a high performance Python library for data extraction, analysis, conversion & manipulation of PDF (and other) documents.
pdfquery - A fast and friendly PDF scraping library.
polytracker - An LLVM-based instrumentation tool for universal taint tracking, dataflow analysis, and tracing.
pdfsyntax - A Python library to inspect and modify the internal structure of a PDF file
release - Potabi's Release Engineering repository
pdfplumber - Plumb a PDF for detailed information about each char, rectangle, line, et cetera — and easily extract text and tables.
mupdf - mirrored from git://git.ghostscript.com/mupdf.git
QuestPDF - QuestPDF is a modern open-source .NET library for PDF document generation. Offering comprehensive layout engine powered by concise and discoverable C# Fluent API. Easily generate PDF reports, invoices, exports, etc.