From: Damien Thiriet <damien@thiriet.web4me.fr>
To: ntg-context@ntg.nl
Subject: xtable and natural tables
Date: Tue, 19 Feb 2019 20:52:24 +0100 [thread overview]
Message-ID: <20190219195223.GA15488@valencay.home> (raw)
Hi list,
From Hans xtable manual:
As each cell is basically a \framed and as we need to do two passes over
the table, this mechanism is not
the fastest but it is some two times faster than the natural tables
mechanism, and in most cases can be used instead.
Manuals examples are of course short ones, but I understand this
mechanism is faster even on tables that do not expand on more than one
page.
Does this mean, that extreme tables should now be considered as the
recommended way to build tables?
Are there simple cases, when natural tables should be obviously
preferred?
Thanks,
Damien Thiriet
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
reply other threads:[~2019-02-19 19:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190219195223.GA15488@valencay.home \
--to=damien@thiriet.web4me.fr \
--cc=ntg-context@ntg.nl \
/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).