From: BP Jonsson <bpj-J3H7GcXPSITLoDKTGw+V6w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Internal References in MarkDown
Date: Mon, 16 Jun 2014 17:39:55 +0200 [thread overview]
Message-ID: <539F0FCB.8090307@gmail.com> (raw)
In-Reply-To: <CAKGY2Pkyw=p8akPnNq7A4HjYQegg7-Hy=VH6FnoAwWY3mn8GWg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-06-16 17:13, Wagner Macedo skrev:
> Using <span id="name-of-label"></span> worked for me for both html and latex
It does, if you use a new enough version of pandoc.
In too old versions neither <span> nor <div> work at all with
anything but HTML, because then pandoc saw them just as
raw HTML. Recent versions parse them, the LaTeX writer sees them
and inserts a `\label`.
>
> --
> Wagner Macedo
>
>
> On 16 June 2014 07:36, Sebastian Humenda <shumenda-Mmb7MZpHnFY@public.gmane.org> wrote:
>
>> Hello,
>>
>> I am trying to reference internal labels within a MarkDown document. I
>> thought
>> the following might work:
>>
>> Please click [here][link]
>>
>> [link]: Some other text.
>>
>> Does this only work for referencing external links? It also seems that
>> Pandoc
>> ``eats'' paragraphs ust containing [xxx]:. Even the JSon output doesn't
>> show
>> this text. I have tried to implement a pandoc filter myself to add this
>> feature.
>>
>> Thanks
>> Sebastian
>> --
>> Web: http://www.crustulus.de | Blog:
>> http://www.crustulus.de/cgi-bin/blog.cgi?de-0
>> Freies Latein-Deutsch-Wörterbuch: http://www.crustulus.de/freedict.de.html
>> FreeDict: Free multilingual dictionary databases - http://www.freedict.org
>>
>
--
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/539F0FCB.8090307%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2014-06-16 15:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 10:36 Sebastian Humenda
2014-06-16 12:16 ` Wagner Macedo
[not found] ` <CAKGY2P=_trQqo3Hjv4fkwBOLmh9ekVKVOgGLQoaz8yLySzsLEg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-06-16 13:22 ` Sebastian Humenda
2014-06-16 13:38 ` Wagner Macedo
2014-06-16 13:50 ` BP Jonsson
[not found] ` <539EF63D.5030001-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-06-16 14:08 ` Wagner Macedo
2014-06-16 14:36 ` Sebastian Humenda
2014-06-16 15:13 ` Wagner Macedo
[not found] ` <CAKGY2Pkyw=p8akPnNq7A4HjYQegg7-Hy=VH6FnoAwWY3mn8GWg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-06-16 15:39 ` BP Jonsson [this message]
[not found] ` <539F0FCB.8090307-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-06-18 16:58 ` Sebastian Humenda
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=539F0FCB.8090307@gmail.com \
--to=bpj-j3h7gcxpsitlodktgw+v6w@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).