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 <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Incorrect column widths / text off page, for table containing math
Date: Fri, 15 Jul 2022 03:58:19 -0700 (PDT)	[thread overview]
Message-ID: <20a1f4d9-5ac6-45f8-a0e0-90f57de08fd7n@googlegroups.com> (raw)
In-Reply-To: <m21r9tv8s5.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 3438 bytes --]

Hi John MacFarlane,

In the below thread you mention

> Note that in LaTeX tables widths must be specified; LaTeX doesn't 
calculate optimum column widths the way HTML does.

In that case would you care to explain how table widths are specified by 
pandoc when converting from markdown to LaTeX? Everything I've read on 
tables seems to suggest that pandoc attempts to compute the width itself. 
Is there any way to specify that or control it more explicitly?

Regards,

Amine

On Wednesday, May 26, 2021 at 5:01:52 PM UTC+2 John MacFarlane wrote:

>
> See the pandoc manual under pipe tables: 
>
> If a pipe table contains a row whose Markdown content is wider 
> than the column width (see --columns), then the table will take 
> up the full text width and the cell contents will wrap, with the 
> relative cell widths determined by the number of dashes in the 
> line separating the table header from the table body. (For 
> example ---|- would make the first column 3/4 and the second 
> column 1/4 of the full text width.) 
>
> Your table has 
>
> |:---|:---| 
>
> which says to make the columns equal-width. Try 
>
> |:-|:-----| 
>
> for example, to make the right-hand column 5 x the 
> width of the left-hand column. 
>
> Note that in LaTeX tables widths must be specified; 
> LaTeX doesn't calculate optimum column widths the way 
> HTML does. 
>
>
> rwijtvliet <rwijt...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes: 
>
> > Dear all, 
> > 
> > I posted this question elsewhere <
> https://github.com/jgm/pandoc/issues/7317> 
> > but was asked to ask again here, so here I am. 
> > 
> > This table 
> > 
> > 
> > | Profit-at-risk (gas) | | 
> > |:---|:---| 
> > |For modelling | $\Delta rmp_{par gas} = \underbrace{-qu_0 \cdot \Delta 
> > pu_L - (\Delta qo_L + \Delta qo_S) \cdot (pu_0 + \Delta pu_L - po_0) - 
> qu_L 
> > \cdot \Delta pu_S}_{\text{indirect}} \ \underbrace{- \Delta qo_S \cdot 
> > \Delta pu_S}_{\text{direct}}$ | 
> > | (idealised) | $\Delta rmp_{par gas} = \underbrace{- \Delta qo_S \cdot 
> > (pu_L - po_0)}_{\text{indirect}} \ \underbrace{-\Delta qo_S \cdot \Delta 
> > pu_S}_{\text{direct}}$ | 
> > 
> > 
> > is rendered to pdf like this: 
> > [image: 119658665-b5553c80-be2d-11eb-957a-ce4333d04f24.png] 
> > 
> > That can't be right. Is there something I did wrong, i.e. let me know if 
> > there is anything I can do to help in finding the bug. 
> > 
> > Here are my versions: 
> > 
> > pandoc.exe 2.13 
> > Compiled with pandoc-types 1.22, texmath 0.12.2, skylighting 0.10.5, 
> > citeproc 0.3.0.9, ipynb 0.1.0.1 
> > 
> > Many thanks and Best regards 
> > 
> > -- 
> > 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-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/pandoc-discuss/37b73eb8-97e8-4abb-84d3-76d6b0fffbb8n%40googlegroups.com. 
>
>

-- 
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/20a1f4d9-5ac6-45f8-a0e0-90f57de08fd7n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 5099 bytes --]

      parent reply	other threads:[~2022-07-15 10:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-26 14:44 rwijtvliet
     [not found] ` <37b73eb8-97e8-4abb-84d3-76d6b0fffbb8n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-05-26 15:01   ` John MacFarlane
     [not found]     ` <m21r9tv8s5.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2021-05-26 15:15       ` Ruud Wijtvliet
2022-07-15 10:58       ` A A [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=20a1f4d9-5ac6-45f8-a0e0-90f57de08fd7n@googlegroups.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).