David Clipsham

Note that [Siegfried ](https://github.com/richardlehane/siegfried) Correctly handles the original intent with the original skeletal test files I created - each accurately identifies as fmt/142 except for the file [Should_be_nope_FEFF.txt](https://github.com/digital-preservation/droid/files/9377581/Should_be_nope_FEFF.txt) which falls...

Not a disimmilar conclusion to that which the 7zip folk came to: https://sourceforge.net/p/sevenzip/discussion/45798/thread/9e936d87/ Out of interest does OLM at least ID now with the TrueVFS update?

Well the reason is that a container signature identification is considered more definitive than a zip (because many container based formats use zip as their wrapper) so when it finds...

Interesting scenario, not covered in the original FF ID documentation (https://www.nationalarchives.gov.uk/aboutapps/fileformat/pdf/automatic_format_identification.pdf see section 3. starting at page 13). As the signature for Freehand 1 is only using ASCII characters from...

Thanks @steve-daly - by my count there are 86 Signatures that have at least one variable sequence - every single one of them has either a BOF or an EOF...

In answer to your question about defaults for GUI & CLI - I favour behavioural consistency, so having both default to full scan would be my preference.

Thank you for your comments Matt, The most frequent ones that seem to get queried are PDF/A or similar PDF variants (where the conformance tags are often found deep within...

Thank you for looking at this @jcupitt - As I understand it we're using `magickload` as a general purpose because of the wide variety of origin image formats we need...

There's no identification signature for x-fmt/152 yet but they should at least be coming up with an extension-match. Are you running DROID at command line or GUI? Is there anything...

I've posted a corrected Container Signature file in #924