public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Wagner Macedo <wagnerluis1982-Re5JQEeQqe8AvxtiuMwx3w@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 21:12:13 -0700 (PDT)	[thread overview]
Message-ID: <a1f74398-0593-452e-b0d0-43c66f72304c@googlegroups.com> (raw)
In-Reply-To: <76171d01-68c8-4927-99ec-560e3280659f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1138 bytes --]

I don't see what you are talking about of not implemented. Markdown tables is very well converted to latex. But unfortunately has some issues that isn't suited to every situations and I agree to maintain longtables as the default option, as the standard latex 'table' environment with 'tabular' has other issues such as not handle footnotes, not adjust columns and not split between pages.

If you can live with all these limitations I used in some of my documents a filter that I wrote in Python to read a table and write a tabular instead of longtables.

-- 
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/a1f74398-0593-452e-b0d0-43c66f72304c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

  parent reply	other threads:[~2015-07-06  4:12 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
     [not found]             ` <76171d01-68c8-4927-99ec-560e3280659f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-07-06  4:12               ` Wagner Macedo [this message]
     [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=a1f74398-0593-452e-b0d0-43c66f72304c@googlegroups.com \
    --to=wagnerluis1982-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).