public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: tolot27 <mathias-taBouHiV1h1goHlPtYpdqQ@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Converting docx tables to markdown piped tables
Date: Thu, 24 Aug 2017 13:04:05 -0700 (PDT)	[thread overview]
Message-ID: <f2cbf749-c0df-4a5c-8ea2-1f47866256df@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1075 bytes --]

Hi!

I just wonder why I cannot convert a docx table to a markdown piped table 
if I use the following command: pandoc -t markdown+pipe_tables

It only works if I convert it to markdown_mmd or markdown_phpextra but has 
the drawback that I get much more diffs compared with my original markdown 
document (which I have converted to docx for review purposes). Also the 
syntax of docx documents changes to the form using spans.

Did I understand the extension mechanism incorrectly?

--
Regards,
Mathias

-- 
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/f2cbf749-c0df-4a5c-8ea2-1f47866256df%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #1.2: Type: text/html, Size: 1599 bytes --]

             reply	other threads:[~2017-08-24 20:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-24 20:04 tolot27 [this message]
     [not found] ` <f2cbf749-c0df-4a5c-8ea2-1f47866256df-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-08-25  1:09   ` John MACFARLANE
     [not found]     ` <20170825010922.GD77000-nFAEphtLEs/fysO+viCLMa55KtNWUUjk@public.gmane.org>
2017-08-26 19:35       ` tolot27

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=f2cbf749-c0df-4a5c-8ea2-1f47866256df@googlegroups.com \
    --to=mathias-tabouhiv1h1gohlptypdqq@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).