From: erw1 <erwann.rogard-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: `xparse` instructions and `enumitem` formatting appear to be lost on `pandoc` (cross post)
Date: Wed, 12 May 2021 12:45:20 -0700 (PDT) [thread overview]
Message-ID: <28c205b8-5f80-4e79-bb56-3f96d2844c6dn@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1700 bytes --]
In cased this post at tex.stackechange
<https://tex.stackexchange.com/questions/596425/xparse-instructions-and-enumitem-formatting-appear-to-be-lost-on-pandoc>
was missed, cross-post:
`xparse` instructions and `enumitem` formatting appear to be lost on pandoc.
It's been pointed out conversion from LaTeX to TeX is not possible
<https://tex.stackexchange.com/questions/3174/latex-macro-expander>, so
what are the options?
```
\documentclass{article}
\usepackage{enumitem}
\usepackage{xparse}
\newlist{foo}{enumerate*}{1}
\setlist[foo]{label=\arabic*), itemjoin={{; }}}
\ExplSyntaxOn
\tl_set:Nn\g__erw_foo_tl{\item \textbf{a}\item b}
\NewDocumentCommand\Foo{}{\tl_use:N\g__erw_foo_tl}
\NewDocumentCommand\Bar{}{\item \textbf{c}\item d}
\def\Qux{\item \textbf{e}\item f}
\ExplSyntaxOff
\begin{document}
\begin{foo} \Foo\Bar\Qux \end{foo}
\end{document}
```
which produces:
[image: Screenshot from 2021-05-10 00-57-35.png]
Whereas,
```
$ pandoc -f latex -t plain jobname.tex
E
f
```
fails to render the "inline list" and `{{; }}` features. It's been
suggested to do :
```
make4ht LaTeX-292.tex && html2text jobname.html
```
but that comes at a price: `\textbf` ignored, and `Â` inserted at the
beginning of each item.
--
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/28c205b8-5f80-4e79-bb56-3f96d2844c6dn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 4489 bytes --]
[-- Attachment #2: Screenshot from 2021-05-10 00-57-35.png --]
[-- Type: image/png, Size: 3349 bytes --]
reply other threads:[~2021-05-12 19:45 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=28c205b8-5f80-4e79-bb56-3f96d2844c6dn@googlegroups.com \
--to=erwann.rogard-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).