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

set handlers really by extensions, not merely by mime-type hiding behind extensions #56

Open
evanescente-ondine opened this issue Jan 31, 2022 · 1 comment

Comments

@evanescente-ondine
Copy link

Hi
I just nocticed ffmpeg isn't setting mimetype properly, or not always at least. It happened with a .nut video I compiled, that reads well with mpv etc, but it's mime-type is absent..
SCP Dollhouse.nut: application/octet-stream; charset=binary
Handlr isn't liking that very much.
So if it could do what it says it can do (setting handlers by extension, regardless of mime-type) it would be neat.

GREEEEEEEEEEEEEEEEEEEEEEEAT program otherwise, lightning-fast too, I love you guys.

@evanescente-ondine
Copy link
Author

evanescente-ondine commented Oct 28, 2024

Yes, this is STLL irritating, two years later.
Many plain text files have no mimetype associated, not just text easier, take the .nut video / mutlimedia container format.
Even when the "file" command sees the mime type, handlr may not see it. Here the mimetype given for a .lit file is "application/x-ms-reader", but handlr can't determine it.
One would imagine using extensions should be easier, no ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant