public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@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 12:48:52 +0100	[thread overview]
Message-ID: <20170106114852.GH791@Administrateurs-iMac-3.local> (raw)
In-Reply-To: <CAKw7uViJOSH3rkjaqMTrbWJsN6Lf_m9H1DjcrxjuqpKEJ6Pzmw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Note that things pandoc stumbles on are not necessary tex
errors.  They may reflect limitations in pandoc's ability to
understand tex.

I've made the tex reader fail when it gets confused, rather
than (e.g.) silently skipping things, partly so that it can
be improved more rapidly.

In pandoc 2.0 we'll have better warnings about places where
information is lost, and perhaps we could add options to
"plow ahead" when pandoc gets confused.

+++ Václav Haisman [Jan 06 17 11:17 ]:
>   On 6 January 2017 at 03:30, Grady D <[1]gsmail4231-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 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: [2]https://hastebin.com/raw/womufuxoko
>
>   ​Well, you will have to fix the math sooner or later anyway, if you
>   want to make any sense out of it. Why not try and fix it before the
>   conversion?
>   --
>   VH
>
>   --
>   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 [3]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To post to this group, send email to
>   [4]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To view this discussion on the web visit
>   [5]https://groups.google.com/d/msgid/pandoc-discuss/CAKw7uViJOSH3rkjaqM
>   TrbWJsN6Lf_m9H1DjcrxjuqpKEJ6Pzmw%40mail.gmail.com.
>   For more options, visit [6]https://groups.google.com/d/optout.
>
>References
>
>   1. mailto:gsmail4231-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
>   2. https://hastebin.com/raw/womufuxoko
>   3. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   4. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   5. https://groups.google.com/d/msgid/pandoc-discuss/CAKw7uViJOSH3rkjaqMTrbWJsN6Lf_m9H1DjcrxjuqpKEJ6Pzmw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org?utm_medium=email&utm_source=footer
>   6. 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/20170106114852.GH791%40Administrateurs-iMac-3.local.
For more options, visit https://groups.google.com/d/optout.


  parent reply	other threads:[~2017-01-06 11: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 [this message]
     [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
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=20170106114852.GH791@Administrateurs-iMac-3.local \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@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).