-
-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Question] Do we manually add metadata to the finished epub files #8
Comments
I know that in travis.yml right now, we're adding stuff to epub file -- don't remember whether there is a manifest in epub that we should be / (must be?) updating whenever we add files, directories to an epub. @eshellman -- do you remember whether we can just add extra files to an epub while keeping epub readers and/or epub validators (like epubcheck) happy? |
Partially answering my own question. When I run epubcheck (v 3.0.1) on https://github.com/GITenberg/Adventures-of-Huckleberry-Finn_76/releases/download/v0.0.3/Adventures-of-Huckleberry-Finn.epub, I get the following WARNINGS (but not ERRORS):
|
I strongly recommend using something like pyepub to manipulate epub files.
|
Good catch. We should:
|
look at https://github.com/Gluejar/regluit/blob/master/core/epub.py https://github.com/Gluejar/regluit/blob/master/core/epub.py
|
@eshellman's idea to use pyepub makes sense -- it should take care of the manifest. How much of a priority is it to get the manifest right by using pyepub? |
a bad manifest will cause kindlegen to choke
|
Does kindlegen choke on the latest release for Huck Finn?
|
I am worried we can't put a version into the epub files. We should know the git commit or tag that built the book.
How hard is it to add this metadata directly to the final epub file? Can we implement this in time?
The text was updated successfully, but these errors were encountered: