You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure what will be possible/practical/best. It feels like it ought to be easier to integrate ebookmaker, given that it too is written in python, but that depends on a bunch of stuff I know nothing about related to how ebookmaker is structured. So, there are a few options:
Import ebookmaker as a module somehow, and treat it like we do the new pptxt.
Install ebookmaker as part of the GG installation, then run it as an external python tool
Continue with an ebookmaker.exe on Windows, like GG1, and use method 2 for other platforms, or leave it to the user to sort out.
Don't bundle/integrate - PPer will have to use online ebookmaker - we could have a menu option that links to the ebookmaker webpage instead
Consider whether we should include the W3C Epubcheck tool, like GG1 has.
The text was updated successfully, but these errors were encountered:
I tend to agree that option 4 sounds good. I realize that some PPers like to be able to do everything after they download the PP files offline, but the likelihood that the included version would be stale within a day or three of a GG2 release is pretty high.
I also agree about option 4 (and it's what I do myself). Two reasons:
Ebookmaker install always seemed to break for me; I gave up trying to maintain it. I'm probably not the only one.
Ultimately, our "customer," the PPer, is responsible to produce text and HTML; it's PG who creates the ebook files, and regenerates them periodically. And as we know, there's an effort to produce other formats like PDFs from the same source material. None of this is produced or uploaded by the PP'er directly.
So I think it's appropriate to point to the PG tooling for this. A motivated PP'er can always install Ebookmaker on their own, of course.
Not sure what will be possible/practical/best. It feels like it ought to be easier to integrate ebookmaker, given that it too is written in python, but that depends on a bunch of stuff I know nothing about related to how ebookmaker is structured. So, there are a few options:
Consider whether we should include the W3C Epubcheck tool, like GG1 has.
The text was updated successfully, but these errors were encountered: