From: "'Martin Ehlers' via pandoc-discuss" <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Pipe table content does not wrap in PDF
Date: Tue, 24 Oct 2023 01:07:42 -0700 (PDT) [thread overview]
Message-ID: <5e3c6aff-bc95-4b0d-8b5b-d9d46c28eeefn@googlegroups.com> (raw)
In-Reply-To: <1C6CF7A8-5918-4E83-9D09-14C6B40F38D3-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 2186 bytes --]
Yes, some lines are longer than the column width. This is the command I use
to create the PDF:
pandoc config_guide.md --wrap=auto --ascii --from=gfm+pipe_tables
--output=Config_Guide.pdf
I have also tried other wrap options. Please find a screenshot of one of
the truncated tables in the PDF attached.
Kind Regards
Martin
John MacFarlane schrieb am Montag, 23. Oktober 2023 um 18:14:18 UTC+2:
> Are any of the lines of your markdown pipe table longer than column width
> (e.g. 78 columns)? IF not, this feature doesn't kick in.
>
> > On Oct 23, 2023, at 6:17 AM, 'Martin Ehlers' via pandoc-discuss <
> pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> wrote:
> >
> > Hi All,
> >
> > According to the Pandoc User's Guide, for pipe tables, "if any line of
> the markdown source is longer than the column width, 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."
> >
> > However when I am converting markdown to PDF using LaTeX, content is not
> wrapped, and content exceeding the PDF page width is truncated instead. I
> have tried with different column and cell widths. Is this is a known issue,
> or do I miss something?
> >
> > Kind Regards
> > Martin
> >
> > --
> > 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/6d691fee-0237-4680-bfa1-ac220f46e116n%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/5e3c6aff-bc95-4b0d-8b5b-d9d46c28eeefn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 3295 bytes --]
[-- Attachment #2: pipe_table_truncated.jpg --]
[-- Type: image/jpeg, Size: 83930 bytes --]
next prev parent reply other threads:[~2023-10-24 8:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 13:17 'Martin Ehlers' via pandoc-discuss
[not found] ` <6d691fee-0237-4680-bfa1-ac220f46e116n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-10-23 16:14 ` John MacFarlane
[not found] ` <1C6CF7A8-5918-4E83-9D09-14C6B40F38D3-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-10-24 8:07 ` 'Martin Ehlers' via pandoc-discuss [this message]
2023-10-24 8:10 ` 'Martin Ehlers' via pandoc-discuss
[not found] ` <93d59e4d-d23e-4dca-ad50-80e970c7ba66n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-10-24 17:14 ` John MacFarlane
[not found] ` <B97BA90B-F9E0-4B1E-92EB-CCEDBF4FFD1A-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-10-25 16:23 ` 'Martin Ehlers' via pandoc-discuss
[not found] ` <a7dd3efe-aa22-4536-90a6-6ccadf314573n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-10-25 16:36 ` John MacFarlane
[not found] ` <5E4C2B79-FE4D-4D8E-9422-7C15DD5D1F63-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-10-26 14:03 ` 'Martin Ehlers' via pandoc-discuss
2023-10-24 8:15 ` 'Martin Ehlers' via pandoc-discuss
2023-10-24 8:21 'Ehlers, Martin (EXT)' via pandoc-discuss
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=5e3c6aff-bc95-4b0d-8b5b-d9d46c28eeefn@googlegroups.com \
--to=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).