Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add custom_signatures that include rules about extensions #39

Open
clausjuhl opened this issue Jun 14, 2024 · 0 comments
Open

Add custom_signatures that include rules about extensions #39

clausjuhl opened this issue Jun 14, 2024 · 0 comments
Labels
custom signature Possible new costum signature

Comments

@clausjuhl
Copy link
Member

We should implement functionality that enables custom rules that take extensions into account when making decisions about the correct file format.

An example could be .emz files that are correctly identified by Pronom as gzipped files, but they only use the gzip format as a compression container and it makes no sense to extract .emz files with unarchiver.

Another example is .dat files which are related to Mapinfo projects. They are also correctly identified as dBase files, but when related to a GIS project, they only make sense in relation to the other project files. Fortunately, it is possible to reidentify those .dat files using their byteheader, but that is not the case with .emz files.

@clausjuhl clausjuhl added the custom signature Possible new costum signature label Jun 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
custom signature Possible new costum signature
Projects
None yet
Development

No branches or pull requests

1 participant