# Fixed-version source diagnosis

Accessed 2026-11-09. These notes separate source facts from the constructed fixture observations. No Word client was run.

## Pandoc 3.11

- https://raw.githubusercontent.com/jgm/pandoc/3.11/src/Text/Pandoc/Readers/Docx/Parse.hs : `pHeading`, lines 782–783, reads `headingLev` from paragraph styles. `elemToBodyPart`, lines 875–898, chooses Heading versus Paragraph from that result. It does not promote a normal paragraph to a heading merely because a run has a large font.
- https://raw.githubusercontent.com/jgm/pandoc/3.11/src/Text/Pandoc/Readers/Docx.hs : `isBlockQuote`, lines 226–230, recognizes selected quote styles. `paragraphStyleToTransform`, lines 624–641, also uses a positive relative indentation heuristic for eligible non-list paragraphs. `relativeIndent`, lines 645–651, compares direct and inherited indentation. A cosmetic indent can consequently become semantic quotation.
- Inference for editors: font styling and semantic structure are different signals. A named quote style is not the only possible input to this reader's quote handling. This is a source-based diagnostic, not a guarantee for arbitrary Word exporters.

## MarkItDown 0.1.8

- Public pinned source: https://raw.githubusercontent.com/microsoft/markitdown/v0.1.8/packages/markitdown/src/markitdown/converters/_docx_converter.py . Local installed source was read in full and has the same conversion stages.
- `DocxConverter.convert` preprocesses DOCX, combines caller and embedded style maps with its underline rule, calls `mammoth.convert_to_html`, then invokes `HtmlConverter.convert_string`. Its result reflects both DOCX-to-HTML style mapping and subsequent HTML-to-Markdown escaping.
- No custom map was supplied in this guide. Default handling of Quote versus a literal greater-than character differed in our fixtures. This does not establish what a user-supplied map could achieve.

## Upstream failure report and bounded reproduction

- https://github.com/microsoft/markitdown/issues/2157 : report opened 2026-06-24, specifying 0.1.6 on Windows, described leading hash characters remaining active and an empty header in a converted Word table.
- This guide uses newly constructed fixtures on macOS with 0.1.8, not the reporter's original document. `results.json` records a Header in the literal export from MarkItDown and no Header from Pandoc. `lab/markitdown-word/styled.md` contains an empty header above the row that held labels. These reproduce the stated failure shapes under our stated conditions, not the reporter's whole environment or every part of the issue.
- The literal pipe lines did not become a table in either exported result; blank paragraphs separate the rows. Do not claim this experiment reproduced the issue's pipe-inside-table subcase.
