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
{{ message }}
This repository has been archived by the owner on Mar 27, 2022. It is now read-only.
I've been using the latest published image of this project and am seeing the encoding issue reported at harvard-lts/fits#186.
Example snippets:
Output from FITSServlet container service:
<creatingApplicationNametoolname="Jhove"toolversion="1.20.1"status="CONFLICT">Microsoft������ Word 2010/Microsoft������ Word 2010</creatingApplicationName>
Output from running FITS v1.4.1 command line tool on same file:
<creatingApplicationNametoolname="Jhove"toolversion="1.20.1"status="CONFLICT">Microsoft® Word 2010/Microsoft® Word 2010</creatingApplicationName>
The text was updated successfully, but these errors were encountered:
Do you have a sharable file and method by which you are submitting the file that we can test? We don't believe that Jhove should be called for word documents to begin with so it is interesting that you are seeing this error at all. The latest container may have corrected the character encoding but we can't prove it without a file to test against.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I've been using the latest published image of this project and am seeing the encoding issue reported at harvard-lts/fits#186.
Example snippets:
Output from FITSServlet container service:
Output from running FITS v1.4.1 command line tool on same file:
The text was updated successfully, but these errors were encountered: