-
Notifications
You must be signed in to change notification settings - Fork 587
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
[Bug]: The warning about unrecognized media types cannot be dismissed because there are too many files. #791
Comments
I will look into creating an abort to a load. But incorrect media types should be very very rare as the list of recognized media types is given right in the epub spec. Please post a copy of the OPF here so we can see what incorrect media type is being used so often. |
Just to verify, is this with the just released Sigil-2.4.0? The code that implements load warnings was recently changed. |
yes,It was just downloaded. |
These are two articles I exported casually. This EPUB was converted from HTML using other software. |
Whatever you created is NOT an epub. Files are missing file extensions and media-types are explicitly left blank. Archive: test.epub And from the content.opf manifest there are missing media-types:
So you should instead file a bug report with: Sigil is an epub editor, not an editor for crap just called "an epub" without it meeting any of the basic structure of the epub specifiication. So I am closing this as not a bug as missing media-type values for files without file extensions are very rare meaning that user's of Sigil should never have to deal with this when actually editing real epubs. Maybe in a future release we will add a skip or abort warnings capabilities, but for the foreseeable future this is really not needed. |
You might want to point out to the epub-gen npm crowd that looking for magic bytes at the start of files and mapping them to image types would certainly help to create a more proper content.opf: cp OEBPS/images The content.opf should have included the proper media-type in the manifest for each file. That is required in both epub2 and epub3 specifications. And without a proper file extension, Sigil can not easily guess and would have to probe each and every file before trying to load the correct type of resource. |
OK. Thank you for your answer. |
Bug Description
I edited a converted EPUB file, but when I opened it, I was greeted with a barrage of warning pop-ups. I couldn't do anything except click "OK" or "Close" repeatedly. With over 400 pages, I pressed the Enter key for several minutes and the pop-ups just wouldn't stop.
Platform (OS)
Windows (Default)
OS Version / Specifics
windows11
What version of Sigil are you using?
current
Any backtraces or crash reports
The text was updated successfully, but these errors were encountered: