From: Nandakumar Chandrasekhar <navanitachora-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: What determines inter column space/separation?
Date: Sun, 16 Jan 2022 08:51:32 -0800 (PST) [thread overview]
Message-ID: <521e20c4-0fc8-4beb-a067-767a8e1fd339n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1888 bytes --]
Dear Folks,
I have a markdown file which I am converting to PDF using the lualatex
engine using the command:
pandoc --from markdown+pipe_tables --to latex --pdf-engine lualatex
--output inter-column-space.pdf inter-column-space.md
My markdown file is as follows:
---
title: "What determines the inter-column space/separation?"
papersize: a4
fontsize: 11pt
mainfont: Noto Serif
geometry:
- margin=25mm
header-includes:
- \usepackage[margins=raggedright]{floatrow}
- \let\toprule\relax
- \let\bottomrule\relax
---
| | |
|:--|:--|
| a |
1234567890123456789012345678901234567890123456789012345678901234567890 |
| | 70 characters in second column |
| | |
|:--|:--|
| a |
12345678901234567890123456789012345678901234567890123456789012345678901234567890
|
| | 80 characters in second column |
The behavior I am seeing is that as soon as the number of characters passes
80 characters in the second column the inter column spacing increases and
does not adhere to the margins specified in the YAML block.
Here is a link to the compiled PDF which clearly shows what I see:
https://www.dropbox.com/s/89z845hhy7dbnm4/inter-column-space.pdf?dl=0
Since I am using the same source to create a PDF and DOCX file I would like
to use the same table markup for both. I do not see this issue in the DOCX
version as I compile it with a reference doc.
I hope you may be able to provide me with a robust table solution.
Many thanks,
Nanda
--
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/521e20c4-0fc8-4beb-a067-767a8e1fd339n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2622 bytes --]
reply other threads:[~2022-01-16 16:51 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=521e20c4-0fc8-4beb-a067-767a8e1fd339n@googlegroups.com \
--to=navanitachora-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).