pymupdf4llm with pymupdfpro

[mark3st]

I got pymupdf pro key and tried to pymupdf4llm.mark_down(example.hwpx)

Then I got runtime error.

RuntimeError: code=7: cannot find entry Contents/Contents/header.xml

But this did not happen when I executed mark_down function with example.hwp file.

Have this happened to other people as well?
If it’s not, please share your solution.

Thank you for your support for hwp, hwpx files.

[JorjMcKie]

Please provide a problem file.

[mark3st]

hwpx file is not allowed in github. I shared this situation and .hwpx file in your discord channel.

[JorjMcKie]

The simple solution for such cases: pack your upload in a ZIP file!
But I will have a look at Discord now.

[mark3st]

test.hwpx.zip

This is the .hwpx file for the test. Since I didn't notice any fixes after my issue-raise via discord channel, can you share when this problem is supposed to be resolved?

[JorjMcKie]

test.hwpx.zip

This is the .hwpx file for the test. Since I didn't notice any fixes after my issue-raise via discord channel, can you share when this problem is supposed to be resolved?

Nothing has happened yet because you did not share a reproducing file!
Efforts to solve the problem can start now. There is no way to predict how much time this will take.

[JorjMcKie]

With the provided test file, the error can be reproduced like this:

import pymupdf.pro

pymupdf.pro.unlock(key)
doc = pymupdf.open("test.hwpx")
print(doc.page_count)

The traceback:

Traceback (most recent call last):
  File "test.py", line 5, in <module>
    print(doc.page_count)
          ^^^^^^^^^^^^^^
  File "...\site-packages\pymupdf\__init__.py", line 5109, in page_count
    return self.page_count2(self)
           ~~~~~~~~~~~~~~~~^^^^^^
  File "...\site-packages\pymupdf\extra.py", line 135, in page_count_fz
    return _extra.page_count_fz(document)
           ~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^
RuntimeError: code=7: cannot find entry Contents/Contents/header.xml

[JorjMcKie]

SmartOffice bug tracker link: https://bugs.ghostscript.com/show_bug.cgi?id=708522

[JorjMcKie]

The MuPDF team has identified and fixed the problem.
The fix will be part of the next PyMuPDF version.

[julian-smith-artifex-com]

This was fixed in PyMuPDF-1.26.1 and PyMuPDFPro-1.26.1.