public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: CS <cole.shaw-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Table conversion from LaTeX missing multirow strings?
Date: Thu, 18 Nov 2021 09:04:09 -0800 (PST)	[thread overview]
Message-ID: <e5e04026-8801-4ed2-8f95-713a98286c08n@googlegroups.com> (raw)


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


Hello, I am attempting to convert a LaTeX document into HTML, but running 
into issues with tables that use `\multirow`. From recent issues / PRs on 
the repo (https://github.com/jgm/pandoc/issues/6603, among others), it 
seems like this is  supported and should work. However, when I run pandoc, 
the multirow values seem to get stripped out. I am using pandoc 2.9.2.1 on 
Ubuntu 20.04, with texlive 2020.20210202-3 installed.

My minimal example is pulled from the GH issue mentioned above:

\documentclass{article}

\usepackage{multirow}

\begin{document}
\begin{tabular}{|r|r|}
\multirow{2}{5em}{hello} & A \\
& B \\
\end{tabular}
\end{document}

Converting this to native Haskell (for debugging), with the following 
command, results in:

$ pandoc table_test.tex -f latex -t native -o table_test.hs


[Table [] [AlignRight,AlignRight] [0.0,0.0]
[[]
,[]]
[[[]
,[Plain [Str "A"]]]
,[[]
,[Plain [Str "B"]]]]]


However, I would expect to see some rowspan declarations and at least the 
string "hello" somewhere in the output. Instead, I'm getting empty cells 
([]). The HTML version of the above is thus also missing the rowspan cell:

<table>
<tbody>
<tr class="odd">
<td style="text-align: right;"></td>
<td style="text-align: right;">A</td>
</tr>
<tr class="even">
<td style="text-align: right;"></td>
<td style="text-align: right;">B</td>
</tr>
</tbody>
</table>


Am I missing some command-line argument or use of an extension, to get 
multirow table cells to work? I've tried going through this discussion 
board and the documentation, but have not been able to find what I am 
missing. I am new to both LaTeX and pandoc, so perhaps I am missing 
something in the original document as well?

I appreciate your time and help. Thanks!

-- 
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/e5e04026-8801-4ed2-8f95-713a98286c08n%40googlegroups.com.

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

             reply	other threads:[~2021-11-18 17:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-18 17:04 CS [this message]
     [not found] ` <e5e04026-8801-4ed2-8f95-713a98286c08n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-11-18 21:43   ` Albert Krewinkel

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=e5e04026-8801-4ed2-8f95-713a98286c08n@googlegroups.com \
    --to=cole.shaw-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).