From: kurt.pfeifle-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Is the usage of "longtable" hard-coded into current Pandoc?
Date: Sun, 5 Jul 2015 14:06:20 -0700 (PDT) [thread overview]
Message-ID: <76171d01-68c8-4927-99ec-560e3280659f@googlegroups.com> (raw)
In-Reply-To: <CAKGY2P=97XY+AW_+KBNevd8LDD+hhbbNtaT__utC-B+2CGJ=mg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 3137 bytes --]
As long as this is not yet implemented, maybe a little hint in the
docu/README should be placed explaining that…
- …Markdown tables do not work in PDF/LaTeX/Beamer output,
- …and will even stop to create *any* of the desired output unless the
Markdown table is removed altogether or replaced by appropriat raw_tex
table code.
Am Sonntag, 5. Juli 2015 01:54:27 UTC+2 schrieb Wagner Macedo:
Hello John,
>
> I also have an issue with long tables due to 'longtables' sometimes
> unnecessarily split small tables (depending where you insert). So, while we
> don't have a better option how about if pandoc provide an option to use
> standard tabular instead of the default longtables?
>
> --
> Wagner Macedo
>
> On 4 July 2015 at 19:26, John MacFarlane <j...-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org <javascript:>>
> wrote:
>
>> +++ kurt.p...-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org <javascript:> [Jul 04 15 11:41 ]:
>>
>>> It occurred to me that what I had thought of previously may not work:
>>> modifying the LaTeX template to not use `longtable`, but another
>>> package instead and get classoption `twocolumn` to work.
>>> This may be because the LaTeX "micro code" (my name for it) for tables
>>> may not work when simply loading a different table package. Is this
>>> assumption correct?
>>>
>>
>> Correct, use of longtable is hard coded. This is quite
>> unfortunate, and I've long been wanting a better alternative
>> that will work with 2-column text but also break across
>> pages when needed. Haven't found one yet.
>>
>> Failing that, it may be worth having an option for regular
>> tables.
>>
>> Do I indeed have to resort into writing my own raw LaTeX code if I want
>>> tables in two-column output?
>>>
>>
>> It's probably possible to redefine the longtable environment
>> to something else in your preamble.
>>
>> --
>> 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...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>.
>> To post to this group, send email to pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>> <javascript:>.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/pandoc-discuss/20150704222645.GD11787%40localhost.hsd1.ca.comcast.net
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
--
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/76171d01-68c8-4927-99ec-560e3280659f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 11819 bytes --]
next prev parent reply other threads:[~2015-07-05 21:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-04 18:41 kurt.pfeifle-gM/Ye1E23mwN+BqQ9rBEUg
[not found] ` <37a4c533-b6b8-4f8c-af74-52c37c0798bf-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-07-04 22:26 ` John MacFarlane
[not found] ` <20150704222645.GD11787-bi+AKbBUZKbivNSvqvJHCtPlBySK3R6THiGdP5j34PU@public.gmane.org>
2015-07-04 23:54 ` Wagner Macedo
[not found] ` <CAKGY2P=97XY+AW_+KBNevd8LDD+hhbbNtaT__utC-B+2CGJ=mg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-07-05 21:06 ` kurt.pfeifle-gM/Ye1E23mwN+BqQ9rBEUg [this message]
[not found] ` <76171d01-68c8-4927-99ec-560e3280659f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-07-06 4:12 ` Wagner Macedo
[not found] ` <a1f74398-0593-452e-b0d0-43c66f72304c-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-07-06 13:21 ` kurt.pfeifle-gM/Ye1E23mwN+BqQ9rBEUg
[not found] ` <5e1a514c-9422-4fc6-8257-5040990ceb53-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-07-06 14:03 ` Wagner Macedo
[not found] ` <CAKGY2Pm6nyJdRWG6cwAuFoQcZ=LFUPo+y89Tg6m9bv+X96n0MQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-07-19 20:55 ` Richard Huntsinger
2022-07-19 20:46 ` Richard Huntsinger
2022-07-19 20:43 ` Richard Huntsinger
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=76171d01-68c8-4927-99ec-560e3280659f@googlegroups.com \
--to=kurt.pfeifle-gm/ye1e23mwn+bqq9rbeug@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).