emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: convert subtree or nested list to table
Date: Tue, 06 Jul 2021 21:49:08 +1000	[thread overview]
Message-ID: <87bl7fmzcg.fsf@gmail.com> (raw)
In-Reply-To: <875yxn9066.fsf@ucl.ac.uk>

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> On Tuesday,  6 Jul 2021 at 15:10, Tim Cross wrote:
>> One advantage working with HTML has over latex is
>> that you don't have to worry about lines and line breaks and can have
>> really long cell lines which will get wrapped in HTML rendering. 
> Minor point: in LaTeX, the standard tabular environment has "p{X}" for
> paragraph columns (as opposed to "l" and "r", say) where X is some size
> (e.g. 10cm) and each entry is formatted as paragraphs.  You don't have
> to worry about line breaks etc.  So quite easy really.

Yes, that is true. However, you have to decide before hand how wide you
want the columns to be (i.e. it won't auto scale based on other data).
Typically, you have to do some 'trial and error' to work out what width
to make each column and avoid overful parbox warnings etc. With HTML,
you just specify the number of columns and it will scale to fit to the
page (screen) width. So, HTML great for display, sucks for printing.
latex, great for printing, but sucks for display. Getting things right
for latex tables/tabular environments is much harder than for HTML. Then
again, HTML tables sort of suck as well - much more flexible to have div
elements which you can style using a good grid/flow layout scheme.

Tim Cross

  reply	other threads:[~2021-07-06 11:55 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-05 19:44 convert subtree or nested list to table Matt Price
2021-07-05 20:01 ` Juan Manuel Macías
     [not found]   ` <CAN_Dec8iqKS+3qvjkYvQxovegnEzqR_rra0Q-ZA9baPz1mXDAA@mail.gmail.com>
2021-07-06 12:56     ` Juan Manuel Macías
2021-07-07  6:18       ` Uwe Brauer
2021-07-07 18:27         ` Juan Manuel Macías
2021-07-07 18:44           ` Uwe Brauer
2021-07-07 21:16       ` Matt Price
2021-07-05 22:10 ` Tim Cross
2021-07-06  3:15   ` Matt Price
2021-07-06  5:10     ` Tim Cross
2021-07-06 11:00       ` Eric S Fraga
2021-07-06 11:49         ` Tim Cross [this message]
2021-07-06 11:50 ` Uwe Brauer
2021-07-07 21:17   ` Matt Price
2021-07-07 10:27 ` tbanelwebmin
2021-07-07 21:13   ` Matt Price
2021-07-08  9:27     ` tbanelwebmin
2021-07-08 12:22     ` Christian Moe
2021-07-20 15:11       ` Matt Price
2021-07-20 16:03         ` Nick Dokos
2021-07-20 17:03           ` Matt Price
2021-07-10 12:03 ` [a very different solution] (was: convert subtree or nested list to table) Uwe Brauer

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:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87bl7fmzcg.fsf@gmail.com \
    --to=theophilusx@gmail.com \
    --cc=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \


* 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.
Code repositories for project(s) associated with this public inbox


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 read-only IMAP folder(s) and NNTP newsgroup(s).