Closed sprater closed 9 months ago
@sprater This is a jhove bug. I recommend opening a ticket with them.
Before FITS runs a file through jhove, it first executes the jhove signature check to determine which module to run. In this case, this produces:
./jhove -s ~/Downloads/misidentified-text.txt
Jhove (Rel. 1.28.0, 2023-05-18)
Date: 2024-02-23 16:21:56 CST
RepresentationInformation: /home/pwinckles/Downloads/misidentified-text.txt
ReportingModule: AIFF-hul, Rel. 1.6.2 (2022-04-22)
LastModified: 2024-02-23 16:14:27 CST
Size: 1761
Format: AIFF
Status: Well-Formed
SignatureMatches:
AIFF-hul
MIMEtype: audio/x-aiff
So, jhove says to use the AIFF-hul, and that's what FITS does.
Thanks. And I see the bug is still in the current version of Jhove.
Jhove issue submitted: https://github.com/openpreserve/jhove/issues/902
As far as I am concerned, this ticket can be closed/withdrawn.
When running FITS 1.6.0 on certain plain text files, the Jhove check fails, and the file is reported to be an invalid AIFF file:
The other tools correctly identify the file as a text file.
I tried running the file through Jhove 1.26.1, using the same Jhove configuration as the one distributed in FITS 1.6.0; Jhove on its own identifies the file correctly.
The files we have that fail in this way all start with the word "FORM". Attached is the sample file that provokes the error, as well as the full output of FITS when run on this file.
fits-output.txt misidentified-text.txt