[
https://issues.apache.org/jira/browse/TIKA-3968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17684953#comment-17684953
]
Tim Allison edited comment on TIKA-3968 at 2/6/23 9:50 PM:
-----------------------------------------------------------
Pulling the file name from the comment records ought to be easier than parsing
the text. Thank you!
What did you use to dump the EMF info?
was (Author: [email protected]):
Pulling the file name from the metadata ought to be easier than parsing the
text. Thank you!
> Reconstruct embedded file names from recent docx files
> ------------------------------------------------------
>
> Key: TIKA-3968
> URL: https://issues.apache.org/jira/browse/TIKA-3968
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Major
> Attachments: Microsoft_Word_Document.docx,
> image-2023-02-06-15-46-05-678.png, image-2023-02-06-15-58-20-443.png,
> image1.emf, image2.emf, image3.emf, oleObject1.bin, oleObject2.bin, testWORD
> has attachment.docx
>
>
> I'm starting to see among several users communicating with me privately that
> Microsoft has changed their basic behavior for files attached to at least
> docx files (possibly pptx and xlsx?). Rather than storing the original file
> name, the file associates an EMF file with an attachment. The filename that
> a human sees in the application is spelled/painted out in the EMF file, but
> does NOT exist in any of the XML.
> I'm attaching an example file.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
