-
Notifications
You must be signed in to change notification settings - Fork 5
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
Add flattening of AsciiDoc indexes and dir structures #13
Comments
My approach (admittedly less elegant) was to generate epub from the single-page html... |
Hmmmm. I'm more than a little bothered that I did not think of that. Let me get to work getting out of your way. |
Yeah, honestly, if it's not lossy, I don't really see your solution as less elegant, even. HTML is a legitimate source format if there's a good HTML -> ePub converter. |
Single line of pandoc works
Although there is some slight oddness with the heading levels. Part Five: Evolving seems to be at a different level to everything else. And then, to make it Kindle suitable
Has some wibbles. None of this is really production suitable, but it does get it onto my kindle so I can read it... :-D |
No. Way. That is so cool. I never even thought of it. You're giving me some ideas..... Thanks for being patient. I hope the content is worth it! LMAO |
One frustrating limitation of Asciidoctor's ePub generator is that it requires all included source
.adoc
files to be in the same directory. This isn't convenient for large, complex documents (like, ahem, books). Let's help AsciiDoc authors by giving an option toflatten
the structure during migration, so we can move an index file and all its dependencies (includes, images, etc) into a build/scratch directory, and we'll build the ePub (and other Asciidoctor) output from there.This requires flattening the
include::
macros as well as flatting the actual file structure during the move, dumping it all in the same target dir.The text was updated successfully, but these errors were encountered: