Commas or periods shouldn’t be placed

[remywu]

🔎 Search before asking | 提交之前请先搜索

• I have searched the MinerU Readme and found no similar bug report.
• I have searched the MinerU Issues and found no similar bug report.
• I have searched the MinerU Discussions and found no similar bug report.

🤖 Consult the online AI assistant for assistance | 在线 AI 助手咨询

• I have consulted the online AI assistant but was unable to obtain a solution to the issue.

Description of the bug | 错误描述

When converting a PDF file to a Markdown file, you shouldn’t put a comma or period right before the $ at the end of an inline math expression.

How to reproduce the bug | 如何复现

Error: $P(G\mid ¬U),$

Correct: $P(G\mid ¬U)$,

Operating System Mode | 操作系统类型

No response

Operating System Version| 操作系统版本

windows 11

Python version | Python 版本

No response

Software version | 软件版本 (mineru --version)

No response

Backend name | 解析后端

No response

Device mode | 设备模式

No response

[dosubot]

Hi @remywu! I'm Dosu and I'm helping the OpenDataLab team.

Thanks for reporting this. I looked into the rendering pipeline and can confirm the issue. The root cause is that the upstream OCR/extraction model is including the trailing punctuation (comma, period, etc.) as part of the INLINE_EQUATION span content itself, rather than placing it in a separate TEXT span. The _render_span() function simply wraps whatever is in span['content'] with $...$ delimiters without any punctuation filtering, so if the content already contains a trailing comma, it ends up inside the delimiters.

There is currently no post-processing logic anywhere in the pipeline to strip or relocate trailing punctuation from math expressions [1].

A fix could be applied at either layer:

• Extraction layer — strip trailing punctuation (,, ., ;, :, etc.) from INLINE_EQUATION span content during span extraction, and append it to the next TEXT span (or create one).
• Rendering layer — add a check in _render_span() to detect and move trailing punctuation outside the $...$ delimiters before output. This is a simpler workaround that doesn't fix the underlying span data but would produce correct Markdown.

I didn't find any existing issues or PRs specifically tracking this punctuation-placement problem.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.