document-cli 5.3.4 → 5.3.6

package/README.md

@@ -161,14 +161,14 @@ document-cli docx-extras report.docx
 document-cli metadata report.pdf
 ```
 
-**`set-metadata <input> [output]`** — patches a document's own title/author/subject/keywords, leaving every other field untouched (`--set-title`, `--set-author`, `--set-subject`, `--set-keywords` — the last a comma-separated list); source and target format must match, so run `convert`/`from-package` first if a different target format is also needed. A `pdf` source/target patches the parsed PDF directly (`writePdf`) with no layout engine involved — genuinely lossless for everything else on the page; every other format rebuilds a fresh package from that format's own `ContentDocument`, which for docx specifically is lossy (it drops everything `docx-extras` covers, since `buildDocxPackage` has no way to carry that data through a `ContentDocument`-only rebuild); a `csv` or `svg` source/target is rejected outright, since plain text has no metadata container and a rebuild would silently drop the override:
+**`set-metadata <input> [output]`** — patches a document's own title/author/subject/keywords, leaving every other field untouched (`--set-title`, `--set-author`, `--set-subject`, `--set-keywords` — the last a comma-separated list); source and target format must match, so run `convert`/`from-package` first if a different target format is also needed. A `pdf` source/target patches the parsed PDF directly (`writePdf`) with no layout engine involved, and a `docx` source/target patches `docProps/core.xml` directly on the decoded package (`patchDocxMetadata`) with no `ContentDocument` rebuild involved — both genuinely lossless for everything else in the document, the docx path included: comments, footnotes, headers/footers, and numbering definitions (everything `docx-extras` covers) survive untouched, since nothing but the metadata part itself is ever written. Every other format (pptx, xlsx, odt, odp, ods, odg, markdown, rtf) rebuilds a fresh package from that format's own `ContentDocument`; a `csv` or `svg` source/target is rejected outright, since plain text has no metadata container and a rebuild would silently drop the override:
 
 ```sh
 document-cli set-metadata report.docx report.docx --set-title "Q3 Report" --set-author "Finance"
 document-cli set-metadata report.docx report.odt --set-keywords "draft,internal"
 ```
 
-**`outline <input>`** — prints a document's outline: the table-of-contents projection over the tree-form `DocumentTree` read straight off the source document's own bytes — headings nested by heading level, list items nested under their heading or slide, one group per slide (labelled `Slide N`), sheet (labelled with the sheet's own name), or draw page (labelled `Page N`) — rendered as indented text, two spaces per nesting depth. Leaves render their own text (a paragraph's runs, a table's cell text, an image's alt text, a formula's LaTeX) or their kind in brackets when they carry none (`[page-break]`, `[vector]`, `[embeddedObject]`). Works on any of the seventeen readable formats: the command reads the source's own native tree directly (documents.js's `readNativeDocumentTree`) — no bridging conversion runs and no output bytes are discarded — and projects that tree through [`document-outline.js`](../document-outline.js/README.md)'s own `buildOutline`, this command being that package's first real consumer. `--json` emits the outline tree itself — groups as `{ text, level, children }`, leaves as the package leaves they are — rather than a CLI-private shape; a `pdf` source's own `readPdf` parse diagnostics still reach stderr exactly as they would on the matching `pdf-to-docx` command. `--from <format>` names the source format when the input path carries no recognised extension to infer it from — the only way to outline a document read from stdin (`-`), which otherwise has no extension to read at all. Heading nesting depends on the source document actually carrying a heading-level signal on disk (`w:outlineLvl` for docx, `text:outline-level` for odt) — present in anything authored by Word or LibreOffice, and always present for a markdown source, whose own reader parses `#`/`##` headings directly; a docx or odt this ecosystem's own writers produce does not currently stamp that signal even though the paragraph still carries its `Heading1`/`Heading2`-style reference, so outlining a docx/odt generated by this CLI's own conversions loses heading nesting specifically (list nesting and slide/sheet/page grouping are unaffected):
+**`outline <input>`** — prints a document's outline: the table-of-contents projection over the tree-form `DocumentTree` read straight off the source document's own bytes — headings nested by heading level, list items nested under their heading or slide, one group per slide (labelled `Slide N`), sheet (labelled with the sheet's own name), or draw page (labelled `Page N`) — rendered as indented text, two spaces per nesting depth. Leaves render their own text (a paragraph's runs, a table's cell text, an image's alt text, a formula's LaTeX) or their kind in brackets when they carry none (`[page-break]`, `[vector]`, `[embeddedObject]`). Works on any of the seventeen readable formats: the command reads the source's own native tree directly (documents.js's `readNativeDocumentTree`) — no bridging conversion runs and no output bytes are discarded — and projects that tree through [`document-outline.js`](../document-outline.js/README.md)'s own `buildOutline`, this command being that package's first real consumer. `--json` emits the outline tree itself — groups as `{ text, level, children }`, leaves as the package leaves they are — rather than a CLI-private shape; a `pdf` source's own `readPdf` parse diagnostics still reach stderr exactly as they would on the matching `pdf-to-docx` command. `--from <format>` names the source format when the input path carries no recognised extension to infer it from — the only way to outline a document read from stdin (`-`), which otherwise has no extension to read at all. Heading nesting depends on the source document carrying a heading-level signal on disk (`w:outlineLvl` for docx, `text:outline-level` for odt) — present in anything authored by Word or LibreOffice, always present for a markdown source (whose own reader parses `#`/`##` headings directly), and also stamped by this ecosystem's own docx/odt writers (`buildDocxPackage`'s `w:outlineLvl`, `buildOdtPackage`'s promotion to a real `text:h`), so outlining a docx/odt this CLI's own conversions produce nests headings correctly too:
 
 ```sh
 document-cli outline report.docx

package/dist/cli.js

@@ -1174,11 +1174,11 @@ async function runSetMetadata(input, output, options) {
 function registerSetMetadataCommand(program) {
 	const command = program.command("set-metadata <input> [output]").description("patch a document's own title/author/subject/keywords, leaving every other field and every other flag as-is").addHelpText("after", [
 		"",
-		"Two write paths: a pdf source/target patches the metadata directly on the parsed PDF (writePdf), with no layout engine",
-		"involved at all -- genuinely lossless for everything else on the page. Every other supported format (docx, pptx, xlsx,",
-		"odt, odp, ods, odg, markdown, rtf) rebuilds a fresh package from that format's own ContentDocument -- for docx specifically,",
-		"this is LOSSY: it drops anything docx-extras covers (comments, footnotes, headers/footers, numbering definitions),",
-		"since buildDocxPackage builds a fresh package from the ContentDocument alone, with no way to carry that data through.",
+		"Three write paths: a pdf source/target patches the metadata directly on the parsed PDF (writePdf), and a docx source/target",
+		"patches docProps/core.xml directly on the decoded package -- both with no layout engine or ContentDocument rebuild involved",
+		"at all, so everything else on the page (pdf) or in the package (docx -- comments, footnotes, headers/footers, numbering",
+		"definitions included) survives byte-faithful. Every other supported format (pptx, xlsx, odt, odp, ods, odg, markdown, rtf)",
+		"rebuilds a fresh package from that format's own ContentDocument instead.",
 		"",
 		"set-metadata does not convert format -- source and target must match. Run convert/from-package first, then",
 		"set-metadata on the result, if you need a different target format."
@@ -1199,7 +1199,7 @@ function registerSetMetadataCommand(program) {
 }
 //#endregion
 //#region package.json
-var version = "5.3.4";
+var version = "5.3.6";
 //#endregion
 //#region src/program.ts
 function createProgram() {

package/dist/index.cjs

@@ -1522,11 +1522,11 @@ async function runSetMetadata(input, output, options) {
 function registerSetMetadataCommand(program) {
 	const command = program.command("set-metadata <input> [output]").description("patch a document's own title/author/subject/keywords, leaving every other field and every other flag as-is").addHelpText("after", [
 		"",
-		"Two write paths: a pdf source/target patches the metadata directly on the parsed PDF (writePdf), with no layout engine",
-		"involved at all -- genuinely lossless for everything else on the page. Every other supported format (docx, pptx, xlsx,",
-		"odt, odp, ods, odg, markdown, rtf) rebuilds a fresh package from that format's own ContentDocument -- for docx specifically,",
-		"this is LOSSY: it drops anything docx-extras covers (comments, footnotes, headers/footers, numbering definitions),",
-		"since buildDocxPackage builds a fresh package from the ContentDocument alone, with no way to carry that data through.",
+		"Three write paths: a pdf source/target patches the metadata directly on the parsed PDF (writePdf), and a docx source/target",
+		"patches docProps/core.xml directly on the decoded package -- both with no layout engine or ContentDocument rebuild involved",
+		"at all, so everything else on the page (pdf) or in the package (docx -- comments, footnotes, headers/footers, numbering",
+		"definitions included) survives byte-faithful. Every other supported format (pptx, xlsx, odt, odp, ods, odg, markdown, rtf)",
+		"rebuilds a fresh package from that format's own ContentDocument instead.",
 		"",
 		"set-metadata does not convert format -- source and target must match. Run convert/from-package first, then",
 		"set-metadata on the result, if you need a different target format."
@@ -1547,7 +1547,7 @@ function registerSetMetadataCommand(program) {
 }
 //#endregion
 //#region package.json
-var version = "5.3.4";
+var version = "5.3.6";
 //#endregion
 //#region src/program.ts
 function createProgram() {

package/dist/index.js

@@ -1521,11 +1521,11 @@ async function runSetMetadata(input, output, options) {
 function registerSetMetadataCommand(program) {
 	const command = program.command("set-metadata <input> [output]").description("patch a document's own title/author/subject/keywords, leaving every other field and every other flag as-is").addHelpText("after", [
 		"",
-		"Two write paths: a pdf source/target patches the metadata directly on the parsed PDF (writePdf), with no layout engine",
-		"involved at all -- genuinely lossless for everything else on the page. Every other supported format (docx, pptx, xlsx,",
-		"odt, odp, ods, odg, markdown, rtf) rebuilds a fresh package from that format's own ContentDocument -- for docx specifically,",
-		"this is LOSSY: it drops anything docx-extras covers (comments, footnotes, headers/footers, numbering definitions),",
-		"since buildDocxPackage builds a fresh package from the ContentDocument alone, with no way to carry that data through.",
+		"Three write paths: a pdf source/target patches the metadata directly on the parsed PDF (writePdf), and a docx source/target",
+		"patches docProps/core.xml directly on the decoded package -- both with no layout engine or ContentDocument rebuild involved",
+		"at all, so everything else on the page (pdf) or in the package (docx -- comments, footnotes, headers/footers, numbering",
+		"definitions included) survives byte-faithful. Every other supported format (pptx, xlsx, odt, odp, ods, odg, markdown, rtf)",
+		"rebuilds a fresh package from that format's own ContentDocument instead.",
 		"",
 		"set-metadata does not convert format -- source and target must match. Run convert/from-package first, then",
 		"set-metadata on the result, if you need a different target format."
@@ -1546,7 +1546,7 @@ function registerSetMetadataCommand(program) {
 }
 //#endregion
 //#region package.json
-var version = "5.3.4";
+var version = "5.3.6";
 //#endregion
 //#region src/program.ts
 function createProgram() {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "document-cli",
-  "version": "5.3.4",
+  "version": "5.3.6",
   "description": "CLI and interactive Ink TUI for documents.js: every docx/pptx/odt/odp/ods/odg/odf/pdf/odm/odb/xlsx/csv/svg/markdown/rtf conversion, bridge, and editor as a scriptable command or a terminal app.",
   "type": "module",
   "repository": {
@@ -90,9 +90,9 @@
   "packageManager": "pnpm@11.6.0",
   "dependencies": {
     "commander": "^15.0.0",
-    "document-outline.js": "^3.2.4",
-    "document-schema.js": "^5.6.0",
-    "documents.js": "^6.5.2",
+    "document-outline.js": "^3.3.0",
+    "document-schema.js": "^6.0.0",
+    "documents.js": "^7.0.0",
     "ink": "^7.1.1",
     "ink-text-input": "^6.0.0",
     "react": "^19.2.8"
@@ -106,7 +106,7 @@
     "eslint": "^10.8.0",
     "husky": "^9.1.7",
     "ink-testing-library": "^4.0.0",
-    "odf.js": "^6.4.1",
+    "odf.js": "^7.0.0",
     "publint": "^0.3.22",
     "semantic-release": "^25.0.8",
     "tsdown": "^0.22.14",