public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Vin Cent <irakay17-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Latex source . \begin{enumerate} nested in \blockquote generates an error.
Date: Sun, 5 Sep 2021 22:26:12 -0700 (PDT)	[thread overview]
Message-ID: <e6a6d0fb-5d58-405c-9e72-68489c5f0d35n@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1377 bytes --]

Hi,

I have had quite some pain isolating this problem, because pandoc (v 
2.14.2) provides a quite obscure error. I had to run a number of 
dichotomies into my source.

Here is the isolated problem. This latex code does is not accepted by 
pandoc :
\begin{document}
\blockquote{Foo
    \begin{enumerate}
    \item First
    \item Second
    \end{enumerate}
}
\end{document}

Moreover, if this code is isolated into a \input{} file, the error raised 
by pandoc does not allow to find it easily. The error does not point to the 
\blockquote or even to the included document containing it. The error 
points to \begin{document} in the .tex "main" document.


Error at "epub.tex" (line 92, column 17):
unexpected ()
\begin{document}

I would consider this a (double?) bug, since my code is absolutely well 
compiled with pdflatex, for instance. Or maybe this is too naive an 
analysis (pandoc newb here).
I'd be happy to know about a workaround, too.

Cheers,

Vincent

-- 
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/e6a6d0fb-5d58-405c-9e72-68489c5f0d35n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 2678 bytes --]

                 reply	other threads:[~2021-09-06  5:26 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=e6a6d0fb-5d58-405c-9e72-68489c5f0d35n@googlegroups.com \
    --to=irakay17-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).