nature-paper2word

1# Markdown → compliant Word
2 
3This file is the router. The engine is deterministic: the same manuscript and the same format
4requirements always produce a byte-identical `.docx`. Do not substitute a hand-written
5python-docx script; run the installed pipeline.
6 
7**Before the first export in a session, confirm the engine is available**: `md-to-word --version`
8must print a version. The export engine is installed separately; if the command is missing, install it
9with `pip install md-to-word-docx`, then run the check again.
10 
11**The full vocabulary lives in the manual inside the package**, not here. `md-to-word --contract`
12prints its absolute path (Chinese or English, following the manuscript). Everything below is order
13of work; every spelling is looked up in the manual.
14 
15## 1. Decide the scenario first
16 
17| Scenario | What the user says | What to do |
18|---|---|---|
19| Journal or school compliance | "format it using these journal instructions" | Read [format-requirements](references/format-requirements.md); extract requirements from PDF, Word, images or pasted text, then build the engine requirements file. |
20| Reference-paper reformatting | "format manuscript A like paper B" | Read [reference-layout](references/reference-layout.md); inspect actual reference paragraphs, map their roles, then extract and verify the requirements. |
21| Existing requirements | "use our lab's spec file" | Pass it with `-r`. |
22…