public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "'Ehlers, Martin (EXT)' via pandoc-discuss" <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
To: "pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org"
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Pipe table content does not wrap in PDF
Date: Tue, 24 Oct 2023 08:21:12 +0000	[thread overview]
Message-ID: <e878e1328ea34a2f8fd9e2a328ad4966@bwi.de> (raw)

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

Kind Regards
Martin


-----Ursprüngliche Nachricht-----
Von: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> Im Auftrag von John MacFarlane
Gesendet: Montag, 23. Oktober 2023 18:14
An: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Betreff: [Externe E-Mail] Re: Pipe table content does not wrap in PDF

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.
.

-- 
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/e878e1328ea34a2f8fd9e2a328ad4966%40bwi.de.


             reply	other threads:[~2023-10-24  8:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-24  8:21 'Ehlers, Martin (EXT)' via pandoc-discuss [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
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

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=e878e1328ea34a2f8fd9e2a328ad4966@bwi.de \
    --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).