View Single Post
Old 11-11-2019, 08:59 AM   #41
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
That is up to you. There is nothing inherently wrong when creating an ebook from scratch to use a layout you like. Sigil's default epub layout is in fact a very logical and good one. But some epubs like compendiums and some epub3's that use prebuilt location specific javascripts, need a specific epub layout. Sigil could never properly edit them before without a lot of renaming, and even sometimes breakage. That is why Sigil is needed this feature before it claim "1.0" status.
As for me, I rarely use or need a different structure than what Sigil defaults to. That said, since this is an alpha release for testing purposes, I hope everyone is loading one of their non-standard epubs and trying hard to break Sigil and reporting back.

As for plugins, the other main purpose of this alpha release, is to give plugin developers access to a working version of the new plugin interface so that they could update their plugins before Sigil 1.0 is actually released. So please ask nicely in the Plugin's thread for an update to work with Sigil 1.0 but understand not everyone will update things soon.

I personally would be happy to help update any plugin developers plugins if they run into any difficulties.

If you have skills in python, another approach is to fix that plugin yourself and give the changes back to the developer after testing that it works with standard and non-standard epubs as well as on Sigil-0.9.991 and the previous Sigil-0.9.18.

Hope this helps,

KevinH


Quote:
Originally Posted by odamizu View Post
I've spent a little time playing with Sigil 0.9.991 on macOS High Sierra, and so far so good. I also opened 0.9.991 on Catalina, but haven't done anything further than to make sure it launches successfully.

Sigil itself is running fine so far, however I've run into one plugin (InsertImageSVG) that fails when it comes to epubs with non-Sigil-standard structures. Using Tools > Restructure Epub to Sigil Norm solves the problem.

QUESTION: I understand KevinH and DiapDealer went to great lengths to enable Sigil to accept and handle any epub structure. Is there an advantage to leaving the epub in its original non-Sigil-standard structure? Is there any reason that I should not use the Tools > Restructure Epub to Sigil Norm as soon as I load an epub into Sigil as part of my workflow now?
KevinH is offline   Reply With Quote