From: bapt a <auguieba-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: custom LaTeX writer example
Date: Wed, 16 Nov 2022 11:13:25 -0800 (PST) [thread overview]
Message-ID: <a327ba5a-21fe-4cae-85e5-4ce1c323154an@googlegroups.com> (raw)
In-Reply-To: <493DA04D-5B8D-4D3A-8A26-35A8A34E64AB-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 2598 bytes --]
Thanks – it does seem ideal; I wasn't sure from the description if one
could only include the targets to be replaced from an existing format, or
if everything had to be included to be a valid writer.
I think I'll start with a simpler case, because Tables seem too advanced
for my level of understanding.
Best,
baptiste
On Wednesday, 16 November 2022 at 08:48:07 UTC+13 fiddlosopher wrote:
> I'd recommend using a "new style" writer and just replacing the code that
> formats tables.
>
> https://pandoc.org/custom-writers.html#new-style
>
>
>
> > On Nov 14, 2022, at 7:30 PM, bapt a <augu...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> >
> > Hi,
> >
> > I'm hoping to play around with custom writers, to understand a bit
> better how to turn pandoc's AST into a specific output format (for example,
> I'd like to use tabularray syntax for tables in LaTeX, and it seems
> "cleaner" to use a writer than to inject raw inline LaTeX via a filter into
> the AST). The html writer example is quite useful, but since I'm aiming for
> LaTeX output, it would be helpful to have something a little closer in
> syntax as a starting point.
> >
> > I searched a bit and the closest thing I could find was a plain TeX
> writer at https://github.com/drehak/pandoc-to-markdown
> > but this is perhaps not as helpful for learning because most of the
> magic seems to be delegated to custom TeX macros. (A good strategy, but I
> wouldn't know (La)TeX well enough to perform some of the more complex
> processing)
> >
> > I wonder if someone here has a minimal (or complete!) example of a
> custom Lua writer for LaTeX they could share?
> >
> > Many thanks,
> >
> > baptiste
> >
> > --
> > 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-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> > To view this discussion on the web visit
> https://groups.google.com/d/msgid/pandoc-discuss/34e5e93b-8832-40d3-8803-8e5a12b5290an%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/a327ba5a-21fe-4cae-85e5-4ce1c323154an%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 4303 bytes --]
prev parent reply other threads:[~2022-11-16 19:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 3:30 bapt a
[not found] ` <34e5e93b-8832-40d3-8803-8e5a12b5290an-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-11-15 19:48 ` John MacFarlane
[not found] ` <493DA04D-5B8D-4D3A-8A26-35A8A34E64AB-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-11-16 19:13 ` bapt a [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=a327ba5a-21fe-4cae-85e5-4ce1c323154an@googlegroups.com \
--to=auguieba-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).