Reducto in Converting a complex PDF into clean Markdown with a hosted API

Reducto did not preserve the code block as fenced or preformatted Markdown. The returned file had no fences or indented code lines, while the source block’s line breaks remained and the output also altered code tokens, including `window = reload_window(reset_at, margin_minutes=45)` becoming `window reload_window (reset_at, margin_minutes=45)`.

Reducto failed a document with mathematical equations: the returned Markdown contained no math markup and no fallback, and the equations were flattened into prose with missing symbols and substituted characters. This is the case: the source page shows set mathematics, while the output preserves only garbled lines instead of LaTeX, MathML, or an explicit fallback.

Reducto flattened the heading structure in the Markdown output. The file contains one "#", 26 "##" headings, and no deeper levels; the document title is plain paragraph text. The two visible parent/child pairs were emitted as peers, so the nesting expected for styled headings and subheadings was not preserved.

Reducto accurately recovered the visible text from a cleanly scanned document. The scan’s text matched the output field by field, with the handwritten signature left as a <signature> placeholder and only two middle-dot separators dropped from the letterhead and footer lines.

The mixed PDF’s scanned page was processed rather than skipped. Reducto’s Markdown includes the image-only page 2 with its headers, table, certificate section, and recipient details, matching the digital pages’ presentation in the checked evidence.

Reducto kept the simple table as a table in Markdown, with the same headers, rows, columns, and values. In the checked run, the table stayed in the right place on page 1, and pages 2 and 3 had no table. The table used HTML table markup rather than pipe syntax.