public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Andreas Scherer <andreas_scherer-KuiJ5kEpwI6ELgA04lAiVw@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: [LaTeX] Problem with Links in headers
Date: Tue, 03 Sep 2019 10:43:57 +0200	[thread overview]
Message-ID: <906b7dd2fdd045c00a777d5492d3aa2f@email.freenet.de> (raw)

Finally, I was able to rearrange the full MD document to compile it successfully into PDF and HTML. Moving all '#' sectioning commands one level up seems to satisfy pdflatex. Maybe the 'paragraph' level was too deep (although there were more such items, none followed by 'text').

The final result is in this gist: https://gist.github.com/ascherer/b10e9680436f61bb776adef2c0c353f7
Thanks. Case closed.








-- 
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/906b7dd2fdd045c00a777d5492d3aa2f%40email.freenet.de.


             reply	other threads:[~2019-09-03  8:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-03  8:43 Andreas Scherer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-09-01 13:16 Andreas Scherer
     [not found] ` <9600a513-8196-4747-953f-70ada224a688-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-09-02  3:52   ` John MacFarlane
     [not found]     ` <m28sr7cq31.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-09-02 17:13       ` Andreas Scherer

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=906b7dd2fdd045c00a777d5492d3aa2f@email.freenet.de \
    --to=andreas_scherer-kuij5kepwi6elga04laivw@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).