microsoft / microsoft/markitdown

Poor Markdown conversion quality for academic paper

Open
#2,226 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
186k
Forks
13.7k
Avg merge
1d 4h
Merged PRs (30d)
49

Description

Description

I used MarkItDown to convert the following paper from PDF to Markdown:

However, the generated Markdown has very poor formatting and structure. For example, the reading order, headings, equations, tables, and multi-column content are not preserved correctly, making the output difficult to read and use.

Is this an expected limitation when converting academic papers with complex layouts, or could this indicate an issue with the conversion process?

Expected behavior

The converted Markdown should preserve the document structure and reading order as accurately as possible, including:

  • Section headings
  • Paragraph order
  • Mathematical equations
  • Tables and figures
  • Multi-column layouts
Actual behavior

The generated Markdown contains significant formatting and structural issues, resulting in content that is difficult to read.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the conversion using the linked AutoSOTA PDF and compare the result with AutoSOTA.md. Investigate the conversion path responsible for reading order, headings, equations, tables, figures, and multi-column content; done means the issue is either resolved with improved structure or documented as an established limitation.

Written by the indexing model from the issue text.

Assessment

Tech stack
markdown, python
Domain
content
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.