public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MACFARLANE <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Converting docx tables to markdown piped tables
Date: Thu, 24 Aug 2017 18:09:22 -0700	[thread overview]
Message-ID: <20170825010922.GD77000@protagoras.berkeley.edu> (raw)
In-Reply-To: <f2cbf749-c0df-4a5c-8ea2-1f47866256df-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

Is it that you're getting a different kind of table?
Pandoc's Markdown supports several kinds of tables,
and the markdown writer tends to prefer the other
styles to pipe tables. So, if you want pipe tables,
you may have to disable the others: try

-t markdown-simple_tables-multiline_tables-grid_tables

+++ tolot27 [Aug 24 17 13:04 ]:
>   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 [1]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To post to this group, send email to
>   [2]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To view this discussion on the web visit
>   [3]https://groups.google.com/d/msgid/pandoc-discuss/f2cbf749-c0df-4a5c-
>   8ea2-1f47866256df%40googlegroups.com.
>   For more options, visit [4]https://groups.google.com/d/optout.
>
>References
>
>   1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   2. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   3. https://groups.google.com/d/msgid/pandoc-discuss/f2cbf749-c0df-4a5c-8ea2-1f47866256df-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
>   4. https://groups.google.com/d/optout


  parent reply	other threads:[~2017-08-25  1:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-24 20:04 tolot27
     [not found] ` <f2cbf749-c0df-4a5c-8ea2-1f47866256df-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-08-25  1:09   ` John MACFARLANE [this message]
     [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=20170825010922.GD77000@protagoras.berkeley.edu \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@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).