docrev 0.9.14 → 0.9.15

package/README.md

@@ -179,11 +179,12 @@ my-report/
 ├── references.bib
 ├── rev.yaml
 ├── paper.md              ← combined sections (auto-generated)
-├── my-report.docx        ← output for collaborators
-└── my-report.pdf         ← output for journals
+└── output/
+    ├── my-report.docx    ← output for collaborators
+    └── my-report.pdf     ← output for journals
 ```
 
-The output filename is derived from your project title in `rev.yaml`. Citations are resolved, equations rendered, and cross-references numbered.
+The output filename is derived from your project title in `rev.yaml`. Citations are resolved, equations rendered, and cross-references numbered. Set `outputDir: null` in `rev.yaml` if you'd rather have the built files land alongside `paper.md` (legacy layout).
 
 ### Starting from an Existing Word Document
 
@@ -201,14 +202,32 @@ Layout is controlled in `rev.yaml`:
 
 ```yaml
 title: "My Document"
-output:
-  docx:
-    reference-doc: template.docx   # your Word template
-  pdf:
-    documentclass: article
-    fontsize: 12pt
+authors: []
+sections:
+  - intro.md
+  - methods.md
+  - results.md
+  - discussion.md
+
+# Where built artefacts land (default: output/). Set to null for the
+# legacy "outputs alongside paper.md" layout.
+outputDir: output
+
+docx:
+  reference: template.docx       # your Word template
+
+pdf:
+  documentclass: article
+  fontsize: 12pt
+  engine: pdflatex               # or xelatex/lualatex for Latin-Extended
+  # Fonts apply only under xelatex/lualatex (fontspec):
+  # mainfont: "TeX Gyre Termes"
+  # sansfont: "TeX Gyre Heros"
+  # monofont: "TeX Gyre Cursor"
 ```
 
+Switch to `engine: xelatex` (or `lualatex`) when the manuscript has Czech/Polish/Croatian/Spanish names or species epithets that `pdflatex` mangles. Under those engines, `mainfont`/`sansfont`/`monofont` are forwarded to pandoc.
+
 Configure your name for comment replies:
 
 ```bash
@@ -321,6 +340,7 @@ Cross-references: `@fig:label`, `@tbl:label`, `@eq:label` → "Figure 1", "Table
 | Build DOCX | `rev build docx` |
 | Build PDF | `rev build pdf` |
 | Build clean + annotated | `rev build docx --dual` |
+| Build with visible track changes | `rev build docx --show-changes` |
 | Sync Word feedback | `rev sync reviewed.docx` |
 | Sync PDF comments | `rev sync annotated.pdf` |
 | Extract PDF comments | `rev pdf-comments annotated.pdf` |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "docrev",
-  "version": "0.9.14",
+  "version": "0.9.15",
   "description": "Academic paper revision workflow: Word ↔ Markdown round-trips, DOI validation, reviewer comments",
   "type": "module",
   "types": "dist/lib/types.d.ts",

package/skill/REFERENCE.md

@@ -61,11 +61,20 @@ rev build pdf                # PDF only
 rev build docx               # DOCX only
 rev build --toc              # Include table of contents
 rev build docx --dual        # Clean + annotated versions
+rev build docx --show-changes  # DOCX with visible track changes (audit)
 ```
 
+By default, outputs land in `output/` next to `rev.yaml`. Override or
+disable via the `outputDir` field in rev.yaml (see below).
+
 The `--dual` flag produces:
-- `paper.docx` — clean, for submission
-- `paper_comments.docx` — includes comment threads as Word comments
+- `output/<title>.docx` — clean, for submission
+- `output/<title>_comments.docx` — includes comment threads as Word comments
+
+The `--show-changes` flag (DOCX only) produces a single audit document
+where every accepted/rejected revision and substitution is exported as a
+visible Word track change, attributed to the configured user. Useful when
+a co-author wants to see what changed since the last shared version.
 
 ### rev preview
 Build and open document in default app.
@@ -342,6 +351,39 @@ rev config                   # Show current config
 
 ## rev.yaml Settings
 
+### Output Directory
+
+By default, built artefacts land in `output/` next to `rev.yaml`. Both the
+clean output and `--dual` companion (`*_comments.docx` / `*_comments.pdf`)
+follow the configured location. Override or disable:
+
+```yaml
+outputDir: output       # default — outputs land in ./output/
+outputDir: dist         # custom subdirectory
+outputDir: null         # legacy layout — outputs alongside paper.md
+```
+
+Explicit caller-supplied output paths (e.g. internal temp files in the
+dual flow) bypass `outputDir`.
+
+### PDF Engine and Fonts
+
+The default PDF engine is `pdflatex`. Switch to xelatex/lualatex when the
+manuscript needs native UTF-8 rendering of Latin-Extended diacritics
+(Czech/Polish/Croatian/Spanish author names, species epithets):
+
+```yaml
+pdf:
+  engine: xelatex          # or lualatex, tectonic, etc.
+  mainfont: "TeX Gyre Termes"   # serif (xelatex/lualatex only — uses fontspec)
+  sansfont: "TeX Gyre Heros"    # sans (optional)
+  monofont: "TeX Gyre Cursor"   # monospace (optional)
+```
+
+`mainfont`/`sansfont`/`monofont` are forwarded as pandoc `-V` flags and
+require an engine that loads `fontspec` (xelatex or lualatex). They are
+ignored under `pdflatex`.
+
 ### Tables
 
 Configure table formatting for PDF output:

package/skill/SKILL.md

@@ -85,11 +85,20 @@ rev resolve methods.md -n 1  # Mark comment #1 as resolved
 ### 7. Rebuild with comment threads
 
 ```bash
-rev build docx --dual        # Produces clean + annotated versions
+rev build docx --dual            # Produces clean + annotated versions
+rev build docx --show-changes    # Single DOCX with visible track changes
 ```
 
-- `paper.docx` — clean, for submission
-- `paper_comments.docx` — includes comment threads as Word comments
+`--dual` produces:
+- `output/<title>.docx` — clean, for submission
+- `output/<title>_comments.docx` — comment threads as Word comments
+
+`--show-changes` produces a single audit DOCX where every accepted/rejected
+revision is rendered as a visible Word track change. Useful when a co-author
+wants to see what changed since the last shared version.
+
+Outputs land in `output/` by default; set `outputDir: null` in `rev.yaml`
+to keep them alongside `paper.md` (legacy layout).
 
 ### 8. Archive reviewer files
 
@@ -135,6 +144,7 @@ rev response                 # Generate point-by-point response letter
 | Build PDF | `rev build pdf` |
 | Build clean + annotated Word | `rev build docx --dual` |
 | Build clean + annotated PDF | `rev build pdf --dual` |
+| Build with visible track changes | `rev build docx --show-changes` |
 | Show contributors | `rev contributors` |
 | Lookup ORCID | `rev orcid 0000-0002-1825-0097` |
 | Archive reviewer files | `rev archive` |
@@ -193,9 +203,15 @@ my-document/
 ├── discussion.md
 ├── references.bib     # Bibliography
 ├── figures/           # Images
-└── paper.docx         # Built output
+├── paper.md           # Combined sections (auto-generated)
+└── output/            # Built artefacts
+    ├── my-document.docx
+    └── my-document.pdf
 ```
 
+Set `outputDir: null` in `rev.yaml` to write outputs alongside `paper.md`
+instead.
+
 ## PDF Comment Workflow
 
 For reviewers who annotate PDFs instead of Word documents: