public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: jiewuza <jiewuza-9Onoh4P/yGk@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Bounty for Table Cells that Span
Date: Tue, 25 Feb 2020 16:09:56 +0800	[thread overview]
Message-ID: <m27e0b84vf.fsf@163.com> (raw)
In-Reply-To: <768ecd54-52b9-4ccd-b84a-b7fda991ae39@googlegroups.com>


This involves two issues:
1. markdown format for multiple column spanning tables
2. pandoc AST that supports colspan
(https://github.com/jgm/pandoc/issues/1024)

IMHO, the first one relates to markdown standard, which is beyond the
control of pandoc community.

While the second one seems be discussed over years. It would be great if
someone starts this work. It is beneficial to HTML/Latex format which supports
multiple column spanning table by itself.


IVO I WELCH <ivo.welch-xwz7R8GQi1g@public.gmane.org> writes:

> If anyone would like to take on the task of creating a reasonable markdown input table format that allows for multiple column spanning with output support into docx, pptx, latex, pdf, and html, *AND* convince
> john macfarlane to accept the changes into the pandoc code base in 2020, I would be happy to subsidize the effort with $500.
>
> please coordinate with this group, john, and myself if interested.
>
> /iaw
>
> PS: we had some discussions about reasonable input formats in https://groups.google.com/forum/#!searchin/pandoc-discuss/iaw%7Csort:date/pandoc-discuss/1Ljpq0fX9fo/VDoV01uwAAAJ .  this
> particular format would work great for me, but any other reasonable input format would be ok for me, too.  getting john m on board is really key.


  reply	other threads:[~2020-02-25  8:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-25  0:36 IVO I WELCH
2020-02-25  8:09 ` jiewuza [this message]
     [not found] ` <768ecd54-52b9-4ccd-b84a-b7fda991ae39-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-02-29 13:26   ` mb21

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=m27e0b84vf.fsf@163.com \
    --to=jiewuza-9onoh4p/ygk@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).