Correction! All clickable (HTML style) links in my ePub are purple, and I suppose the TOC are a list of clickable links to anchors within the document. So the purple thing (for TOC entries) isn't an issue after all.
But I still don't have any idea why -fepub (using a2x) doesn't generate the bk01-toc.html file for you and breaks the build, or why creating an empty bk01-toc.html makes TOC generation work for ePub. On Wednesday, November 22, 2017 at 11:02:55 AM UTC-6, Shep wrote: > > OK, followed your link and tried this, which seems to me should have done > the trick: > > a2x -fepub -dbook -adocinfo --xsltproc-opts "--stringparam generate.toc > \"book toc\"" book.txt > > > But I get this error: > > a2x: ERROR: missing resource: /Users/AJTSheppard/Documents/Writing/Book - > Goodbye Google/Gmail/bk01-toc.html > > > Here are some more parts the --verbose version (which is very long): > > ... > > a2x: executing: "xsltproc" --stringparam generate.toc "book toc" > --stringparam callout.graphics 0 --stringparam navig.graphics 0 > --stringparam admon.textlabel 1 --stringparam admon.graphics 0 > --stringparam toc.section.depth 1 --stringparam chunk.section.depth 0 > "/opt/local/etc/asciidoc/docbook-xsl/epub.xsl" > "/Users/AJTSheppard/Documents/Writing/Book - Goodbye Google/Gmail/book.xml" > > > Writing OEBPS/pr01.html for preface > Writing OEBPS/ch01.html for chapter(_introduction) > Writing OEBPS/ch02.html for chapter(non-an-all-or-nothing-thing) > Writing OEBPS/ch03.html for chapter(_a_very_brief_history_of_google) > Writing OEBPS/ch04.html for > chapter(_a_list_of_google_products_and_services) > Writing OEBPS/ch05.html for > chapter(_google_terms_of_service_amp_privacy_policy) > Writing OEBPS/ch06.html for chapter(_voice_and_face_recognition) > Writing OEBPS/ch07.html for chapter(_how_email_works) > Writing OEBPS/pt01.html for part(_reasons_to_say_goodbye) > Writing OEBPS/ch08.html for chapter(gameplan) > Writing OEBPS/ch09.html for chapter(step1) > Writing OEBPS/ch10.html for chapter(step2) > Writing OEBPS/ch11.html for chapter(step3) > Writing OEBPS/ch12.html for chapter(step4) > Writing OEBPS/ch13.html for chapter(step5) > Writing OEBPS/ch14.html for chapter(step6) > Writing OEBPS/pt02.html for > part(_a_step_by_step_guide_to_replacing_gmail_with_something_better) > Writing OEBPS/apa.html for appendix(A1) > Writing OEBPS/apb.html for appendix(A2) > Writing OEBPS/apc.html for appendix(A3) > Writing OEBPS/pt03.html for part(_resources) > Writing OEBPS/co01.html for colophon(_book_description_back_cover) > Writing OEBPS/index.html for book > Writing OEBPS/toc.ncx > Writing OEBPS/../OEBPS/content.opf > Writing OEBPS/cover.html for mediaobject > Writing OEBPS/../META-INF/container.xml > > > ... > a2x: finding resources in: /Users/AJTSheppard/Documents/Writing/Book - > Goodbye Google/Gmail/book.epub.d/OEBPS/pt02.html > a2x: finding resources in: /Users/AJTSheppard/Documents/Writing/Book - > Goodbye Google/Gmail/book.epub.d/OEBPS/pt03.html > a2x: ERROR: missing resource: /Users/AJTSheppard/Documents/Writing/Book - > Goodbye Google/Gmail/bk01-toc.html > > > > On Tuesday, November 21, 2017 at 5:11:50 AM UTC-6, Lex Trotman wrote: >> >> On 21 November 2017 at 20:58, Shep <[email protected]> wrote: >> > Here's my Asciidoc markdown, minimal-book.adoc: >> > >> > = The Book Title >> > >> > == The first chapter >> > Nec vitae mus fringilla eu vel pede sed pellentesque. Nascetur fugiat >> > nobis. Eu felis id mauris sollicitudin ut. Sem volutpat feugiat. >> > Ornare convallis urna vitae. >> > >> > Nec mauris sed aliquam nam mauris dolor lorem imperdiet. >> > >> > == The second chapter >> > Ut suspendisse nulla. Auctor felis facilisis. Rutrum vivamus nec >> > lectus porttitor dui dapibus eu ridiculus tempor sodales et. Sit a >> > cras. Id tellus cubilia erat. >> > >> > Quisque nullam et. Blandit dui tempor. Posuere in elit diam egestas >> > sem vivamus vel ac. >> > >> > >> > Here's how I build the book: >> > >> > >> > a2x -fepub -dbook -atoc minimal-book.adoc >> > >> > >> > Resulting ePub doesn't have a TOC! >> >> As I stated in a previous message, Asciidoc only generates TOCs for >> xhtml and HTML5. >> >> To be excessively detailed, actually it doesn't, it inserts javascript >> that generates the TOC in the browser, so that won't work with docbook >> toolchains, which includes epub. >> >> You need to teach the epub toolchain (which I think is an XSLT >> transform) to do it, the Sagehill docs I posted before should provide >> that information, see >> http://www.sagehill.net/docbookxsl/TOCcontrol.html. >> >> Cheers >> Lex >> >> > >> > -- >> > You received this message because you are subscribed to the Google >> Groups >> > "asciidoc" group. >> > To unsubscribe from this group and stop receiving emails from it, send >> an >> > email to [email protected]. >> > To post to this group, send email to [email protected]. >> > Visit this group at https://groups.google.com/group/asciidoc. >> > For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "asciidoc" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
