From: David Snopek <dsnopek-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: EPUB toc for whole book?
Date: Mon, 7 May 2012 17:13:55 -0500 [thread overview]
Message-ID: <CADca9RdSo1NdMDsFDGhEC-YejS4pcgKQNOr2DpvVL_TWS9P15Q@mail.gmail.com> (raw)
In-Reply-To: <20120428150316.GA405-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1108 bytes --]
2012/4/28 John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>:
>
> Internal links between chapters do work in pandoc 1.9.2 -- but
> maybe not in the way you expect. You need to create
> the links using the implicit identifiers described in
> <http://johnmacfarlane.net/pandoc/README.html#header-identifiers-in-html-latex-and-context>.
Hey Guys!
Sorry for my late reply. I just figured out what was wrong with the
internal links in EPUB. For some reason, if you have any content in
the beginning that isn't in a chapter, internal links break. For
example, the follow document will get a bad internal link in EPUB (but
not Latex or HTML):
% Test Book
% Test Author
Here is the forward.
# Chapter 1
I am chapter 1.
# Chapter 2
[See Chapter 1](#chapter-1)
I've also attached two files to demostrate in case this isn't clear
enough. Anyway, to fix in my case, I just made a chapter for the
forward material. When I generate the latex, I have a preprocess step
that removes that chapter.
Best regards,
David.
--
Blog: http://www.linguatrek.com
Product: http://www.bibliobird.com
next prev parent reply other threads:[~2012-05-07 22:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 21:09 David Snopek
2012-04-28 10:21 ` niczero
2012-04-28 15:03 ` John MacFarlane
[not found] ` <20120428150316.GA405-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org>
2012-04-29 13:49 ` niczero
2012-04-29 16:31 ` John MacFarlane
[not found] ` <20120429163127.GC24897-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org>
2012-04-29 21:18 ` niczero
2012-04-29 21:37 ` John MacFarlane
2012-05-07 22:13 ` David Snopek [this message]
2012-10-26 5:16 ` Jason Morrison
[not found] ` <8cc0d96a-d364-4f03-a7bb-3b0b558fa857-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2012-10-26 6:17 ` fiddlosopher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADca9RdSo1NdMDsFDGhEC-YejS4pcgKQNOr2DpvVL_TWS9P15Q@mail.gmail.com \
--to=dsnopek-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).