AI Demos Research — the structured-intelligence platform. Every verdict on these pages opens to the execution behind it.
Graded 28 October 2026

Does LiteParse keep mathematical equations as math markup or an honest fallback?

LiteParse turned the note's equations into scrambled text: its Markdown has no math markup and no placeholder, each display equation is split across lines in the wrong order, the ω of equation (4)'s ω/c factor is missing, and the top of equation (6) became a heading.

1 of 1 test case failed

Every test case in this scenario has a result.

Pass rate0%0 of 1 gradable
Coverage1 of 1test case with a result
0PassNo test case passed.
1FailMissed at least one thing it was expected to do; the reason and proof are with each test case below.
0Not gradableEvery result here could be graded.
0UntestedEvery test case in this scenario has a result.
The pass rate is a summary. The evidence is the test case below: what we sent, what we checked, what the tool returned, and the proof.

The test case

Each test case is judged on its own: Pass, Fail, Not gradable, or Untested. The scenario result above is based on this test case.

Equations — math markup or honest fallbackFailEvidence
What we sent

We called LiteParse 2.14.7 in Python on the complete three-page technical note with the default settings and Markdown output.

InputDocument (PDF)
Input PDF: the three-page technical note with six numbered equations
Open the PDF ↗
What the tool returned

Copied from Output file (Markdown), lines 17–23

Markdown
∂A ∂Q

+ = 0

(1)

∂t ∂x

Copied from Output file (Markdown), lines 49–51

Markdown
*c ( χ* ))1/2 8 n 2 *c η0* *μ =* , *χ =*

2(1 + χ 2 3π h 4/3 (4)

Copied from Output file (Markdown), lines 63–67

Markdown
*b n(h) = n∞ +*

(5)

*h 1/3*

Copied from Output file (Markdown), lines 77–81

Markdown
## |ηo - ηm|

*ε =*

*ηo* (6)

Returned Markdown: the equations as scattered text fragments with no math markup

Open the Markdown file ↗
Expected vs. Found
✗Expected: Equations come out as math markup, such as LaTeX or MathML, or an honest fallback, not garbled prose.Found: No math markup or placeholder; every display equation is split over several out-of-order lines, equation (4) drops the ω from its ω/c factor, and equation (6)'s numerator became a heading.
Supporting proof
Proof 1Screenshot
Run console and source page 1: the call, its timings and the first output lines
Open original ↗
Why this result

The test needed math markup or an honest fallback instead of garbled prose. The output has neither: equations are broken into out-of-order fragments, equation (4) drops the ω from its ω/c factor, and part of equation (6) is a heading.

Also observed in this test case

Prose sections intact. The prose sections came through well: section headings became Markdown headings and the paragraphs read correctly.

Inline symbols displaced. Inline symbols are displaced too: in the paragraph after equation (3), the symbols are lifted out of the sentence that defines them.

Tested by Vamshidhar Rao Thumula · evidence dated 28 October 2026

Configuration and setup

How this tool was set up for the run and what the test needed in place. Each row is a fact from the run's records; a fact the records do not hold is left out, not guessed.

Software that produced the output
LiteParse
Build or version
LiteParse 2.14.7
Surface
SDK / library
Set up before the run
A three-page technical note with six typeset numbered equations, sent whole to LiteParse's default Markdown conversion in one pass with no tuning.
Output format
Markdown
Tested
28 October 2026 · Vamshidhar Rao Thumula

How this scenario is graded

How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.

How results are decided

Each test case gets one result per tool: Pass, Fail or Not gradable. A test case we haven't run yet shows Untested. There are no partial results.

The rules
  • Pass: the tool did everything the test expected, and nothing it said contradicts the correct answer.
  • Fail: at least one expected behaviour clearly didn't happen; the test case's result says which one and quotes the tool.
  • Not gradable: our evidence couldn't settle the outcome (for example a record we needed is missing). It is never counted as a fail, and the test case's result says what's missing.

Where this sits in the benchmark

This page is one cell of a larger study: one tool, one scenario. Only this benchmark's frame appears here.

History of this result

What has happened to this result since it was first published. Runs and grades are never overwritten: a retest or a re-grade publishes a new result and keeps the earlier one readable.

from the publication record
16 November 2026First publishedConverting a complex PDF into clean Markdown with an open-source library v1

Act on this result

Nothing filed here edits the run or the grade. A challenge opens a review, and a review can produce a new run or a re-grade — which becomes the current result and leaves this one in the history.

This matches what I see

You run the same kind of test against your own setup and get the same behaviour.

Agree →
This does not match

Yours behaves differently. Tell us what you got, with a screenshot if you have one.

Disagree →
Point out an issue

Something here is wrong — a reference value, a transcription, a grade.

Report an issue →
Request a retest

On a newer build, a larger dataset, or your own setup.

Request a retest →
We have fixed this

Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.

Vendor notice →
Filed against this evidenceNothing yet. Challenges, counter-evidence and fix notices appear here with their outcome, and stay on the page after they are resolved.
Cite this result
aidemos.com/benchmarks/pdf-to-markdown-open-source/results/liteparse/a-document-containing-mathematical-equations · 0 pass · 1 fail · coverage 1/1 · graded 2026-10-28

The same record is available as structured data through the AI Demos MCP server, with the counts, the coverage and every per-test-case reason carried as fields.

Verify the proof files

These files support this result. Open a file to inspect the original evidence.

Input · Document (PDF) ↗application/pdf · 236 KB
Output file (Markdown) ↗text/markdown; charset=utf-8 · 5 KB
Proof 1 · Screenshot ↗image/png · 275 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Input · Document (PDF)f3d69b6d9d2191c5806a426fd4ea5e209dcd7cf693ad6abe67a5d18a014b9fd6
Output file (Markdown)cfc54a80c35995edd7383cd63edb7ea4c56954acebb47185bcf68c2bea155846
Proof 1 · Screenshot66b41c0a13cdb28a244167c36bcc7dfd52a142fcc8dbf7c892466ca4a84e2a80