From: Rory Byrne <rory-v7nxjtxOdhc@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: How can I process custom LaTeX commands?
Date: Tue, 31 Aug 2021 03:16:05 -0700 (PDT) [thread overview]
Message-ID: <bce57945-4313-4da1-a12f-8c290c709c94n@googlegroups.com> (raw)
In-Reply-To: <f238e164-9c72-4d27-a9c7-aae0222cc031n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1454 bytes --]
I've found that I can use `+raw_tex` which at least allows me to manually
process the custom commands:
`pandoc -f latex+raw_tex -F filter.py -t native test.tex`
```
#!/usr/bin/env python
from pandocfilters import Para, Str, toJSONFilter
def foo(key, value, format, meta):
if key == 'RawBlock':
return Para([Str(value[1])])
if __name__ == "__main__":
toJSONFilter(foo)
```
If there's any other approach to this kind of thing then I'd love to hear
it!
On Tuesday, 31 August 2021 at 08:39:04 UTC+1 Rory Byrne wrote:
> Hi friends,
>
> I am building a LaTeX package which adds some new annotation commands for
> semantics, like `\argument{...}` or `\conclusion{...}`. I'm brand new to
> Pandoc, but I would like to parse a LaTeX file containing these commands
> into JSON output.
>
> I was thinking that I could write a Pandoc filter which would process
> those commands, but that doesn't seem possible.
>
> Is there a way to use Pandoc to process a LaTeX file containing custom
> commands?
>
> Thanks,
> Rory
>
--
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/bce57945-4313-4da1-a12f-8c290c709c94n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2331 bytes --]
next prev parent reply other threads:[~2021-08-31 10:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 7:39 Rory Byrne
[not found] ` <f238e164-9c72-4d27-a9c7-aae0222cc031n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-08-31 10:16 ` Rory Byrne [this message]
2021-08-31 17:02 ` John MacFarlane
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=bce57945-4313-4da1-a12f-8c290c709c94n@googlegroups.com \
--to=rory-v7nxjtxodhc@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).