public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Success story: Pandoc at NASA
Date: Sat, 7 Oct 2023 16:15:08 -0700	[thread overview]
Message-ID: <6C8FD4DC-37A0-4A92-87E9-4DDC02DD1092@gmail.com> (raw)
In-Reply-To: <b4fcfa36-71f6-45a1-b7f0-63d344976fb4n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

When I was a kid I was obsessed with astronomy and space exploration, and naturally a gigantic fan of NASA. So it is gratifying to hear that pandoc contributes in some small way!

> On Oct 7, 2023, at 10:28 AM, Ivan Perez <ivanperezdominguez-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> 
> Hi,
> 
> I'm sure this is very little in comparison with all the successes of pandoc, but I wanted to let you know what we used pandoc at NASA to create the documentation needed so that the projects Copilot (https://github.com/Copilot-Language/copilot/) and Ogma (https://github.com/nasa/ogma) could be used in more critical software and in flights.
> 
> The documentation is written in Markdown and the converted to PDF via latex using pandoc. Using Markdown has made it much easier to keep a clean document and also to compare documents across projects to search for meaningful differences.
> 
> I used a custom template for this based on pandoc's standard template, with lots of fields in the header that need to go in the first pages of the document (they are like form fields). I'm also using % as a comment in pandoc to separate sentences to make documents easier to read, and I'm pre-filtering the file removing all lines matching '^%$'.
> 
> Also, these two papers:
> https://dl.acm.org/doi/10.1145/3609026.3609727
> https://dl.acm.org/doi/10.1145/3609025.3609475
> were written in pandoc. For those, I didn't use a custom template. Rather, I converted the core text of the paper to LaTeX with pandoc and then had a paper.tex file that imported the result.
> 
> I hope this is of interest to some people in the community.
> 
> Cheers,
> 
> Ivan
> 
> -- 
> 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/b4fcfa36-71f6-45a1-b7f0-63d344976fb4n%40googlegroups.com.

-- 
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/6C8FD4DC-37A0-4A92-87E9-4DDC02DD1092%40gmail.com.


      parent reply	other threads:[~2023-10-07 23:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-07 17:28 Ivan Perez
     [not found] ` <b4fcfa36-71f6-45a1-b7f0-63d344976fb4n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-10-07 17:32   ` Ivan Perez
2023-10-07 23:15   ` John MacFarlane [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=6C8FD4DC-37A0-4A92-87E9-4DDC02DD1092@gmail.com \
    --to=fiddlosopher-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).