[
https://issues.apache.org/jira/browse/TIKA-3968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17684960#comment-17684960
]
Ross Johnson commented on TIKA-3968:
------------------------------------
FYI I did a test with a very long embedded file name, and it does seem like the
comment is the best way to go. The icon will wrap the text onto a max of two
lines (corresponding to two EMR_EXTTEXTOUTW text drawing records), and cut off
the rest, but the comment still looks to contain the full name.
[^image1.emf] is the example EMF icon with a long, wrapped file name.
The EMF dump info is from a tool I wrote, but I have not yet made it available
anywhere.
> 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-1.emf, image1-2.emf, 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)
