public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Joseph Reagle <joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: How is the grid table column width calculated in pandoc?
Date: Thu, 14 Jul 2022 12:46:35 -0400	[thread overview]
Message-ID: <d078b93d-b20e-0f01-efb3-b130200d1550@reagle.org> (raw)
In-Reply-To: <CAMwawgN+D-cNfRKXmigUjXXuTVgVSkpkeRrrTE0hVfwK4iFHXw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

It is estimated based on the width of the markdown table.

> In multiline tables, the table parser pays attention to the widths of the columns, and the writers try to reproduce these relative widths in the output. So, if you find that one of the columns is too narrow in the output, try widening it in the Markdown source.

I don't know if there's an exact way, but I nudge my columns wider, if needed, with comments:

```
::: {#infobox}

+-----------------------+--------------------------+------------------------+
|       COMM 1255       |                          |                        |
|       <2022-SP>       |       Office hours       |        Content         |
|     <!-- 31848 -->    |                          |                        |
+=======================+==========================+========================+
| TU/FR 9:50--11:30\    | *TU appointments         | * [Policies][qp]       |
| [Hayden 424][qm]\     | at 15:30+*\              | * [Assignments][qa]    |
|                       | Prof. Reagle,            | * [Rubric][qru]        |
|                       | <j.reagle>\              | * [Resources][qre]     |
|                       | Comm Studies,            | * [Schedule][qs]       |
| <!-- width ...... --> | <!-- width ........  --> | <!-- 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/d078b93d-b20e-0f01-efb3-b130200d1550%40reagle.org.


      parent reply	other threads:[~2022-07-14 16:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-14 15:40 A A
     [not found] ` <CAMwawgN+D-cNfRKXmigUjXXuTVgVSkpkeRrrTE0hVfwK4iFHXw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-07-14 16:46   ` Joseph Reagle [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=d078b93d-b20e-0f01-efb3-b130200d1550@reagle.org \
    --to=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).