From: Richard Huntsinger <rhuntsinger-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: How to convert nested tables? | longtable vs tabular
Date: Tue, 19 Jul 2022 14:01:58 -0700 (PDT) [thread overview]
Message-ID: <f8c8c8fe-036e-41f0-a2cb-c744ca96176cn@googlegroups.com> (raw)
In-Reply-To: <a477931c-2479-47f4-9cf7-d5880a429a38n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1352 bytes --]
I found a filter on an old thread that attempts to produce tabular tables
rather than longtable tables, but as noted in the thread it does seem to
work for all of us:
https://groups.google.com/g/pandoc-discuss/c/RUC-tuu_qf0/m/h-H3RRVt1coJ
Perhaps someone can provide a new working lua filter to produce tabular
tables? MUCH appreciated.
On Tuesday, July 19, 2022 at 1:32:47 PM UTC-7 Richard Huntsinger wrote:
> I’ve successfully converted Jupyter HTML-format simple tables to
> LaTex-format tables using pandoc.read(raw.text, ‘html’).blocks in a lua
> filter. The resulting LaTex is \begin(longtable} … That’s okay for simple
> tables, but longtable does not support nested tables, which I do need.
>
> How to convert to LaTex tabular tables (which supports nested tables)
> rather than to longtable tables (which does not)? Or is there some other
> solution to converting nested tables?
>
--
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/f8c8c8fe-036e-41f0-a2cb-c744ca96176cn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1866 bytes --]
next prev parent reply other threads:[~2022-07-19 21:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 20:32 Richard Huntsinger
[not found] ` <a477931c-2479-47f4-9cf7-d5880a429a38n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-07-19 21:01 ` Richard Huntsinger [this message]
2022-07-20 21:36 ` BPJ
[not found] ` <CADAJKhDM2Q0S_fSQx3kpFg0kv4r2gYqR-rSHEE=CWhry37jM-A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-07-21 8:33 ` William Lupton
[not found] ` <CAEe_xxh5=xr8=N2BunXCihUHBFbsXUVaPQF4qwuLjq8jLqNsLg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-07-21 20:38 ` Richard Huntsinger
2022-07-21 20:47 ` Richard Huntsinger
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=f8c8c8fe-036e-41f0-a2cb-c744ca96176cn@googlegroups.com \
--to=rhuntsinger-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).