From: Jeremy Conlin <jlconlin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Approach to converting large, custom, LaTeX document to restructured text
Date: Thu, 10 Sep 2020 14:43:56 -0700 (PDT) [thread overview]
Message-ID: <9c40cd2c-9874-446b-8772-c8a99e377acan@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1520 bytes --]
I have a large (900 page) LaTeX document (broken up into several LaTeX
files) that I want to convert into restructured text. I've already tried to
use pandoc to convert some of the files and it has failed for a few
reasons.
I'm a new pandoc user, but I figure I'm going to have to write my own
converter. Before I do, I wanted to ask this forum what the right way to
approach the conversion. I was planning on reading everything into Python,
do my own search/replace and then pass the result on to pandoc. I would
then rinse/repeat until I have everything the way I want it.
I know there are filters and such that I can write to customize things, but
(as a beginner) I'm not sure if it would be easier to learn pandoc syntax
and write my own filter, or just go at it in Python as I described above.
I don't mind doing it either way; I think it might be a fun side project to
do when I'm procrastinating doing what I really should be doing.
Please advise on what is the right approach. I'm sure there are other
approaches too that I'm not aware of. I'm open for suggestions.
Thanks,
Jeremy
--
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/9c40cd2c-9874-446b-8772-c8a99e377acan%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1959 bytes --]
next reply other threads:[~2020-09-10 21:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 21:43 Jeremy Conlin [this message]
[not found] ` <9c40cd2c-9874-446b-8772-c8a99e377acan-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-09-11 0:50 ` John MacFarlane
[not found] ` <m27dt1qgqk.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2020-09-11 13:31 ` Jeremy Conlin
[not found] ` <d8e598ff-e975-420d-baee-523f9ab38e35n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-09-11 15:07 ` 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=9c40cd2c-9874-446b-8772-c8a99e377acan@googlegroups.com \
--to=jlconlin-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).