From: IVO I WELCH <ivo.welch-xwz7R8GQi1g@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Bounty for Table Cells that Span
Date: Mon, 24 Feb 2020 16:36:54 -0800 (PST) [thread overview]
Message-ID: <768ecd54-52b9-4ccd-b84a-b7fda991ae39@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1159 bytes --]
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.
--
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/768ecd54-52b9-4ccd-b84a-b7fda991ae39%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1584 bytes --]
next reply other threads:[~2020-02-25 0:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 0:36 IVO I WELCH [this message]
2020-02-25 8:09 ` jiewuza
[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=768ecd54-52b9-4ccd-b84a-b7fda991ae39@googlegroups.com \
--to=ivo.welch-xwz7r8gqi1g@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).