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

Svante Schubert commented on ODFTOOLKIT-472:
--------------------------------------------

Hello Guzman,

do you delete/edit the metadata with the ODF Toolkit and if this is the case, 
could you please provide a short test function that does it, so someone could 
debug it.

You might reuse an existing metadata test to prove your point.

PS: If you are editing the file with note++ it is rather an issue for note++ 
and you might want to close this issue ;)

Thanks in advance,

Svante

> mimetype error
> --------------
>
>                 Key: ODFTOOLKIT-472
>                 URL: https://issues.apache.org/jira/browse/ODFTOOLKIT-472
>             Project: ODF Toolkit
>          Issue Type: Bug
>          Components: odfdom
>    Affects Versions: 0.6.2-incubating
>         Environment: Windows 10 Home 64 Bits
> ODF Toolkit 0.6.2
>            Reporter: Guzman Rejon
>            Priority: Major
>         Attachments: correctmimetypeapplication.odt, 
> corruptmimetypeapplication.odt
>
>
> Hello,
> For odt files, after delete or update its metadata the mimetypeapplication is 
> corrupted so even is possible open or edit the document in Open Office, other 
> applications like TIKA not recognize them due to a corrupt 
> mimetypeapplication.
> Example:
>  # Create a odt file and open it with note++ or some editor, the 
> mimetypeapplication looks like (please see correctmimetypeapplication.odt):
>           *mimetypeapplication/vnd.oasis.opendocument.text*
>       2. Delete metadata for odt file
>       3. Edit with note++ and mimetypeapplication is corrupted (please see    
>   
>           corruptmimetypeapplication.odt):
>           *mimetypeK,(ÈÉLN,ÉÌÏÓ/ËKÑËO,Î,ÖË/HÍKÉO.ÍMÍ+Ñ+I­*
> Could you please send us a patch or workaround to solve this issue?
> Thanks a lot in Advance,
> Best Regards,
> Guzman



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to