docx-template-translatorlisted

# DOCX Template Translator ## Core Idea Treat the input file as the content source and the Word template as the formatting source. Do not expect pandoc or PDF import to infer template semantics. Build a project-specific Python postprocessor after inspecting the template and the converted body document. Do not treat the bundled starter pipeline or a preset JSON file as a finished converter for institutional templates. For thesis/dissertation templates, you must create or patch a project-specific pipeline for the concrete template and source project before claiming success. ## Workflow 1. Identify inputs: - Source: `.tex` project, `.pdf`, `.md`, or an existing rough `.docx`. - Template: required `.docx`. - Output location and document metadata. 2. Inspect the template with the real CLI form: - `python scripts/inspect_docx_template.py template.docx --out template_report.json` 3. Create a rough body `.docx`: - LaTeX/Markdown: use pandoc when available. - PDF: try Word COM import or `pdf2docx`; prefer PDF only when the original source is unavailable. - Existing DOCX: use it as the rough body source. 4. Write or patch a project-specific Python pipeline: - Start from `scripts/adaptive_docx_pipeline.py`. - Copy it into the run/output directory or project workspace before patching; do not edit the bundled script in place for a one-off conversion. - Decide, from the template inspection, which template paragraphs/tables/sections are reusable and which