Word comes through, and the format we cannot read is named

[tannevaled]

word-to-pdf is claimed, through go-ooxml/ooxml v0.1.0 over
go-ooxml/opc v0.1.0 — a new organisation, because nothing in 2 033
repositories matched ooxml, docx, office or excel, and the fleet's
convention puts a packaged format in its own organisation (go-odf/odf,
go-rtf/rtf) while keeping the text formats in go-richdoc.

covered       77
not covered   37
parity       67.5% (77/114), every claim verified

⛔ The format we cannot read is named, not passed over

BentoPDF's own page says this tool takes "DOC, DOCX, ODT, and RTF".

DOCX	go-ooxml/ooxml — new
ODT	go-odf/odf
RTF	go-rtf/rtf
DOC	not read. The pre-2007 binary format is an OLE compound file and nothing in the fleet reads one

The gap is written in the table, the way cbz-to-pdf names CBR, because a
claim whose shortfall is written down can be closed by whoever reads it.

The claim names ParseWord rather than the repository: a "go-ooxml/ooxml
exists" claim would go on saying yes after the Word reader had been dropped in
favour of the other two.

What the new reader found worth writing down

• ⛔ one container, three vocabularies — the opposite of ODF, where four
  bodies share one vocabulary and one walker reads all four. Here w:t,
  a:t and an index into sharedStrings.xml are three different languages
  over one ZIP, so there is one reader per format;
• ⛔ the main part is found by relationship, and on three files LibreOffice
  wrote in the same minute it points at three different paths;
• ⛔ a relationship type must be compared without regard to case: that same
  .xlsx wrote officedocument in lower case where the .docx and .pptx
  wrote officeDocument.

Measured 2026-10-11 against BentoPDF 3a5f146 (v2.8.8, 114 tools), pdfops
and ops at a376bb2 (= v0.13.0), ooxml and opc at v0.1.0, odf
3d1deee (= v0.7.0), convert 45fbb5d, render 3bb5dcf, app
1feda5d, rtf 6bc4897, markdown eafebfd, data 128b6c7.

🤖 Generated with Claude Code