public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "E. Castedo Ellerman" <castedo-HtDYFTekaG5BDgjK7y7TUQ@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: New research document technology using Pandoc
Date: Sat, 4 Nov 2023 07:33:01 -0700 (PDT)	[thread overview]
Message-ID: <83c21ee1-e4cd-45bb-88f5-285c24a28e52n@googlegroups.com> (raw)


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

Some Pandoc users might be interested in this new technology that stands on 
the giant shoulders of Pandoc:

https://try.perm.pub/

As of release 3.1.9, Pandoc and the convenience authoring tool Baseprinter 
<https://try.perm.pub/baseprinter/> both output
Baseprint Document Format (BDF) <https://baseprints.singlesource.pub/bdf/>. 
To output BDF using only Pandoc (without Baseprinter),
visit https://try.perm.pub/pandoc.

Questions and feedback are welcome.

-- 
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/83c21ee1-e4cd-45bb-88f5-285c24a28e52n%40googlegroups.com.

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

             reply	other threads:[~2023-11-04 14:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-04 14:33 E. Castedo Ellerman [this message]
     [not found] ` <83c21ee1-e4cd-45bb-88f5-285c24a28e52n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-11-06  8:43   ` Guillaume Dehaene
     [not found]     ` <CAKOoOVV69XSKPTGAuXzZ5UVyLG=j0J_vUwMq5O9D69hLbo0rFg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-11-06 16:48       ` E. Castedo Ellerman

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=83c21ee1-e4cd-45bb-88f5-285c24a28e52n@googlegroups.com \
    --to=castedo-htdyftekag5bdgjk7y7tuq@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).