public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Uwe Brauer <oub-YB6e1s5WF/He5aOfsHch1g@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: from org --> odt/docx -->back, does not well word for odt
Date: Sun, 10 Jul 2022 18:19:02 +0200	[thread overview]
Message-ID: <87mtdhueix.fsf@mat.ucm.es> (raw)
In-Reply-To: <87y1x1uezb.fsf@mat.ucm.es>

[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]


> 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             |


On my MacBook I have 1.22 and I can reproduce the problem.

Uwe Brauer 

-- 
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 view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/87mtdhueix.fsf%40mat.ucm.es.

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]

      reply	other threads:[~2022-07-10 16:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-10 16:09 Uwe Brauer
2022-07-10 16:19 ` Uwe Brauer [this message]

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=87mtdhueix.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).