[ 
https://issues.apache.org/jira/browse/TIKA-3827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17575184#comment-17575184
 ] 

Tim Allison edited comment on TIKA-3827 at 8/4/22 10:06 AM:
------------------------------------------------------------

Ah, ok, thank you.  Good to have confirmation from a Windows application. I 
don't know if this is a feature of how RTF embeds bitmaps (without headers) or 
if the file is corrupted.  If you open the file in a hex editor, you can see 
the bytes are extracted properly and that the files do not start with "BM" (see 
eg: https://gist.github.com/leommoore/f9e57ba2aa4bf197ebc5).  This is the 
reason that Tika's mime detection on the bytes of these images is failing.  
There's no header.


was (Author: talli...@mitre.org):
Right.  That's my point above. I don't know if this is a feature of how RTF 
embeds bitmaps (without headers) or if the file is corrupted.  If you open the 
file in a hex editor, you can see the bytes are extracted properly and that the 
files do not start with "BM" (see eg: 
https://gist.github.com/leommoore/f9e57ba2aa4bf197ebc5).  This is the reason 
that Tika's mime detection on the bytes of these images is failing.  There's no 
header.

> Word Document extracted mpga file extension instead of bitmap 
> --------------------------------------------------------------
>
>                 Key: TIKA-3827
>                 URL: https://issues.apache.org/jira/browse/TIKA-3827
>             Project: Tika
>          Issue Type: Bug
>          Components: parser
>            Reporter: Tika User
>            Priority: Major
>         Attachments: Screenshot from 2022-08-04 06-05-09.png, example.DOC, 
> file_1.bmp, file_2.bmp, image-2022-08-04-10-52-44-800.png, 
> image-2022-08-04-10-53-48-894.png
>
>
> When tried to parser the .doc document it is extracted two mpga files which 
> can't be open to play. We are suspecting they should be bitmap image files. 
> The Tika version we are using is 2.4.1.
> [^example.DOC]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to