From: Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Project ideas for Haskell Summer of Code 2023
Date: Wed, 22 Mar 2023 18:08:59 +0100 [thread overview]
Message-ID: <871qlg66up.fsf@zeitkraut.de> (raw)
In-Reply-To: <e23134bf-ebad-44e1-8c5f-c833eeb434c3n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Hi!
"bkle...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <bkleung89-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> The Haskell Foundation is sponsoring a SoC program (https://
> github.com/haskell-org/summer-of-haskell/pull/167).
>
> There is a task list for Pandoc (https://github.com/jgm/pandoc/issues
> /1852), but many of those tasks have been completed. Is there an
> updated list of tasks somewhere?
We don't have a list right now. Here are two ideas:
- Compile an in-browser version of pandoc: There is
<https://markup.rocks>, but it is outdated and hasn't been updated for
years. We have restructured pandoc's modules to make it easier to
build it without Lua, which removes the biggest non-Haskell
dependency. The other big one is libyaml, as a pure Haskell library
wasn't fast enough. Fixing performance issues in Haskell's YAML
parsing, building it into pandoc and providing an in-browser version
of pandoc would be huge.
- Improved support for OOXML: to be honest though, this is less about
Haskell and more about reading the Office Open XML specs.
--
Albert Krewinkel
GPG: 8eed e3e2 e8c5 6f18 81fe e836 388d c0b2 1f63 1124
prev parent reply other threads:[~2023-03-22 17:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 15:35 bkle...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
[not found] ` <e23134bf-ebad-44e1-8c5f-c833eeb434c3n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-03-22 17:08 ` Albert Krewinkel [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=871qlg66up.fsf@zeitkraut.de \
--to=albert+pandoc-9eawchwdxg8hfhg+jk9f0w@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).