mdmint 0.2.0rc1__tar.gz

mdmint-0.2.0rc1/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or Derivative
+          Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Meaningful Data
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

mdmint-0.2.0rc1/NOTICE

@@ -0,0 +1,5 @@
+mdmint
+Copyright 2026 Meaningful Data
+
+This product includes software developed at Meaningful Data
+(https://meaningfuldata.eu).

mdmint-0.2.0rc1/PKG-INFO

@@ -0,0 +1,196 @@
+Metadata-Version: 2.4
+Name: mdmint
+Version: 0.2.0rc1
+Summary: Export Markdown files to DOCX and/or PDF. Pure-Python, cross-platform, minimal dependencies.
+Author-email: Antonio Olleros <antonio.olleros@meaningfuldata.eu>
+License: Apache-2.0
+Project-URL: Homepage, https://github.com/Meaningful-Data/mdmint
+Keywords: markdown,docx,pdf,converter,export,mermaid,mkdocs,template
+Classifier: Programming Language :: Python :: 3
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Operating System :: OS Independent
+Classifier: Topic :: Text Processing :: Markup :: Markdown
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: markdown-it-py>=3.0
+Requires-Dist: mdit-py-plugins>=0.4
+Requires-Dist: htmldocx>=0.0.6
+Requires-Dist: python-docx>=1.1
+Requires-Dist: xhtml2pdf>=0.2.11
+Requires-Dist: svglib<1.6
+Requires-Dist: PyYAML>=5.1
+Provides-Extra: weasyprint
+Requires-Dist: weasyprint>=60; extra == "weasyprint"
+Provides-Extra: math
+Requires-Dist: matplotlib>=3.5; extra == "math"
+Provides-Extra: all
+Requires-Dist: weasyprint>=60; extra == "all"
+Requires-Dist: matplotlib>=3.5; extra == "all"
+Dynamic: license-file
+
+# mdmint
+
+Export Markdown files to **DOCX** and/or **PDF** — pure-Python, cross-platform,
+minimal dependencies.
+
+A single Markdown → HTML pass feeds both writers. The two features that can't be
+rendered statically in pure Python (mermaid diagrams and LaTeX math) use an
+**optional** renderer if one is available and fall back gracefully otherwise — so
+the base install stays small and works everywhere.
+
+## Install
+
+```bash
+pip install mdmint
+```
+
+The core install is pure-Python (no native libraries):
+`markdown-it-py`, `mdit-py-plugins`, `htmldocx`/`python-docx`, `xhtml2pdf`.
+
+Optional extras:
+
+```bash
+pip install "mdmint[math]"        # render LaTeX math (adds matplotlib)
+pip install "mdmint[weasyprint]"  # higher-fidelity PDF (needs native Pango/Cairo)
+pip install "mdmint[all]"         # both of the above
+```
+
+For **mermaid diagrams**, install the mermaid CLI separately (optional):
+`npm install -g @mermaid-js/mermaid-cli` (provides `mmdc`).
+
+## Usage
+
+```bash
+mdmint notes.md                          # -> notes.pdf
+mdmint notes.md -f docx,pdf -o out/      # both formats into ./out/
+mdmint a.md b.md -f docx                 # -> a.docx and b.docx (one per input)
+mdmint a.md b.md --merge -f pdf -o book.pdf   # one merged PDF
+mdmint report.md --toc -f pdf            # insert a table of contents
+mdmint report.md -f pdf --pdf-backend weasyprint
+```
+
+| Option | Meaning |
+| ------ | ------- |
+| `-f, --format` | `pdf`, `docx`, or both (comma-separated). Default `pdf`. |
+| `-o, --output` | Output directory, or a file path. Default: alongside each input. |
+| `--merge` | With multiple inputs, produce one merged file per format. |
+| `--toc` | Insert a table of contents (or honour a `[TOC]` marker). |
+| `--pdf-backend` | `xhtml2pdf` (default) or `weasyprint`. |
+| `-v, --verbose` | Verbose logging. |
+
+| `--mkdocs FILE` | Build one document from an mkdocs.yml `nav` (instead of INPUTs). |
+| `--section-style` | With `--mkdocs`: `part` (default) or `heading` — see below. |
+| `--template FILE` | Word template (`.docx`/`.dotx`) for DOCX output. |
+| `--meta KEY=VALUE` | Value for a template `{{KEY}}` placeholder (repeatable). |
+| `--style ROLE=STYLE` | Use a specific template style for a role (repeatable). |
+
+Also runnable as `python -m mdmint ...`.
+
+### From an mkdocs site
+
+```bash
+mdmint --mkdocs mkdocs.yml -f docx,pdf -o out/     # -> out/<site_name>.docx/.pdf
+```
+
+The `nav` decides which pages go in and in what order (without a `nav`, the
+`docs_dir` tree is used, like mkdocs does). Sections become headings:
+
+- `--section-style part` (default): a **top-level section** is a *part* divider
+  that doesn't use up a heading level, so its pages keep their `#` as chapters;
+  nested sections become `#`, `##`… and demote their pages to match.
+- `--section-style heading`: every section is a heading one level above its pages.
+
+Pages under a section titled *Annex(es)*, *Appendix* or *Appendices* become
+appendix chapters. Links between pages (`../other/page.md#anchor`) become
+in-document links; links to pages left out of the nav are kept as plain text.
+Headings accept mkdocs `attr_list` syntax (`# Title {#id .part}`).
+
+Settings can live in the mkdocs.yml itself (command-line options win):
+
+```yaml
+extra:
+  mdmint:
+    template: templates/brand.docx     # relative to mkdocs.yml
+    section_style: part
+    status: Final                      # any other key fills {{STATUS}} etc.
+    confidentiality: Internal
+    styles: {code: "My Code Style"}    # optional role overrides
+```
+
+### Branded DOCX with a Word template
+
+```bash
+mdmint report.md -f docx --template brand.docx --meta status=Draft
+```
+
+With `--template`, DOCX output is written *into a copy of the template*: its
+cover, contents page, headers/footers, page setup and styles are kept, and the
+content is appended at the end (or where a paragraph reading `{{CONTENT}}` sits).
+Text like `{{TITLE}}`, `{{AUTHOR}}`, `{{DATE}}` anywhere in the body, headers or
+footers is filled from, in increasing priority: mkdocs.yml (`site_name` → title,
+`site_description` → subtitle, `site_author` → author, `extra.mdmint`), the Markdown
+front matter, and `--meta`. `date` defaults to the current month; placeholders
+left without a value are blanked with a warning.
+
+Each element uses the template's styles, picking the first that exists:
+
+| Role (`--style` key) | Styles tried |
+| --- | --- |
+| headings | `Heading 1`…`Heading N` (deeper levels reuse the last) |
+| `part` / `appendix` | `Part Title` / `Appendix Heading` (else `Heading 1`) |
+| `code` / `inline_code` | `Code Block`, `Source Code`, `HTML Preformatted` / `Inline Code`, `Verbatim Char`, `HTML Code` |
+| `quote` | `Callout`, `Quote` (blockquotes) |
+| `note` / `warning` | `Callout Note` / `Callout Warning` (admonitions, `> [!NOTE]`) |
+| `table` | the template's own (non-stock) table style, else `Table Grid` |
+| `table_heading` / `table_text` | `Table Heading` / `Table Text` |
+| `figure` / `caption` | `Figure` / `Caption` ("Figure N." from the image alt text; `Table: …` before a table gives "Table N.") |
+| lists | `List Bullet`, `List Number` (real multi-level numbering, restarted per list) |
+| footnotes | `Footnote Text`/`Footnote Reference` (created if missing) — real Word footnotes |
+
+How to build a template that styles well — required styles, numbering, placeholders, and a
+specimen file to test it — is in [docs/TEMPLATES.md](docs/TEMPLATES.md).
+
+Headings are bookmarked so in-document links work, and the template's TOC field
+(if any) picks the headings up when Word updates fields on open. Without
+`--template`, DOCX output is unchanged (htmldocx).
+
+### Library API
+
+```python
+from mdmint import convert
+
+convert(["report.md"], formats=["pdf", "docx"], output="out/")
+convert(["a.md", "b.md"], formats=["pdf"], output="book.pdf", merge=True)
+```
+
+## Supported Markdown
+
+CommonMark plus: GFM tables, task lists, strikethrough, footnotes, auto table of
+contents, fenced code, [admonitions](https://squidfunk.github.io/mkdocs-material/reference/admonitions/)
+(`!!! note` / `??? warning` callouts), embedded images (relative paths resolved
+against the source file; remote URLs downloaded), LaTeX math, and mermaid diagrams.
+
+## Notes & limitations
+
+- **PDF backend.** `xhtml2pdf` (default) is pure-Python and runs anywhere, with a
+  pragmatic subset of CSS. `weasyprint` produces nicer output but needs native
+  Pango/Cairo libraries, so it is an opt-in extra.
+- **Math** uses matplotlib's *mathtext* engine (a large LaTeX-math subset, no system
+  LaTeX required) rendered to images. Full LaTeX environments (e.g. `align`) are not
+  supported. Without matplotlib, math is shown as literal source with a warning.
+- **Mermaid** requires the `mmdc` CLI. Without it, diagrams are shown as styled code
+  blocks with a warning. A snap-installed `mmdc` is supported (mdmint places its
+  scratch files where snap confinement can read them).
+- **Admonitions** render as a colour-coded callout box (tinted background + accent
+  bar + coloured title) in both PDF and DOCX. Type icons are intentionally omitted:
+  the pure-Python PDF backend can't embed an emoji font, so colour and the title
+  carry the type instead. The collapsible `???`/`???+` blocks render fully expanded
+  (static documents have nothing to collapse into).
+
+## License
+
+Licensed under the [Apache License, Version 2.0](LICENSE).
+
+Copyright 2026 Meaningful Data.

mdmint-0.2.0rc1/README.md

@@ -0,0 +1,164 @@
+# mdmint
+
+Export Markdown files to **DOCX** and/or **PDF** — pure-Python, cross-platform,
+minimal dependencies.
+
+A single Markdown → HTML pass feeds both writers. The two features that can't be
+rendered statically in pure Python (mermaid diagrams and LaTeX math) use an
+**optional** renderer if one is available and fall back gracefully otherwise — so
+the base install stays small and works everywhere.
+
+## Install
+
+```bash
+pip install mdmint
+```
+
+The core install is pure-Python (no native libraries):
+`markdown-it-py`, `mdit-py-plugins`, `htmldocx`/`python-docx`, `xhtml2pdf`.
+
+Optional extras:
+
+```bash
+pip install "mdmint[math]"        # render LaTeX math (adds matplotlib)
+pip install "mdmint[weasyprint]"  # higher-fidelity PDF (needs native Pango/Cairo)
+pip install "mdmint[all]"         # both of the above
+```
+
+For **mermaid diagrams**, install the mermaid CLI separately (optional):
+`npm install -g @mermaid-js/mermaid-cli` (provides `mmdc`).
+
+## Usage
+
+```bash
+mdmint notes.md                          # -> notes.pdf
+mdmint notes.md -f docx,pdf -o out/      # both formats into ./out/
+mdmint a.md b.md -f docx                 # -> a.docx and b.docx (one per input)
+mdmint a.md b.md --merge -f pdf -o book.pdf   # one merged PDF
+mdmint report.md --toc -f pdf            # insert a table of contents
+mdmint report.md -f pdf --pdf-backend weasyprint
+```
+
+| Option | Meaning |
+| ------ | ------- |
+| `-f, --format` | `pdf`, `docx`, or both (comma-separated). Default `pdf`. |
+| `-o, --output` | Output directory, or a file path. Default: alongside each input. |
+| `--merge` | With multiple inputs, produce one merged file per format. |
+| `--toc` | Insert a table of contents (or honour a `[TOC]` marker). |
+| `--pdf-backend` | `xhtml2pdf` (default) or `weasyprint`. |
+| `-v, --verbose` | Verbose logging. |
+
+| `--mkdocs FILE` | Build one document from an mkdocs.yml `nav` (instead of INPUTs). |
+| `--section-style` | With `--mkdocs`: `part` (default) or `heading` — see below. |
+| `--template FILE` | Word template (`.docx`/`.dotx`) for DOCX output. |
+| `--meta KEY=VALUE` | Value for a template `{{KEY}}` placeholder (repeatable). |
+| `--style ROLE=STYLE` | Use a specific template style for a role (repeatable). |
+
+Also runnable as `python -m mdmint ...`.
+
+### From an mkdocs site
+
+```bash
+mdmint --mkdocs mkdocs.yml -f docx,pdf -o out/     # -> out/<site_name>.docx/.pdf
+```
+
+The `nav` decides which pages go in and in what order (without a `nav`, the
+`docs_dir` tree is used, like mkdocs does). Sections become headings:
+
+- `--section-style part` (default): a **top-level section** is a *part* divider
+  that doesn't use up a heading level, so its pages keep their `#` as chapters;
+  nested sections become `#`, `##`… and demote their pages to match.
+- `--section-style heading`: every section is a heading one level above its pages.
+
+Pages under a section titled *Annex(es)*, *Appendix* or *Appendices* become
+appendix chapters. Links between pages (`../other/page.md#anchor`) become
+in-document links; links to pages left out of the nav are kept as plain text.
+Headings accept mkdocs `attr_list` syntax (`# Title {#id .part}`).
+
+Settings can live in the mkdocs.yml itself (command-line options win):
+
+```yaml
+extra:
+  mdmint:
+    template: templates/brand.docx     # relative to mkdocs.yml
+    section_style: part
+    status: Final                      # any other key fills {{STATUS}} etc.
+    confidentiality: Internal
+    styles: {code: "My Code Style"}    # optional role overrides
+```
+
+### Branded DOCX with a Word template
+
+```bash
+mdmint report.md -f docx --template brand.docx --meta status=Draft
+```
+
+With `--template`, DOCX output is written *into a copy of the template*: its
+cover, contents page, headers/footers, page setup and styles are kept, and the
+content is appended at the end (or where a paragraph reading `{{CONTENT}}` sits).
+Text like `{{TITLE}}`, `{{AUTHOR}}`, `{{DATE}}` anywhere in the body, headers or
+footers is filled from, in increasing priority: mkdocs.yml (`site_name` → title,
+`site_description` → subtitle, `site_author` → author, `extra.mdmint`), the Markdown
+front matter, and `--meta`. `date` defaults to the current month; placeholders
+left without a value are blanked with a warning.
+
+Each element uses the template's styles, picking the first that exists:
+
+| Role (`--style` key) | Styles tried |
+| --- | --- |
+| headings | `Heading 1`…`Heading N` (deeper levels reuse the last) |
+| `part` / `appendix` | `Part Title` / `Appendix Heading` (else `Heading 1`) |
+| `code` / `inline_code` | `Code Block`, `Source Code`, `HTML Preformatted` / `Inline Code`, `Verbatim Char`, `HTML Code` |
+| `quote` | `Callout`, `Quote` (blockquotes) |
+| `note` / `warning` | `Callout Note` / `Callout Warning` (admonitions, `> [!NOTE]`) |
+| `table` | the template's own (non-stock) table style, else `Table Grid` |
+| `table_heading` / `table_text` | `Table Heading` / `Table Text` |
+| `figure` / `caption` | `Figure` / `Caption` ("Figure N." from the image alt text; `Table: …` before a table gives "Table N.") |
+| lists | `List Bullet`, `List Number` (real multi-level numbering, restarted per list) |
+| footnotes | `Footnote Text`/`Footnote Reference` (created if missing) — real Word footnotes |
+
+How to build a template that styles well — required styles, numbering, placeholders, and a
+specimen file to test it — is in [docs/TEMPLATES.md](docs/TEMPLATES.md).
+
+Headings are bookmarked so in-document links work, and the template's TOC field
+(if any) picks the headings up when Word updates fields on open. Without
+`--template`, DOCX output is unchanged (htmldocx).
+
+### Library API
+
+```python
+from mdmint import convert
+
+convert(["report.md"], formats=["pdf", "docx"], output="out/")
+convert(["a.md", "b.md"], formats=["pdf"], output="book.pdf", merge=True)
+```
+
+## Supported Markdown
+
+CommonMark plus: GFM tables, task lists, strikethrough, footnotes, auto table of
+contents, fenced code, [admonitions](https://squidfunk.github.io/mkdocs-material/reference/admonitions/)
+(`!!! note` / `??? warning` callouts), embedded images (relative paths resolved
+against the source file; remote URLs downloaded), LaTeX math, and mermaid diagrams.
+
+## Notes & limitations
+
+- **PDF backend.** `xhtml2pdf` (default) is pure-Python and runs anywhere, with a
+  pragmatic subset of CSS. `weasyprint` produces nicer output but needs native
+  Pango/Cairo libraries, so it is an opt-in extra.
+- **Math** uses matplotlib's *mathtext* engine (a large LaTeX-math subset, no system
+  LaTeX required) rendered to images. Full LaTeX environments (e.g. `align`) are not
+  supported. Without matplotlib, math is shown as literal source with a warning.
+- **Mermaid** requires the `mmdc` CLI. Without it, diagrams are shown as styled code
+  blocks with a warning. A snap-installed `mmdc` is supported (mdmint places its
+  scratch files where snap confinement can read them).
+- **Admonitions** render as a colour-coded callout box (tinted background + accent
+  bar + coloured title) in both PDF and DOCX. Type icons are intentionally omitted:
+  the pure-Python PDF backend can't embed an emoji font, so colour and the title
+  carry the type instead. The collapsible `???`/`???+` blocks render fully expanded
+  (static documents have nothing to collapse into).
+
+## License
+
+Licensed under the [Apache License, Version 2.0](LICENSE).
+
+Copyright 2026 Meaningful Data.

mdmint-0.2.0rc1/mdmint/__init__.py

@@ -0,0 +1,18 @@
+"""mdmint — export Markdown files to DOCX and/or PDF.
+
+Pure-Python, cross-platform, minimal dependencies. The two features that cannot
+be rendered statically in pure Python — mermaid diagrams and LaTeX math — use an
+optional renderer if present and fall back gracefully (with a warning) otherwise.
+
+Public API
+----------
+    from mdmint import convert, MarkdownConverter
+
+    convert(["doc.md"], formats=["pdf", "docx"], output="out/")
+    convert_mkdocs("mkdocs.yml", formats=["docx"], template="brand.docx")
+"""
+
+from .core import MarkdownConverter, convert, convert_mkdocs
+
+__version__ = "0.2.0rc1"
+__all__ = ["MarkdownConverter", "convert", "convert_mkdocs", "__version__"]

mdmint-0.2.0rc1/mdmint/__main__.py

@@ -0,0 +1,6 @@
+"""Enable ``python -m mdmint``."""
+
+from .cli import main
+
+if __name__ == "__main__":
+    raise SystemExit(main())

mdmint-0.2.0rc1/mdmint/admonitions.py

@@ -0,0 +1,70 @@
+"""Shared colour table for Markdown admonitions (``!!!`` / ``???`` callouts).
+
+Both writers need to agree on what a "warning" looks like, but they style it
+through completely different mechanisms: :mod:`mdmint.render` emits inline CSS that
+the PDF backend honours, while :mod:`mdmint.backends` paints the DOCX cell with
+low-level OOXML after the fact. Keeping the palette here means the two paths can
+never drift, and adding a type is a one-line change.
+
+Type names follow python-markdown / mkdocs-Material conventions; unknown tags
+degrade to the neutral ``note`` styling rather than raising.
+"""
+
+from __future__ import annotations
+
+# Canonical type -> (accent colour, light background tint), both ``#rrggbb``.
+_CANONICAL: dict[str, tuple[str, str]] = {
+    "note": ("#448aff", "#eaf1ff"),
+    "abstract": ("#00b0ff", "#e5f6ff"),
+    "info": ("#00b8d4", "#e3f8fc"),
+    "tip": ("#00bfa5", "#e3f8f4"),
+    "success": ("#00c853", "#e6f9ec"),
+    "question": ("#64dd17", "#eef9e3"),
+    "warning": ("#ff9100", "#fff3e0"),
+    "failure": ("#ff5252", "#ffecec"),
+    "danger": ("#ff1744", "#ffe9ed"),
+    "bug": ("#f50057", "#ffe6ef"),
+    "example": ("#7c4dff", "#f0ebff"),
+    "quote": ("#9e9e9e", "#f5f5f5"),
+}
+
+# Extra spellings mkdocs/python-markdown accept, mapped to a canonical key.
+_ALIASES: dict[str, str] = {
+    "summary": "abstract",
+    "tldr": "abstract",
+    "hint": "tip",
+    "important": "tip",
+    "check": "success",
+    "done": "success",
+    "help": "question",
+    "faq": "question",
+    "caution": "warning",
+    "attention": "warning",
+    "fail": "failure",
+    "missing": "failure",
+    "error": "danger",
+    "cite": "quote",
+}
+
+DEFAULT = "note"
+
+
+def resolve(tag: str) -> str:
+    """Map any admonition tag (or alias) to a canonical key, defaulting to note."""
+    tag = (tag or "").strip().lower()
+    if tag in _CANONICAL:
+        return tag
+    return _ALIASES.get(tag, DEFAULT)
+
+
+def style_for(tag: str) -> tuple[str, str]:
+    """Return ``(accent, background)`` hex colours for an admonition tag."""
+    return _CANONICAL[resolve(tag)]
+
+
+# Accent colour (upper-case, no ``#``) -> canonical type. The DOCX post-pass uses
+# this to recognise an admonition table by its title colour, which is the only
+# marker that survives htmldocx's class-stripping conversion.
+ACCENTS: dict[str, str] = {
+    accent.lstrip("#").upper(): key for key, (accent, _bg) in _CANONICAL.items()
+}