epub-tools
epub-tools copied to clipboard
dino-
Command line utilities for working with epub files
We aren't using a `` tag without any attributes. Make the search go like this: ... ... ... And update the usage to reflect this.
``` Preprocessing test suite 'epubname-tests' for epub-tools-2.11.. Building test suite 'epubname-tests' for epub-tools-2.11.. [ 1 of 13] Compiling EpubTools.EpubName.Doc.Rules ( src/EpubTools/EpubName/Doc/Rules.hs, dist/build/epubname-tests/epubname-tests-tmp/EpubTools/EpubName/Doc/Rules.o ) [ 2 of 13] Compiling EpubTools.EpubName.Util (...
Even with `-v`, the output of `epubmeta path/to/ebook.epub` does not include some pieces of metadata. For my particular use-case (identifying which ebooks downloaded from AO3 are in a series) I...
At the moment we can only save it to a file.
Addresses GH-13 You may need to do `stack upgrade` before `stack build`, otherwise you are likely to get errors such as: ``` Unable to load cabal files for snapshot ......
This will probably give us a lot of non-English book support out-of-the-box, but will need lots of tests to see how that goes.
When running the tests from a fresh clone and build, I get ``` epub-tools-2.11: test (suite: epubname-tests) ### Error in: 0:Format:51 user error (Text.Regex.Posix.String died: (ReturnCode 17,"illegal byte sequence")) Cases:...
The few updates we've done at work have been trivial, hoping 10.0 - 13.xx will be only marginally more difficult. Any known reason not to update?
In Contributing.md, please add things like: - what formatting tool to use - what linter to use - etc In addition to this, add config files for the various tools.