files not listed in the manifest

lumpynose · 07-29-2019, 04:09 PM

I'm trying to add covers to epubs I've downloaded from Project Gutenberg. I'm following davidfor's suggestion and using Calibre's Polish books function. After I run that on the following book, when I open the folder where the book is in Calibre's library and double click on the epub file I get Sigil's warning "Files exist in epub that are not listed in the manifest, they will be ignored" and clicking on the details button lists nav.xhtml. If I unzip the epub and look at the content.opf file it does list the nav.xhtml file in the manifest section. If I save the epub and then open it again the error doesn't appear.

For Polish books, the options I have checked are Smarten punctuation, Update metadata in the book files, Update cover in the book files, and Upgrade book internals.

https://www.gutenberg.org/ebooks/16334 (the no images epub)

Any ideas why Sigil is giving that warning?

DiapDealer · 07-29-2019, 04:32 PM

Since it's PD, can you post a version of the epub that is ready to give the error upon opening in Sigil?

Also ... Sigil version and O.S. ?

DiapDealer · 07-29-2019, 04:36 PM

I'd forgotten how much I despise Gutenberg's file-naming protocol.

DiapDealer · 07-29-2019, 04:39 PM

At which point in the process are you converting the epub in question from epub2 to epub3? Or is that what the "Upgrade book internals" option in calibre's Polish does? I've not kept up with how calibre's Polish options have evolved.

EDIT: I appears I don't even know HOW to polish a book in calibre any more.

DiapDealer · 07-29-2019, 05:10 PM

OK. I got the error message to pop up. I'll try and see what might be going on. My guess is the nav is getting lost in the shuffle of the restructuring of the archive that Sigil requires. We don't typically need to move the nav for our own epubs, so something might be falling through the cracks, there.

KevinH · 07-29-2019, 05:19 PM

I am betting this is caused by missing nav manifest property in the calibre generated update to epub 3 which happens with that Upgrade Book Internals option.

So you might want to save the calibre generated epub after the update and post the epub (as zip here). That way we can see what is confusing Sigil.

DiapDealer · 07-29-2019, 05:37 PM

No. The nav manifest property seems to be correctly set. The only odd thing I'm seeing (utterly ridonkulous gutenberg file-names aside) is that the nav document itself is created in the root of the archive (with the mimetype) instead of being alongside the opf file. Still, the href to the nav seems to be correct. There's some attribute errors in one of the html files (and warnings about the html extensions, of course), but other than that, EpubCheck seems to be content with the structure of the epub itself. Unless I'm missing something, I don't think Sigil should be throwing up that error. Especially considering that Sigil succesfully updates the href to it.

I'll attach the problematic version so you can join in.

KevinH · 07-29-2019, 05:51 PM

I'll take a peek. I am surprised that the physical location matters at all given how FolderKeeper actually works.

DiapDealer · 07-29-2019, 05:56 PM

Quote:

Originally Posted by KevinH

I'll take a peek. I am surprised that the physical location matters at all given how FolderKeeper actually works.

That was my thought as well.

I'm guessing that the error is somehow being triggered after the moving of the nav to it's new location and before the href to it gets updated in the opf. But that's not based on anything at all concrete: I haven't really jumped into it yet. We DID make a few tweaks to GetRelativePathToRoot() and few other functions in Resource.cpp recently didn't we?

KevinH · 07-29-2019, 06:11 PM

Okay, I just pushed a fix to master. But as far as I can tell, this only impacts the warning message. In other words, the nav.xhtml file should actually be in Sigil correctly and in the manifest correctly and it is the only the warning that is messed up.

So until the fix comes out, simply ignore that particular warning.

lumpynose · 07-29-2019, 06:38 PM

Quote:

Originally Posted by KevinH

Okay, I just pushed a fix to master. But as far as I can tell, this only impacts the warning message. In other words, the nav.xhtml file should actually be in Sigil correctly and in the manifest correctly and it is the only the warning that is messed up.

So until the fix comes out, simply ignore that particular warning.

Thanks guys!

07-29-2019, 04:09 PM	#1
lumpynose Wizard Posts: 1,086 Karma: 6719822 Join Date: Jul 2012 Device: Palm Pilot M105	files not listed in the manifest I'm trying to add covers to epubs I've downloaded from Project Gutenberg. I'm following davidfor's suggestion and using Calibre's Polish books function. After I run that on the following book, when I open the folder where the book is in Calibre's library and double click on the epub file I get Sigil's warning "Files exist in epub that are not listed in the manifest, they will be ignored" and clicking on the details button lists nav.xhtml. If I unzip the epub and look at the content.opf file it does list the nav.xhtml file in the manifest section. If I save the epub and then open it again the error doesn't appear. For Polish books, the options I have checked are Smarten punctuation, Update metadata in the book files, Update cover in the book files, and Upgrade book internals. https://www.gutenberg.org/ebooks/16334 (the no images epub) Any ideas why Sigil is giving that warning?

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Manifest has disapeared	failure1	Introduce Yourself	2	04-08-2018 04:36 AM
Multiple HTML files w/ TOC to MOBI, not added in order listed in TOC	dysfunction	Conversion	3	01-03-2014 12:40 AM
"files not listed in OPF" ARE listed. what do I do?	lucita	ePub	8	04-18-2013 04:29 PM
Sigil re-sorts files listed in book view!	lindaw2396	Sigil	7	11-17-2012 03:43 PM
XHTML files not listed, only one HTML file	SmartyGuy	Sigil	6	06-21-2011 12:32 PM

07-29-2019, 04:32 PM	#2
DiapDealer Grand Sorcerer Posts: 27,549 Karma: 193191846 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	Since it's PD, can you post a version of the epub that is ready to give the error upon opening in Sigil? Also ... Sigil version and O.S. ?

07-29-2019, 04:36 PM	#3
DiapDealer Grand Sorcerer Posts: 27,549 Karma: 193191846 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	I'd forgotten how much I despise Gutenberg's file-naming protocol.

07-29-2019, 04:39 PM	#4
DiapDealer Grand Sorcerer Posts: 27,549 Karma: 193191846 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	At which point in the process are you converting the epub in question from epub2 to epub3? Or is that what the "Upgrade book internals" option in calibre's Polish does? I've not kept up with how calibre's Polish options have evolved. EDIT: I appears I don't even know HOW to polish a book in calibre any more.

07-29-2019, 05:10 PM	#5
DiapDealer Grand Sorcerer Posts: 27,549 Karma: 193191846 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	OK. I got the error message to pop up. I'll try and see what might be going on. My guess is the nav is getting lost in the shuffle of the restructuring of the archive that Sigil requires. We don't typically need to move the nav for our own epubs, so something might be falling through the cracks, there.

07-29-2019, 05:19 PM	#6
KevinH Sigil Developer Posts: 7,644 Karma: 5433388 Join Date: Nov 2009 Device: many	I am betting this is caused by missing nav manifest property in the calibre generated update to epub 3 which happens with that Upgrade Book Internals option. So you might want to save the calibre generated epub after the update and post the epub (as zip here). That way we can see what is confusing Sigil.

07-29-2019, 05:51 PM	#8
KevinH Sigil Developer Posts: 7,644 Karma: 5433388 Join Date: Nov 2009 Device: many	I'll take a peek. I am surprised that the physical location matters at all given how FolderKeeper actually works.

07-29-2019, 06:11 PM	#10
KevinH Sigil Developer Posts: 7,644 Karma: 5433388 Join Date: Nov 2009 Device: many	Okay, I just pushed a fix to master. But as far as I can tell, this only impacts the warning message. In other words, the nav.xhtml file should actually be in Sigil correctly and in the manifest correctly and it is the only the warning that is messed up. So until the fix comes out, simply ignore that particular warning.

Advert

Advert