Skip to content

The object graph as JSON: pdf-to-json #113

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tannevaled merged 1 commit into from
Oct 12, 2026
Merged

The object graph as JSON: pdf-to-json #113

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -766,9 +766,9 @@ bentoparity -tools ~/src/bentopdf/docs/tools -pdfops ./pdfops -src ~/src/go-pdfk
```

```
covered 88
not covered 26
parity 77.2% (88/114), every claim verified
covered 89
not covered 25
parity 78.1% (89/114), every claim verified
```

⛔ **It refuses to report a figure if a single claim cannot be checked.** A
Expand Down
11 changes: 11 additions & 0 deletions parity/table.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -104,6 +104,17 @@ var BentoPDF = []Claim{
// repository could see.
{Tool: "pdf-to-word", Claim: "verb:word"},
{Tool: "pdf-to-excel", Claim: "verb:excel"},
// ⛔ pdf-to-json is NOT the text. BentoPDF's own page says so plainly —
// "the raw PDF object structure, not extracted text content" — and
// points anyone wanting the text at prepare-pdf-for-ai instead. So the
// claim is the object graph, which `pdfops objects` writes: the trailer
// and everything reachable from it, a stream's dictionary and length
// without its bytes.
//
// Reachable from the trailer, and not every object in the file: an
// object no reference points at is in the bytes and in nobody's
// document, and listing it beside the rest would say the two are alike.
{Tool: "pdf-to-json", Claim: "verb:objects"},
{Tool: "extract-images", Claim: "verb:images"},
{Tool: "extract-attachments", Claim: "verb:detach"},
{Tool: "add-attachments", Claim: "verb:attach"},
Expand Down
Loading