public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Kolen Cheung <christian.kolen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: bug: docx (containing table) to native and docx to markdown then to native is hugely different
Date: Tue, 6 Dec 2016 23:06:11 -0800 (PST)	[thread overview]
Message-ID: <3c212e85-1e24-4fa2-817e-051e55f5821d@googlegroups.com> (raw)


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



I have a doc with 2 tables. I converted it to docx (with Word) and then 
trying to use pandoc to convert it to md.

I got some strange error, and when looking at the native I found this:

   1. pandoc -t native others/Mirrors-Lens.docx -o 
   others/Mirrors-Lens.native is kind of normal 
   2. pandoc -t markdown others/Mirrors-Lens.docx | pandoc -f markdown -t 
   native -o others/Mirrors-Lens-round.native is hugely different from the 
   above 

One of the main difference is that both tables (originally multi-columned) 
collapsed to 1 column only in the later round-trip. (Another annoyance to 
me is I actually tried to use my pantable2csv filter to capture the table 
from the docx directly into csv but resulted in error.)

For the 2nd table, I’m guessing the existence of <, > causes problems. For 
the 1st I have no clue since the native looks fine to me.

But since I do not own the copyright of the file, I am not going to share 
this publicly (isn’t really important but just in case…). If anyone is 
interested in help solving the puzzle / debug pandoc, please give me your 
github account and I can open a private repository and invite you. Thanks!
​

-- 
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/3c212e85-1e24-4fa2-817e-051e55f5821d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

             reply	other threads:[~2016-12-07  7:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-07  7:06 Kolen Cheung [this message]
     [not found] ` <3c212e85-1e24-4fa2-817e-051e55f5821d-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2016-12-07  9:57   ` Kolen Cheung
2016-12-07 10:23   ` Kolen Cheung

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=3c212e85-1e24-4fa2-817e-051e55f5821d@googlegroups.com \
    --to=christian.kolen-re5jqeeqqe8avxtiumwx3w@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).