From: BPJ <melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Mixed zero and non-zero table column widths
Date: Tue, 6 Aug 2019 11:32:07 +0200 [thread overview]
Message-ID: <CADAJKhC5C0Jneasd5rBrB28Xn2cOviw+qNOfxQo3GT68M1sxuw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1503 bytes --]
I'm trying to build tables programmatically in a filter.
It seems as if all column widths are specified as 0.0 Pandoc will calculate
optimal column widths based on the length of cell contents and the
available space. Is this correct?
It also seems that if a column width is an explicit non-zero float Pandoc
will set the width of that column as specified so that the width of the
column is the available space multiplied by the specified float, such that
if the float is e.g. 0.4 the width of the column is 40% of the available
width and if the sum of the specified widths is greater than 1 the table
will be wider than the available width. Is this correct?
Is the above behavior, assuming I have understood it correctly, implemented
in Pandoc or in LaTeX?
What happens, specifically to the columns for which a zero value is
specified, if some of the specified column widths are zero and some are
non-zero? I guess that the available space if any remains after subtracting
the non-zero widths is distributed among the zero-width columns, or do they
become truly zero-width?
--
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/CADAJKhC5C0Jneasd5rBrB28Xn2cOviw%2BqNOfxQo3GT68M1sxuw%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 2038 bytes --]
next reply other threads:[~2019-08-06 9:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 9:32 BPJ [this message]
[not found] ` <CADAJKhC5C0Jneasd5rBrB28Xn2cOviw+qNOfxQo3GT68M1sxuw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-08-06 17:31 ` John MacFarlane
[not found] ` <yh480k8ss6w68u.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-08-06 19:05 ` BPJ
[not found] ` <CADAJKhCAnGbkC3EO_CxD9owf-MJ8q4HwhbucY-vshBTBh04zqw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-08-08 9:22 ` 山本一貴
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=CADAJKhC5C0Jneasd5rBrB28Xn2cOviw+qNOfxQo3GT68M1sxuw@mail.gmail.com \
--to=melroch-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).