public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: A A <amine.aboufirass-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Setting absolute values for table columns in markdown
Date: Fri, 15 Jul 2022 15:00:11 +0200	[thread overview]
Message-ID: <CAMwawgMFeK-xkEV4iVZGxh9JMUiR4LXnowQ7fRz4FFSmmhNcGw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1183 bytes --]

Dear All,

I'm trying to write a markdown to LaTeX writer using panflute. In pandoc,
the table column widths are defined as a "ratio" of the total text width
(72) in pandoc. Each column gets a value from 0 to 1 representing the
fraction of the total text width that that column should take.

This might work well for formats like HTML, but for my LaTeX writer I'd
much rather specify absolute values for the column widths and have pandoc
ignore how wide they are in the markdown source.

Can we provide attribute-like qualities to table columns in markdown? It
would seem quite counterintuitive to have to define the absolute value of
my LaTeX table columns as a *function* of the textwidth and the width of
the column in the markdown source.

Regards,

Amine

-- 
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/CAMwawgMFeK-xkEV4iVZGxh9JMUiR4LXnowQ7fRz4FFSmmhNcGw%40mail.gmail.com.

[-- Attachment #2: Type: text/html, Size: 1643 bytes --]

                 reply	other threads:[~2022-07-15 13:00 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=CAMwawgMFeK-xkEV4iVZGxh9JMUiR4LXnowQ7fRz4FFSmmhNcGw@mail.gmail.com \
    --to=amine.aboufirass-re5jqeeqqe8avxtiumwx3w@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).