[jackie_w]

First off, thank you for the new addition

Originally Posted by kovidgoyal

Although you should not rely on the fact that all html files will be in the spine, there exist books where that is not true.

I guess that can be true, but for my own purposes I only want to tweak HTML files which are in the spine. The rest I'll leave well alone.

Originally Posted by kovidgoyal

For ToC you dont want to be using NCX/nav, instead use the functions in polish.toc, like find_existing_toc etc. Similarly for covers, you should use the functions in polish.cover

I've been using find_existing_ncx_toc, find_existing_nav_toc to get the NCX, nav names. Also more recently get_toc and the attribute toc_file_name.

I've also been using find_cover_image to get the name for cover_image, although perhaps I should be using get_raster_cover_name.

Getting the name for cover_page is a little trickier. I've been using a combination of find_cover_page and find_cover_image_in_page which so far has been OK for my own epubs (which all have a calibre-SVG-style cover) but perhaps too simplistic for a general solution. Do you have a more robust suggestion?

The point I'm trying to make is that although the functionality is probably already available, if you're just starting out with personal tweaking, finding it can be a bit daunting Gathering it all together in plain view in the Container would have been very helpful to me in the early days - reduced thinking time - or maybe that's not such a good idea after all.