You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue Description
When testing v2.16.2 of pandoc on Windows I observed some .docx files do not have all of their images exported when using the --extract-media command line argument (when converting to the .md format). Instead a subset of images are exported. For example, in a simple test .docx file (attached to this issue) only 1 image is exported, but there are several in the document.
Details to recreate
This can be recreated by running the following command using v2.16.2 of pandoc on Windows Server 2012 R2:
I'm not so familiar with the underlying .docx markup, but from the WYSIWYG frontend of MS Word this seems like a fairly normal thing to be able to do, so could potentially be a common scenario for .docx files?
How feasible do you think it might be to extend the parser to cope with multiple pic:pic elements?
...instead of ParPart.
Also remove NullParPart constructor, as it is no longer
needed.
This will allow us to handle elements that contain multiple
ParParts, e.g. w:drawing elements with multiple pic:pic.
See #7786.
Issue Description
When testing v2.16.2 of pandoc on Windows I observed some .docx files do not have all of their images exported when using the
--extract-media
command line argument (when converting to the.md
format). Instead a subset of images are exported. For example, in a simple test .docx file (attached to this issue) only 1 image is exported, but there are several in the document.Details to recreate
This can be recreated by running the following command using v2.16.2 of pandoc on Windows Server 2012 R2:
The sample
.docx
file to recreate this is available here: test.docx.zipFurther details
Original .docx (saved from MS Word v16.56 on OS X)
Generated .md file (from Pandoc)
Unzipped .docx file directory structure (with 10x media files visible)
The text was updated successfully, but these errors were encountered: