From: SGEng <simon-english-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: .TeX in - .Docx Out with glossaries package
Date: Mon, 6 Mar 2023 13:55:12 -0800 (PST) [thread overview]
Message-ID: <a75610fd-e7e1-44e5-b319-965ec45f5a20n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2417 bytes --]
Hello pandoc-users,
I frequently use the LaTeX-reader-to-docx-writer workflow to facilitate
cross-platform collaborations with colleagues. I have recently started
using the glossaries package in LaTeX but as others have noted (see ref
discussions), the Pandoc LaTeX reader doesn’t process the various
glossaries commands. I confess to not having fully understood all of the
suggestions in the linked discussions but I believe they don’t apply to my
case because the workflow I am trying to achieve is input.tex to
output.docx (not using markdown etc).
I’ve looked into using a lua-filter to replace text in the document but
haven’t managed to get one working. That said, I am unfamiliar with both
Lua syntax and Haskell so my attempts were rudimentary at best.
I have two questions:
Can anyone comment on the advantages and disadvantages of the two
approaches to achieving the .tex in- .docx out workflow:
1. Writing a Lua-filter or 2. Amending Pandoc’s LaTeX reader to natively
interpret glossaries commands and render them correctly
Secondly, I use this program frequently and would find adding this feature
valuable but don’t have the skills to achieve it myself. Furthermore, I
have had some difficulty finding programers familiar with
Pandoc/haskell/lua/LaTeX. Can anyone suggest where I might find a
programmer capable of adding this feature to pandoc or recommend anyone
specific who could be available for this job?
Finally, I would be eager to get native interpretation for the recent
tabularray package tables in LaTeX, but that is of slightly lower priority
for me. Also, if I have completely missed some pre-existing solution to my
problem, I would be very glad to learn of it!
Refs
https://groups.google.com/g/pandoc-discuss/c/Bz1cG55BKjM/m/wnzyas2eDwAJ
https://groups.google.com/g/pandoc-discuss/c/U_zeSUrwAHY/m/cvO2LlRxAwAJ
https://groups.google.com/g/pandoc-discuss/c/lErdcsL6Dj4/m/g2Ps-tfYAgAJ
Best,
Simon
--
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/a75610fd-e7e1-44e5-b319-965ec45f5a20n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2776 bytes --]
reply other threads:[~2023-03-06 21:55 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=a75610fd-e7e1-44e5-b319-965ec45f5a20n@googlegroups.com \
--to=simon-english-pkbjnfxxiarbdgjk7y7tuq@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).