From: Uwe Brauer <oub-YB6e1s5WF/He5aOfsHch1g@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: from org --> odt/docx -->back, does not well word for odt
Date: Sun, 10 Jul 2022 18:09:12 +0200 [thread overview]
Message-ID: <87y1x1uezb.fsf@mat.ucm.es> (raw)
Hi
I set up a simple org file containing two headers and two tables, I converted them with the org native export machine to odt and then with LO to docx.
When I used pandoc (still 1.19 sorry), the conversion from docx was ok, but the conversion from odt, left the tables out.
I attach
| test-orginal.org | orginal org file |
| test.odt | converted via org-native |
| test.docx | converted via LO |
| test-from-docx.org | using pandoc |
| test-from-odt.org | using pandoc |
Any idea what's going on here (I hope it is not my old pandoc version)
--
I strongly condemn Putin's war of aggression against the Ukraine.
I support to deliver weapons to Ukraine's military.
I support the ban of Russia from SWIFT.
I support the EU membership of the Ukraine.
next reply other threads:[~2022-07-10 16:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-10 16:09 Uwe Brauer [this message]
2022-07-10 16:19 ` Uwe Brauer
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=87y1x1uezb.fsf@mat.ucm.es \
--to=oub-yb6e1s5wf/he5aofshch1g@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).