View Single Post
Old 02-21-2016, 08:58 PM   #8
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,893
Karma: 6120478
Join Date: Nov 2009
Device: many
Hi DiapDealer,
Since the next release of Sigil is still weeks away (I have a lot of semantic and nav landmark changes to make yet), would you please modify your fixv1 plugin to change 1 to 2 as well as pass through version 2.0 and 3.0 unchanged but make sure you add a xml declaration heading to the opf file if it is missing.

That will help people load in epubs not created in Sigil until we get a new release out. Either that or we can pull the Sigil-0.9.3 tag and add just the bug fixes and release a Sigil 0.9.3b version.

Thanks!

KevinH


Quote:
Originally Posted by DiapDealer View Post
Thanks Kevin!

I'm guessing this explains the post in the Sigil v0.9.3 release thread (which prompted the FixOPFv1 plugin) where people were running into opf package version "1.0" epubs (pre-existing epubs) so often. Sounds like this bug has been making people think there's way more plugins out there with incorrect package versions than there really are, for a very long time!
KevinH is offline   Reply With Quote