public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Abhishek Ulayil <abhiman2000-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Extend functionality of existing LaTeX reader
Date: Sun, 17 Jul 2022 07:06:12 -0700 (PDT)	[thread overview]
Message-ID: <0355c120-5f0c-440e-8bdf-bdf819fd1f4cn@googlegroups.com> (raw)


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

Hi everyone,
 I have been using pandoc, learning about the AST and writing basic Lua 
filters (Mostly for LaTeX).
While it has been a learning experience for me I have started to wonder 
"Can we write a custom reader to extend the functionality of the existing 
reader?
and If such a mechanism already exists then how to go about it?"

I understand that the default LaTeX reader is good enough for most 
conversions, But there are many custom commands and environments that the 
pandoc LaTeX reader skips(or treats as Div) in AST.

I have also explored the latex+raw_tex input format where I could write 
some Lua filters but this format is overkill, considering I want to add 
support for only a few commands/environments and want the default reader to 
handle the rest.

Thanks in advance,
Abhishek U.

-- 
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/0355c120-5f0c-440e-8bdf-bdf819fd1f4cn%40googlegroups.com.

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

                 reply	other threads:[~2022-07-17 14:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=0355c120-5f0c-440e-8bdf-bdf819fd1f4cn@googlegroups.com \
    --to=abhiman2000-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).