public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Joseph Reagle
	<joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>,
	pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Remind me about table widths again...
Date: Thu, 09 Dec 2021 21:44:59 -0800	[thread overview]
Message-ID: <m2h7bh3tes.fsf@Johns-Air.hsd1.ca.comcast.net> (raw)
In-Reply-To: <05eb0d12-eff1-7f4b-7a7a-d9da8a3d2f33-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>

Joseph Reagle <joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org> writes:

> At the top of my syllabi I've long had a big chunk of ugly HTML (with spans) for course info and office hours.
>
> I've finally mocked up a nicer markdown grid table that manages without spans.
>
> https://reagle.org/joseph/2021/cda/cda-syllabus-FA.md
>
> However, I wonder why the table and column widths are hard-coded, and not left to be no more than what's necessary?

Browsers know how to figure out good widths, but that's not
true for many of the formats pandoc supports (e.g. LateX).
So we parse the table with width information.  Yes, grid
tables always have them -- anything that can accept block-level
content that needs to wrap has to have a width.


      parent reply	other threads:[~2021-12-10  5:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-09 23:10 Joseph Reagle
     [not found] ` <05eb0d12-eff1-7f4b-7a7a-d9da8a3d2f33-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2021-12-10  5:44   ` John MacFarlane [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=m2h7bh3tes.fsf@Johns-Air.hsd1.ca.comcast.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=joseph.2011-T1oY19WcHSwdnm+yROfE0A@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).