-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Beamer slides (PDF) show linguistic examples in a overt table #1
Comments
In any case, I really appreciate your work of |
I have never used |
Quick comment before I get to the lines: I first could not reproduce your output, until I realised that there is a change between pandoc 2.11.2 and 2.11.3 for the output of the new table format to latex. Now it works! That is great news! |
Thank you for your work-around. Just a clarification: should I stop using pandoc 2.11.3 and revert to older version of pandoc? |
no no! 2.11.3 is much better! Your results were already better than I was getting here in the last weeks, so I was surprised to see your output. Then I found that I was a .point version behind :-) |
I got it, and I will keep using the latest version of pandoc! 👍🏻 |
Seems to work now: I simply added Please try it with the new release v1.2 and tell me if it works for you |
When I create
Beamer
slides including some linguistic examples produced viapandoc-ling
, the output slides undesirably have these examples in a visible table, as shown in the following screen capture. This does not occur when I create a usual LaTeX-based documents (e.g.article
class).The behaviour is understandable since
pandoc-ling
is a table-environment-based glossing system, as you stated in the manual. However, is there any good practice to make these tables invisible?Working example
Here I put an Rmarkdown example with two subsidiary R packages,
bookdown
andofficedown
. The contents are exactly same as pandoc's markdown, except what I wrote in YAML section.Environment
pandoc-ling: v1.1
pandoc: v2.11.3.2
OS: Windows 10 x64 (build 19042)
The text was updated successfully, but these errors were encountered: