From: jcr <ffi.appdev-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Suggestion: option to use table floats or longtable in LaTeX output
Date: Thu, 21 Sep 2023 08:23:31 -0700 (PDT) [thread overview]
Message-ID: <08b1186b-28c7-4dd4-9014-794666e8f819n@googlegroups.com> (raw)
In-Reply-To: <b2f7f1b5-c1ba-433c-aaa3-49feeceea822n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1494 bytes --]
I would welcome an option to avoid longtable. I'm working on a book that
will include some tables and I need them to be floats. If I don't have an
easier solution, I may try to use a script to convert the tables to raw
LaTeX and then modify the string with regular expressions to turn it into
some variant of tabular.
On Tuesday, September 19, 2023 at 3:29:14 AM UTC-4 pandoc-discuss wrote:
> Table floats with tabular material vs longtable has been discussed before
> and there doesn't seem to be a solution that satisfies all users. Would it
> be possible to make different table styles configurable with pandoc? An
> option like:
>
> tables=longtable|table
>
> would be much appreciated.
>
> If possible, I'd also like to propose a third option, maybe called
> "plaintable" or "plaintabular" or something, that also disables pandoc's
> control of table widths with minipages. Some users (like me) would like
> plain tables and solve too wide tables in other ways (like redefining the
> table environment to set a different font size).
>
--
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/08b1186b-28c7-4dd4-9014-794666e8f819n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2038 bytes --]
prev parent reply other threads:[~2023-09-21 15:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 7:29 pandoc-discuss
[not found] ` <b2f7f1b5-c1ba-433c-aaa3-49feeceea822n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-09-21 15:23 ` jcr [this message]
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=08b1186b-28c7-4dd4-9014-794666e8f819n@googlegroups.com \
--to=ffi.appdev-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).