Using Pandoc's markdown instead of GFM indeed fixes the issue. Cell contents are wrapped now. Thanks so much for your support! Kind Regards Martin John MacFarlane schrieb am Mittwoch, 25. Oktober 2023 um 18:36:33 UTC+2: > 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-...-/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 | > > > |--------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| > > | 
vlan 1523
 name SAR-P_MDB_102_BIE_A
 vn-segment 
> 1001523
| 
vlan \
 name \
 vn-segment 
> \
| 
VLAN:
 - VLAN_ID: 1523
 - VLAN_NAME: 
> SAR-P_MDB_x02_BIE_A
 - VN_SEG: 1001523
| > > | 
interface nve1
 member vni 1001523
 multisite 
> ingress-replication
 mcast-group 239.100.200.101
| 
interface 
> \\
 member vni \
 multisite 
> ingress-replication
 mcast-group \
| > 
INTERFACE_NVE1:
 INTERFACE-CATEGORY: nve (const)
 PORT: 1 
> (const)
 VNI: 1001523
 MULTISITE_INGRESS_REPLICATION_FLAG: True
 
> M_GROUP: 239.100.200.101
| > > | 
evpn
 vni 1001523 l2
 rd auto
 route-target import 
> auto
 route-target export auto
| 
evpn
 vni \ 
> \
 rd \
 route-target import 
> \
 route-target export 
> \
| 
INTERFACE_NVE1:
 
> INTERFACE-CATEGORY: nve (const)
 PORT: 1 (const)
 VNI: 1001523
 
> M_GROUP: 239.100.200.101
| > > > > I have the same issue with all tables exceeding the column width, also > with simple text, i.e. without control statements like "
". > > > > 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-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 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-discus...-/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/2f088d22-165a-4ded-9811-d93fcf01ce76n%40googlegroups.com.