View Single Post
Old Yesterday, 11:44 AM   #7
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
An epub has a specified set of allowable core media-types. You can find that list here:

https://www.w3.org/TR/epub/#sec-core-media-types

These are the only media types allowed to be in epubs unless you specify a fallback resource for them. But that said, very few epub3 e-readers support fallbacks as listed in the opf. See the next part in the spec on fallbacks, in the link provided above.

Try to stick with recognized file types (media types) and you should be fine.

Note: "application/x-bplist" NOT a recognized epub3 core media type.

Since I have no idea what a bplist is, I can not help. If it is a binary Apple plist, then remove the need for it as epub files are not writeable. If it is a network backup thing, then remove the need for it as epubs can be read offline.

Pulling in javascript libraries from npm is rarely something that will work in an epub unless they were properly designed to do so.

Perhaps if you want to create "advanced" epubs, you should read and understand the epub3 specification and its limitations. It can't hurt.

Last edited by KevinH; Yesterday at 11:51 AM.
KevinH is online now   Reply With Quote