pymupdf4llm.to_markdown() returns empty output in 0.0.25 (worked in 0.0.17)

[azhurb]

Summary

I'm encountering an issue where pymupdf4llm.to_markdown() returns an empty string for a specific PDF in version 0.0.25 (and also 0.0.24). However, the same file works correctly in version 0.0.17.

Environment

• pymupdf4llm: 0.0.25
• Python: 3.11.2

PDF Characteristics

Unfortunately, I cannot share the exact file here due to confidentiality (I can provide it privately). However, here are some relevant details:

• The PDF has images in the header.
• The body contains text (visibly selectable in a PDF viewer).
• The output of pdffonts is:

name                                 type              encoding         emb sub uni object ID
------------------------------------ ----------------- ---------------- --- --- --- ---------
Courier                              Type 1            WinAnsi          no  no  no      22  0
Courier-Bold                         Type 1            WinAnsi          no  no  no      23  0

[JorjMcKie]

Thanks for the file.

1. All images on all pages cover more than 90% of the page area. So, sou can safely use ignore_images=True, without loosing information.
2. All text is written with a mono-spaced font. So, you must decide whether or not to use ignore_code=True. If False, all pages will be treated like full page code blocks. Even if True, the output will be treated like code particle and may not look very nice.

Independent from the above, I will handle images of this size as full page images to simplify processing.

[JorjMcKie]

One more comment:
It may seem counter-intuitive, but none of the pages contains any table! Textual indicators like "--+--" or underscores are not taken into account when looking for grid lines. As per position, text is distributed too sparsely across the page for deriving text-based table structures.

[azhurb]

Setting ignore_images=True gives me results very similar to what I was getting with version 0.0.17. Really appreciate the quick response and helpful tip - thanks!

[JorjMcKie]

Fixed in version 0.0.26.