From: Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Bottomrule in tables in beamer output not visible?
Date: Thu, 23 Mar 2023 08:21:24 +0100 [thread overview]
Message-ID: <87wn383p61.fsf@zeitkraut.de> (raw)
In-Reply-To: <bb027d19-3062-47a7-98b8-64d164808099n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
This is an instance of the problem reported here:
<https://github.com/jgm/pandoc/issues/8638>. The issue has been fixed in
the current development version.
You can test the fix by using a recent nightly build from here:
https://github.com/jgm/pandoc/actions/runs/4476692089
Ant Eagle <ant-DePdjkTX6oTpmi9iPZTz7g@public.gmane.org> writes:
> When I try the following MWE in pandoc markdown I get puzzlingly
> different output
>
> ```
> ## Slide title ##
>
> | A | B | C |
> |:---|:---:|---:|
> | 0 | 7 | 8 |
> | 2 | 4 | 3 |
> | 1 | 2 | 7 |
>
> : A table
> ```
>
> When I try
>
>
> pandoc -f markdown -t pdf -s -o table.pdf table.md
>
>
> I get what I expect:
> Screenshot 2023-03-23 at 15.54.
> But when I try
>
>
> pandoc -f markdown -t beamer -s -o table.pdf table.md
>
>
> I get a missing bottomrule:
> Screenshot 2023-03-23 at 15.54.
> Any ideas as to why? I'm not using any weird packages, etc., this is
> all absolutely default stuff. When comparing the .tex output for both
> latex and beamer, the code for the table itself is the same. So is
> this a bad interaction between longtable and beamer, or caused by
> something else in the beamer implementation in pandoc?
--
Albert Krewinkel
GPG: 8eed e3e2 e8c5 6f18 81fe e836 388d c0b2 1f63 1124
--
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/87wn383p61.fsf%40zeitkraut.de.
next prev parent reply other threads:[~2023-03-23 7:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 5:30 Ant Eagle
[not found] ` <bb027d19-3062-47a7-98b8-64d164808099n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-03-23 7:21 ` Albert Krewinkel [this message]
[not found] ` <87wn383p61.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2023-03-23 9:49 ` Ant Eagle
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=87wn383p61.fsf@zeitkraut.de \
--to=albert+pandoc-9eawchwdxg8hfhg+jk9f0w@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).