public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Grady D <gsmail4231-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Sugesstions for dealing with malformed LaTeX documents automatically?
Date: Fri, 6 Jan 2017 18:48:12 -0500	[thread overview]
Message-ID: <83a141c0-cddb-497b-a857-24c2bc4d51bd@Spark> (raw)
In-Reply-To: <caa79c5c-db77-497b-a1ed-c573bedbcf41-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 2453 bytes --]

I will check that out.

Thanks

On Jan 6, 2017, 9:17 AM -0500, 'Jason Seeley' via pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>, wrote:
> You might try DeTeX (or OpenDetex, which is easier to find). It strips all LaTeX commands, just leaving the text.
>
> (Old version with Windows executable here: https://code.google.com/archive/p/opendetex/
> Newer version, but source only, here: https://github.com/pkubowicz/opendetex )
>
> - Jason
>
> On Thursday, January 5, 2017 at 8:30:46 PM UTC-6, Grady D wrote:
> > I am trying to convert many LaTeX documents using Pandoc. However, some of the documents have syntax errors or are poorly formatted, and cause Pandoc to crash. Is there anything I could use, through Pandoc or otherwise, to make these documents usable/convertable? I intend to convert them to plaintext preserving only the content, so I do not need full blown syntax repair as much as I just need a way to eliminate malformed statements. At the bottom of this post, I have attached some of the errors I'm talking about.
> >
> > Thanks for any suggestions you guys have.
> >
> > Error examples: https://hastebin.com/raw/womufuxoko
> --
> You received this message because you are subscribed to a topic in the Google Groups "pandoc-discuss" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/pandoc-discuss/R_86WLQc1kc/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/caa79c5c-db77-497b-a1ed-c573bedbcf41%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/83a141c0-cddb-497b-a857-24c2bc4d51bd%40Spark.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #2: Type: text/html, Size: 4552 bytes --]

  parent reply	other threads:[~2017-01-06 23:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-06  2:30 Grady D
     [not found] ` <496e4ff7-b62a-47f8-8813-f699f56ae541-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-01-06 10:17   ` Václav Haisman
     [not found]     ` <CAKw7uViJOSH3rkjaqMTrbWJsN6Lf_m9H1DjcrxjuqpKEJ6Pzmw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-01-06 11:48       ` John MacFarlane
     [not found]         ` <20170106114852.GH791-BKjuZOBx5Kn2N3qrpRCZGbhGAdq7xJNKhPhL2mjWHbk@public.gmane.org>
2017-01-06 13:21           ` Grady D
2017-01-06 14:17   ` 'Jason Seeley' via pandoc-discuss
     [not found]     ` <caa79c5c-db77-497b-a1ed-c573bedbcf41-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-01-06 23:48       ` Grady D [this message]
2017-01-16 21:09         ` Grady D

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=83a141c0-cddb-497b-a857-24c2bc4d51bd@Spark \
    --to=gsmail4231-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).