Scenario definition · S32
A table that continues across a page break
A table continues across a page break and is still treated as one table.
What this scenario means
This scenario checks whether a conversion preserves table structure when a table spans two pages. The page break can look like a boundary, so a good result keeps the continuation linked to the same table and preserves the header and cell relationships.
What we evaluate
- Whether the table is recognised as one continuous table rather than split into separate tables.
- Whether the continuation keeps the table header context intact across the page break.
- Whether rows and columns remain aligned as a single structure across both pages.
◌Test-case detail. Exact wording, inputs, fixture state, expected output and detailed grading remain at the test-case level and may be withheld while the benchmark version is active. The scenario and its evaluation intent are public.
Capabilities this scenario exercises
A scenario may exercise one or more capabilities.
Table Extraction
Relational data — values whose meaning lives in row/column association; the one type whose partial failure yields confidently wrong downstream answers rather than gaps
Benchmarks that use this scenario
A scenario has global identity and may be reused across benchmarks.
Converting a complex PDF into clean Markdown with a hosted API
Which hosted API converts a complex, real-world PDF into faithful, usable Markdown?
Converting a complex PDF into clean Markdown with an open-source library
Also uses this scenario.