public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Gary Glass <garyglassphotography-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: epub-chapter-level breaks internal links
Date: Tue, 29 Dec 2020 05:16:13 -0800 (PST)	[thread overview]
Message-ID: <fcb19fb0-39ef-4dc6-b830-593825cb421dn@googlegroups.com> (raw)
In-Reply-To: <80a1607f-2986-422e-a0c5-674e011c7414n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 1409 bytes --]

I figured it out. Don't use anchor tags. Instead:


### B

[]{ref1}Bar, Foo. What a mess!

### F

[]{ref2}Foo Bar. See [Bar, Foo](#ref1)


If this is in the docs I never found it. The downside to this is that the 
links don't work in a standard markdown editor. If Pandoc can handle this, 
it ought to handle using HTML anchors the same way. There's no need to 
require special formatting here.
On Monday, December 28, 2020 at 3:51:46 PM UTC+1 Gary Glass wrote:

> Here's the deal: I am converting markdown to epub. One of the markdown 
> files is pretty big, but it's broken up into various level-3. There are 
> many cross-ref links among the items on the page. e.g.:
>
> ### B
>
> <a id="ref1">Bar, Foo. What a mess!
>
> ### F
>
> <a id="ref2">Foo Bar. See [Bar, Foo](#ref1)
>
>
> But since the file is pretty big I use epub-chapter-level=3 to split it up 
> into small chunks in the epub output. But doing that breaks the cross-ref 
> links.
>
> What are my options for getting this to work?
>

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/fcb19fb0-39ef-4dc6-b830-593825cb421dn%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 2212 bytes --]

      parent reply	other threads:[~2020-12-29 13:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-28 14:51 Gary Glass
     [not found] ` <80a1607f-2986-422e-a0c5-674e011c7414n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-12-29 13:16   ` Gary Glass [this message]

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=fcb19fb0-39ef-4dc6-b830-593825cb421dn@googlegroups.com \
    --to=garyglassphotography-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).