From: Daniel Staal <DStaal-Jdbf3xiKgS8@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: MediaWiki to Markdown conversion
Date: Wed, 15 Apr 2020 11:32:35 -0400 [thread overview]
Message-ID: <673beeae-bdca-10b0-9a4e-acbe9d082975@usa.net> (raw)
In-Reply-To: <41ad78f7-a660-40ec-b49a-7061b2800b7f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
On 4/15/20 7:42 AM, sal wrote:
> So, do you see the outcome table ok?
> Maybe I'm doing wrong more than just one thing...
> What did you use to see it?
> I go to an online markdown viewer (like https://markdownlivepreview.com/
> or any other),
> I paste the outcome there and see the table is not properly converted.
I open it up as a text file. No viewer used. ;)
There's no 'official' table spec in Markdown, just whatever table each
variant has supported, so if you're using a viewer (or a different
converter) you need to match the variant that viewer supports.
> I tested that command, but again no success with the table.
> If there are different ways to convert tables, is that documented somewhere?
<https://pandoc.org/MANUAL.html#tables>
> Thanks again. Once I get this thing done, I still will have to convert
> it to "remarkup",
> which is used by Phabricator software.
> Unfortunately I have not find any tool to convert directly from
> MediaWiki to ReMarkUp.
Looks like remarkup uses what Pandoc calls 'Pipe Tables', so you may want:
```
pandoc source -f mediawiki -t
markdown-simple_tables+pipe_tables-multiline_tables -o outcome
```
Daniel T. Staal
--
---------------------------------------------------------------
This email copyright the author. Unless otherwise noted, you
are expressly allowed to retransmit, quote, or otherwise use
the contents for non-commercial purposes. This copyright will
expire 5 years after the author's death, or in 30 years,
whichever is longer, unless such a period is in excess of
local copyright law.
---------------------------------------------------------------
next prev parent reply other threads:[~2020-04-15 15:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 22:57 sal
[not found] ` <79af9e1a-acb0-4bc0-85e6-5812d88238e1-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-04-15 0:03 ` Daniel Staal
[not found] ` <8499788f-514a-9723-148e-f079effe88db-Jdbf3xiKgS8@public.gmane.org>
2020-04-15 11:42 ` sal
[not found] ` <41ad78f7-a660-40ec-b49a-7061b2800b7f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-04-15 15:32 ` Daniel Staal [this message]
[not found] ` <673beeae-bdca-10b0-9a4e-acbe9d082975-Jdbf3xiKgS8@public.gmane.org>
2020-04-15 20:19 ` sal
[not found] ` <07c2c373-5f47-4283-b740-d15feabd8ba5-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-04-19 23:10 ` sal
[not found] ` <4dbf4d89-1367-44fd-8227-5a39cee018b9-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-04-20 0:31 ` John MacFarlane
[not found] ` <m2wo6bf15k.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2020-04-20 23:41 ` sal
[not found] ` <6026cf94-1b7a-4e0a-9b0b-790891b6e759-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-04-21 5:43 ` John MacFarlane
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=673beeae-bdca-10b0-9a4e-acbe9d082975@usa.net \
--to=dstaal-jdbf3xikgs8@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).