public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "'russurquhart1' via pandoc-discuss" <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Markdown w/Include files convert to PDF?
Date: Thu, 13 May 2021 08:35:31 -0700 (PDT)	[thread overview]
Message-ID: <aa45b5fd-283c-4138-b43e-41407f9e11f1n@googlegroups.com> (raw)


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

Hi,

I know standard Markdown has no provisions for a #include function. Our 
system, has added such a function, such that a line similar to:

# include path/to/file

includes that file at that point.

Will Pandoc. when converting Markdown files to PDF, be able to handle this? 
Or is there a way to have it handle this when generating PDF files?

Thanks,

Russ

-- 
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/aa45b5fd-283c-4138-b43e-41407f9e11f1n%40googlegroups.com.

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

             reply	other threads:[~2021-05-13 15:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-13 15:35 'russurquhart1' via pandoc-discuss [this message]
     [not found] ` <aa45b5fd-283c-4138-b43e-41407f9e11f1n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-05-13 22:18   ` John MacFarlane
     [not found]     ` <m21raa46rb.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2021-05-15  7:53       ` BPJ

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=aa45b5fd-283c-4138-b43e-41407f9e11f1n@googlegroups.com \
    --to=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).