View Single Post
Old 04-11-2021, 10:41 AM   #51
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,917
Karma: 6240958
Join Date: Nov 2009
Device: many
@Tex2002ans,

A few others questions related to merge. What happens in calibre during a merge if the chapters being merged are linked to different non-identical css stylesheets?

Does it try to merge stylesheets? I am not sure there is a guaranteed safe way to do a merge like that if the same class name is defined differently in two different stylesheets.

Also your testcase epub has a large guide section, that could end up being treated in different ways depending on the merge.

Would you please use calibre to run the merge of your testcase and copy the resulting guide section of the opf (post merge) and post it here.


Doing a merge of something that was split out is inherently safe and easy since all ids will be unique and all files will use the same stylesheets and no class definitions will differ that use the same selector.

Merging truly separate chapters whose files reuse ids, and that may use different stylesheets and even different class definitions under the same name is going to require some post merge hand work. Not to mention the impact on ncx, guide, and nav.

Thanks.

KevinH

Last edited by KevinH; 04-11-2021 at 11:02 AM.
KevinH is online now   Reply With Quote