public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Alon Bar-Lev <alon.barlev-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: [markdown] links between documents
Date: Thu, 7 Feb 2019 08:26:57 +0200	[thread overview]
Message-ID: <CAOazyz2k3FYHaF4SjVX0agZDH=4ZSAKm6QYyTppVvaQymnbXJA@mail.gmail.com> (raw)
In-Reply-To: <CADAJKhCnRDa+CWqntyPrvqfpSmO+Zakb8hj==C0XxPzBNeBJZQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Thanks!
But then the markdown will not be able to process the files as separate files.
For example, I use markdown generation online on top of git, so
references should be between files and expose this to users. But when
I create a PDF or HTML out of all the files using pandoc, I expect the
generation to be aware of the files it reads and convert the links
that matches the files into inline references.

On Thu, Feb 7, 2019 at 2:13 AM BPJ <melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> You want  `[this](#title-b)`
>
> Den ons 6 feb. 2019 22:01 skrev Alon Bar-Lev <alon.barlev-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>:
>>
>> Hi All,
>>
>> I need to find a solution of generate markdown to pdf.
>> pandoc looks promising, however, I must be missing something.
>>
>> Let's take the following two files:
>>
>> a.md
>> ---
>> # Title A
>>
>> A content.
>>
>> See [this](b.md).
>> ---
>>
>> b.md
>> ---
>> # Title B
>>
>> B content.
>> ---
>>
>> Run:
>> $ pandoc -o a.html --reference-links a.md b.md
>> $ pandoc -o a.pdf --reference-links a.md b.md
>>
>> In both cases the link to B actually goes to the filesystem b.md
>> instead of being a reference to the content of B within the document.
>>
>> Can this be worked out somehow with parameters? I could not find
>> anything that made an impact.
>>
>> Thanks,
>> Alon
>>
>> --
>> 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/CAOazyz04jcRfqkGEkpb2FcBmjVJ7C%3D7cvSf-Tm1wKBWeCKEuoQ%40mail.gmail.com.
>> For more options, visit https://groups.google.com/d/optout.
>
> --
> 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/CADAJKhCnRDa%2BCWqntyPrvqfpSmO%2BZakb8hj%3D%3DC0XxPzBNeBJZQ%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.


  parent reply	other threads:[~2019-02-07  6:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-06 21:00 Alon Bar-Lev
     [not found] ` <CAOazyz04jcRfqkGEkpb2FcBmjVJ7C=7cvSf-Tm1wKBWeCKEuoQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-02-07  0:13   ` BPJ
     [not found]     ` <CADAJKhCnRDa+CWqntyPrvqfpSmO+Zakb8hj==C0XxPzBNeBJZQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-02-07  6:26       ` Alon Bar-Lev [this message]
     [not found]         ` <CAOazyz2k3FYHaF4SjVX0agZDH=4ZSAKm6QYyTppVvaQymnbXJA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-02-07 20:18           ` BP Jonsson
     [not found]             ` <a2366d6c-8f01-2119-1c93-30404f689d25-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-02-08 16:35               ` Alon Bar-Lev

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='CAOazyz2k3FYHaF4SjVX0agZDH=4ZSAKm6QYyTppVvaQymnbXJA@mail.gmail.com' \
    --to=alon.barlev-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).