-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
writer for AZW3 (Kindle native format) #1865
Comments
I hadn't heard of that. Nice idea. As far as I can see, it's not too I don't see myself getting to this in the near future, but someone else |
looking forward to this |
Hey, I intend to start work on this and I haven't contributed before. What documentation would be key for understanding the interface the writer will have to implement? What are the most important modules it will interact with? I'm going to model the AZW3 writer off of the EPUB writer, so some things will be obvious, but any advice would be appreciated as well. |
The EPUB writer is somewhat special in that it basically calls the HTML writer and does some pre- and post-processing and then zips everything. If EPUB and AZW3 are very, very similar, it might even make sense to implement azw3 as an extension to the EPUB writer. Personally, I would probably convert to epub and then use calibre of KindleGen to go to AZW3, instead of writing a pandoc writer, but maybe there are use-cases which I'm not considering... |
I should also say that (as the author of the EPUB
writer) I don't think the code quality is very good.
(It should be broken down into smaller units, and
types should be used more.) But as far as the
interface goes, it should give you a good idea of what
needs to come in and go out!
Note that everything happens in an instance of
PandocMonad, which gives you functions for issuing
warnings, fetching resources, and putting resources
in a "media bag." Studying what the EPUB writer does
should show you how this works, but of course we're
happy to answer any questions.
As @mb21 says, if there are just a few changes from
EPUB, we could consider adding an extension to EPUB
(and maybe HTML) so we wouldn't actually need a
completely new module.
Mauro Bieg <notifications@github.com> writes:
… The EPUB writer is somewhat special in that it basically calls the HTML writer and does some pre- and post-processing and then zips everything. If EPUB and AZW3 are very, very similar, it might even make sense to implement azw3 as an [extension](http://pandoc.org/MANUAL.html#extensions) to the EPUB writer.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#1865 (comment)
|
After a comment by JGM (jgm#1865 (comment)) we refactored EPUB.hs to make it more readable. More refactoring may be necessary, but this is probably a nice first step. Co-authored-by: Ola Wolska <A.k.wolska@student.tudelft.nl@gmail.com> Co-authored-by: Jonathan Dönszelmann <jonabent@gmail.com> Co-authored-by: Jaap de Jong <jaapdejong15@gmail.com>
After a comment by JGM (jgm#1865 (comment)) we refactored EPUB.hs to make it more readable. More refactoring may be necessary, but this is probably a nice first step. Co-authored-by: Ola Wolska <A.k.wolska@student.tudelft.nl@gmail.com> Co-authored-by: Ivar de Bruin <ivardb@gmail.com> Co-authored-by: Jaap de Jong <jaapdejong15@gmail.com>
@jgm, I wonder whether a writer for the Kindle native format could be added to issue #1852.
The text was updated successfully, but these errors were encountered: