public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Pipe table content does not wrap in PDF
Date: Wed, 25 Oct 2023 09:36:27 -0700	[thread overview]
Message-ID: <5E4C2B79-FE4D-4D8E-9422-7C15DD5D1F63@gmail.com> (raw)
In-Reply-To: <a7dd3efe-aa22-4536-90a6-6ccadf314573n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

Two issues:

1)  You're using gfm+pipe_tables, not pandoc's markdown.  The special treatment of relative column widths in pipe tables is a pandoc innovation, not something GFM implements, so it doesn't work with gfm+pipe_tables

2)  The raw HTML in the cells wouldn't pass  through to PDF anyway...



> On Oct 25, 2023, at 9:23 AM, 'Martin Ehlers' via pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> wrote:
> 
> Sure, this is markdown source code for the table I had attached as a screenshot:
> 
> | NX-OS configuration                                                                                                | Variables applied                                                                                                                                                           | Variable & Constansts                                                                                                                                                         |
> |--------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
> | <pre>vlan 1523<br> name SAR-P_MDB_102_BIE_A<br> vn-segment 1001523</pre>                                           | <pre>vlan \<VLAN_ID\><br> name \<VLAN_NAME\><br> vn-segment \<VN_SEG\></pre>                                                                                                | <pre>VLAN:<br> - VLAN_ID: 1523<br> - VLAN_NAME: SAR-P_MDB_x02_BIE_A<br> - VN_SEG: 1001523</pre>                                                                               |
> | <pre>interface nve1<br> member vni 1001523<br> multisite ingress-replication<br> mcast-group 239.100.200.101</pre> | <pre>interface \<INTERFACE_CATEGORY\>\<PORT\><br> member vni \<VNI\><br> multisite ingress-replication<br> mcast-group \<M_GROUP\></pre>                                    | <pre>INTERFACE_NVE1:<br> INTERFACE-CATEGORY: nve (const)<br> PORT: 1 (const)<br> VNI: 1001523<br> MULTISITE_INGRESS_REPLICATION_FLAG: True<br> M_GROUP: 239.100.200.101</pre> |
> | <pre>evpn<br> vni 1001523 l2<br> rd auto<br> route-target import auto<br> route-target export auto</pre>           | <pre>evpn<br> vni \<VNI\> \<VNI_TYPE\><br> rd \<ROUTE_DISTINGUISHER\><br> route-target import \<ROUTE_TARGET_IMPORT\><br> route-target export \<ROUTE_TARGET_EXPORT\></pre> | <pre>INTERFACE_NVE1:<br> INTERFACE-CATEGORY: nve (const)<br> PORT: 1 (const)<br> VNI: 1001523<br> M_GROUP: 239.100.200.101</pre>                                              |
> 
> I have the same issue with all tables exceeding the column width, also with simple text, i.e. without control statements like "<br>".
> 
> Kind Regards
> Martin
> 
> John MacFarlane schrieb am Dienstag, 24. Oktober 2023 um 19:14:08 UTC+2:
> Can you post the markdown source for the table? 
> 
> > On Oct 24, 2023, at 1:10 AM, 'Martin Ehlers' via pandoc-discuss <pandoc-...@googlegroups.com> wrote: 
> > 
> > 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 
> > 
> > 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-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org 
> > To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/93d59e4d-d23e-4dca-ad50-80e970c7ba66n%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/a7dd3efe-aa22-4536-90a6-6ccadf314573n%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/5E4C2B79-FE4D-4D8E-9422-7C15DD5D1F63%40gmail.com.


  parent reply	other threads:[~2023-10-25 16:36 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
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 [this message]
     [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=5E4C2B79-FE4D-4D8E-9422-7C15DD5D1F63@gmail.com \
    --to=fiddlosopher-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).