Quote:
Originally Posted by DiapDealer
Kepub should be considered proprietary in my mind. Only Kobo uses it. I have no idea if it's spec compliant or not (I tend to doubt it), but I'm not on board with adding it as an extension that Sigil can handle inherently.
|
Kepub is completely spec compliant with ePub. The main difference is the addition of spans that are used for location for annotations/bookmarks ( sample would be <span class="koboSpan" id="kobo.4.1">In porttitor. </span> ). Since a Kobo ereader looks for a .kepub.epub extension to indicate a kepub, on my computer, it is handled as an .epub file. A while back, it was common for ePub3 Kobo ebooks to have javascript but I've seen that less over the last few years.
The only place where I used to find .kepub files was in my calibre library where I converted the occasional ePub that benefited from using the Kobo renderer and stored it as filename.kepub to which calibre appended .epub when sending to device. Since calibre now allows converting to kepub on the fly, I now just have a column that decides which format to send.
All this being said, I see no good reason for trying to handle kepub files as separate from ePub files.