From: Daniel Staal <DStaal-Jdbf3xiKgS8@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: ANN: pandoc 3.1.3
Date: Wed, 7 Jun 2023 13:29:00 -0400 [thread overview]
Message-ID: <d382e930-af0a-2fce-d5ca-72f2c3b4cbb4@usa.net> (raw)
In-Reply-To: <D834A676-67BE-4416-ADBD-B36E021DABE7-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Let us know when it can read mail. ;)
Daniel T. Staal
( <http://www.catb.org/jargon/html/Z/Zawinskis-Law.html> )
On 6/7/23 12:47 PM, John MacFarlane wrote:
> And, fun fact, pandoc can now be used as a calculator:
>
> % pandoc -f typst -t plain
> #(3 * calc.sin(90))
> 2.6819899908016733
>
>
>
>> On Jun 6, 2023, at 9:49 PM, John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>>
>> I'm pleased to announce the release of pandoc 3.1.3,
>> available in the usual places:
>>
>> Binary packages & changelog:
>> https://github.com/jgm/pandoc/releases/tag/3.1.3
>>
>> Source & API documentation:
>> http://hackage.haskell.org/package/pandoc-3.1.3
>>
>> The main new feature is a typst reader, which depends
>> on a new Haskell library for parsing and evaluating
>> typst expressions. (This turned out to be quite a project,
>> because typst is a fairly full-featured programming language
>> in its own right.) Typst support isn't perfect, but it
>> should be good enough now to be useful. Typst 0.4 is the
>> version supported.
>>
>> API change: new exposed module, Text.Pandoc.Readers.Typst.
>>
>> For other changes and bug fixes, see the changelog.
>>
>> Thanks to all who contributed, especially new contributors
>> Andreas Scherer, Charlotte Koch, Frank Seifferth, Matt Dodson,
>> Michael Stahl, Noah Malmed, Stephan Meijer, Toni Dietze,
>> perro tuerto, sdhoward, thron7, and wgevaert.
>>
>>
>
--
---------------------------------------------------------------
This email copyright the author. Unless otherwise noted, you
are expressly allowed to retransmit, quote, or otherwise use
the contents for non-commercial purposes. This copyright will
expire 5 years after the author's death, or in 30 years,
whichever is longer, unless such a period is in excess of
local copyright law.
---------------------------------------------------------------
next prev parent reply other threads:[~2023-06-07 17:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 4:49 John MacFarlane
[not found] ` <EA89EE02-8F6D-4C46-8012-2BD22A6BECF6-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-06-07 16:47 ` John MacFarlane
[not found] ` <D834A676-67BE-4416-ADBD-B36E021DABE7-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-06-07 17:29 ` Daniel Staal [this message]
2023-06-07 20:49 ` Václav Haisman
[not found] ` <b82c9871-69e1-21e7-dd6b-5e6181a8288e-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-06-07 20:50 ` Václav Haisman
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=d382e930-af0a-2fce-d5ca-72f2c3b4cbb4@usa.net \
--to=dstaal-jdbf3xikgs8@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).