public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: 'Madhukar Vissapragada' via pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>,
	pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Issue with nested tables and pandoc 65 error
Date: Wed, 19 May 2021 16:39:36 -0700	[thread overview]
Message-ID: <m2tumyguo7.fsf@MacBook-Pro.hsd1.ca.comcast.net> (raw)
In-Reply-To: <71c9115f-6e6d-423d-9ae7-40a121d92fabn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

This works fine with the latest version.

"'Madhukar Vissapragada' via pandoc-discuss"
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> writes:

> Hi Folks, 
> I am using pandoc version 2.10.1 for converting the tex into docx. While 
> trying to convert one of tex which has nested tables pandoc started 
> throwing a *pandoc 65 error stating that*  *it's expecting \end{table} but 
> it got \end{tabular}. *
>
> Here is the element for reference:
>
> \begin{table}[!h]
> \small
> \caption{Some fails.}
> \label{table:failedML}
> \begin{tabular}{llll}
> \hline
> & \textbf{hear}   \textbf{fail}                                       & 
> \textbf{Flex fail}   \textbf{content}                                       
> & \textbf{Flexible failure}\\   
> \textbf{newcontent}                                \\ \hline
> \textbf{Expectation} \\ \textbf{mean} \\ \textbf{deviation} &   If you need 
> to convert files from one markup format into another, pandoc is your 
> swiss-army knife. Pandoc can convert between the following format  \\
> \hline
> \end{tabular}
> \end{table}
>
> Any kind of suggestion or help is really appreciated
>
> Thanks in advance!!!
>
> -- 
> 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/71c9115f-6e6d-423d-9ae7-40a121d92fabn%40googlegroups.com.


  parent reply	other threads:[~2021-05-19 23:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-19 22:04 'Madhukar Vissapragada' via pandoc-discuss
     [not found] ` <71c9115f-6e6d-423d-9ae7-40a121d92fabn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-05-19 23:39   ` John MacFarlane [this message]
     [not found]     ` <m2tumyguo7.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2021-05-20  5:38       ` 'Madhukar Vissapragada' via pandoc-discuss

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=m2tumyguo7.fsf@MacBook-Pro.hsd1.ca.comcast.net \
    --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).