From: Tim Cross <email@example.com>
To: Matt Price <firstname.lastname@example.org>
Cc: Org Mode <email@example.com>
Subject: Re: convert subtree or nested list to table
Date: Tue, 06 Jul 2021 15:10:16 +1000 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Nearly every day, I'm filled with joy because I no longer have to battle
brain dead LMS!
If your forced to use HTML tables, that is a pain - it will be like
stepping back to the turn of the century when we used tables as the
basic layout structure.
It may be worthwhile verifying what/which styling the system strips. I
battled with one system which stripped in-line 'style' attributes, but
it did allow CSS blocks in the header.
It probably isn't too hard to write a function which will generate your
subtree as a table. 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. The
complexity of your function will probably depend on how deeply your tree
goes and how much data is in each node.
Matt Price <email@example.com> writes:
> Thanks for the thoughts, Tim.
> My preference is generally to work in HTML, and in fact if I had a decent platform to work on I could just use a container class and grid or flex
> layouts, but the learning management system at my institution strips out most styling information when HTML is uploaded, so I will probably need a
> real table.
> I odn't think I could really handle doing this in latex. I am a terrible latex user!
> On Mon, Jul 5, 2021 at 9:27 PM Tim Cross <firstname.lastname@example.org> wrote:
> Matt Price <email@example.com> writes:
> > I have to write a number of text-heavy documents which need to be delivered as tables with wrapped paragraphs in most cells. Working
> directly in
> > table format is pretty arduous and uncomfortable. Has anyone ever written a function to accept a list or subtree as input and process it into
> a table?
> > If anyone has done something similar, I'd love some tips!
> No, have not done that. What formats do you need to export the documents
> I ask because if all you need to produce is Latex derived documents
> (i.e. PDF, ps etc) and you do plan to write a function yourself to do
> this, I would work backwards. Latex tables are not very good for your
> use case, but Latex can support what you want to do. Most of the Latex
> table packages are not terribly good at formatting tables containing
> paragraphs of data. They will typically require lots of hand tweaking to
> get the formatting looking right. Getting the right latex package to
> support what you need to do will make the function you will need to
> write a lot easier. Therefore, I would start with a search of the latex
> package archives to find the right package and then write an elisp
> function that generates a latex block which formats your subtree using
> that package. You probably want something which will format a table with
> minipage or similar environments in the cells.
> Tim Cross
next prev parent reply other threads:[~2021-07-06 5:20 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 [this message]
2021-07-06 11:00 ` Eric S Fraga
2021-07-06 11:49 ` Tim Cross
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
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 \
* 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).