View Single Post
Old 01-23-2026, 11:39 AM   #574
JimmXinu
Plugin Developer
JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.
 
JimmXinu's Avatar
 
Posts: 7,257
Karma: 5007213
Join Date: Dec 2011
Location: Midwest USA
Device: Kobo Clara Colour running KOReader
Not having seen the epubs in question, I am speculating.

But what I would guess, is that Draft2Digital is looking at the extra toc.ncx files retained by EpubMerge for UnMerging. Evidence: "/1/toc.ncx"

IMO, this is a mistake in Draft2Digital's processing. Those files should be ignored. OTOH, they are unnecessary and in a clean published book should technically be removed.

It isn't practical for EpubMerge to change the identifier in those files--they need to match the merged sub-book for UnMerge to work.

I suggest that, before doing your final merge, you go into EpubMerge's config and uncheck 'Keep UnMerge Metadata?'. Then EpubMerge won't include those extra toc.ncx (and content.opf files).

Or, if retaining UnMerge is important to you, use Edit book just before uploading to manually remove the extra toc.ncx and content.opf files--ONLY the ones with a number in front: 1/toc.ncx, 1/content.opf, 2/toc.ncx, 2/content.opf, etc.
JimmXinu is offline   Reply With Quote