View Single Post
Old 01-23-2012, 04:41 PM   #2
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,849
Karma: 6120478
Join Date: Nov 2009
Device: many
Hi,

The key is that both versions must use all of the same support files and access them in the same order.

"Note that embedding images and fonts happens when the first version is created; the links in the kf8 version will point to the wrong object if the two sources don’t include the same files in the same order."

This is not easy to guarantee or even do especially with very different mobi and mobi8 pieces. Also, since the fonts are stored alongside and intermixed with the image files, they must all be know in advance and available when the older mobi is created (even though they come from the KF8 side - like fonts).

If you could guarantee that, then putting together a standalone python script to merge them is just not that hard to do. If however, the two sources do not access the same images in the same order (or fonts?), then this is much harder to do as it would require changing the raw ML inside of each part.

It seems to me that having/using two different css stylesheets should go a long way to getting good .mobi and .mobi8 pieces and that is supported.
KevinH is online now   Reply With Quote