You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The pandoc document model doesn't yet support table cells
that span multiple columns. So I suppose the docx reader
is doing as well as it can with your table.
Pandoc expects table rows to have the same number of cells.
(Ideally this would be enforced at the type level, but
currently it is not.) When this assumption fails,
unexpected things may happen, but I'm not sure what
you consider a better behavior would be.
If both the layout can't be replicated and the data's gone, I don't think that's gonna be a win for anybody. I do prefer the rst writer's behaviour, but it might not be worth toiling over; personally, I've taken to parsing the JSON output, which is what I should've been doing from the start.
The pandoc document model doesn't yet support table cells
that span multiple columns. So I suppose the docx reader
is doing as well as it can with your table.
Pandoc expects table rows to have the same number of cells.
(Ideally this would be enforced at the type level, but
currently it is not.) When this assumption fails,
unexpected things may happen, but I'm not sure what
you consider a better behavior would be.
—
Reply to this email directly or view it on GitHub.
With pandoc version 1.16, Imported
docx
tables in the formatappear to be interpreted as
which some writers, like
rst
, print as above, whereas others, notablyplain
and
markdown
, print as below:pandoc --from=docx --to=markdown test.docx
produces:pandoc --from=docx --to=markdown-simple_tables test.docx
produces:pandoc --from=docx --to=rst test.docx
produces:pandoc --from=docx --to=native test.docx
produces:The text was updated successfully, but these errors were encountered: