From: andy <aborruso-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: docx output: how to set tables columns width, starting with pipe table?
Date: Sat, 1 Jul 2023 09:23:21 +0200 [thread overview]
Message-ID: <CAHEdGZNWx23eBW17o6R=vDKnzMkzA8uesM=G6otdinGqAEQh-Q@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1143 bytes --]
Hi,
I have this sample input md file
| Question | Reply | Note |
| ----- | --- | -- |
|Magna sint duis proident do. Laboris Lorem exercitation consectetur
quis|Magna sint duis proident do. Laboris Lorem exercitation
consectetur quis|Magna sint duis proident do. Laboris Lorem
exercitation consectetur quis|
In the documentation I read that the relative cell widths are determined by
the number of dashes in the line separating the table header from the table
body.
I have | ----- | --- | -- |, than it should be 50%, 30% and 20%, but I have
a 33, 33, 33 docx output.
The command I use is pandoc -s input.md -o output.docx and I’m using pandoc
2.9.2.1
Thank you
[image: image.png]
--
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/CAHEdGZNWx23eBW17o6R%3DvDKnzMkzA8uesM%3DG6otdinGqAEQh-Q%40mail.gmail.com.
[-- Attachment #1.2: Type: text/html, Size: 4994 bytes --]
[-- Attachment #2: image.png --]
[-- Type: image/png, Size: 7307 bytes --]
next reply other threads:[~2023-07-01 7:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-01 7:23 andy [this message]
[not found] ` <CAHEdGZNWx23eBW17o6R=vDKnzMkzA8uesM=G6otdinGqAEQh-Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-07-01 8:03 ` Andrea Borruso
2023-07-01 15:58 ` John MacFarlane
[not found] ` <266B2BB1-A4B1-416F-815A-DEE9EB4D2B11-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-07-01 16:09 ` andy
[not found] ` <CAHEdGZO0KafBKX2-OPNPPBP6oaJ18QDx31UM-GaxSCs2Y7Qprw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-07-01 16:26 ` John MacFarlane
[not found] ` <79613221-EDCB-4626-9EA7-563B66F73EC8-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-07-01 16:32 ` andy
[not found] ` <CAHEdGZOm9Ss2u_K-Sto2LAjc5dFWj47L_9vLT2oYMkcvEZ9Waw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-07-01 19:33 ` John MacFarlane
2023-07-01 19:51 ` John MacFarlane
[not found] ` <480DA686-525F-4E99-933C-DF82F266A6DC-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-07-01 20:05 ` John MacFarlane
[not found] ` <8BFA7781-9075-468C-A887-A62F138EF8F3-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-07-02 8:05 ` Andrea Borruso
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='CAHEdGZNWx23eBW17o6R=vDKnzMkzA8uesM=G6otdinGqAEQh-Q@mail.gmail.com' \
--to=aborruso-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).