public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "wolfgang häfelinger" <whaefelinger-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: HTML => ODT - almost identical conversion possible?
Date: Wed, 14 Apr 2021 07:55:21 -0700 (PDT)	[thread overview]
Message-ID: <60ca164c-f868-412d-bdcf-9f75e36f5317n@googlegroups.com> (raw)


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

Dear all,

I generated an example resume (see resume.html) from an ASCIIDOC input. Now 
I wonder whether I can use PANDOC to convert that resume into ODT or DOCX.

I tried 

pandoc -f html resume.html -t odt -o resume.odt

which produced attached ODT file. Below is a screenshot showing the result. 
Obviously the layout is not the same, icons are far to big and so on.

Is there a (easy) way to instruct PANDOC to get a 1:1 convertion?

Thanks.



[image: Screenshot 2021-04-14 at 16.50.44.png]

-- 
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/60ca164c-f868-412d-bdcf-9f75e36f5317n%40googlegroups.com.

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

[-- Attachment #2: Screenshot 2021-04-14 at 16.50.44.png --]
[-- Type: image/png, Size: 344369 bytes --]

[-- Attachment #3: resume.html --]
[-- Type: text/html, Size: 7107 bytes --]

[-- Attachment #4: resume.odt --]
[-- Type: application/x-zip, Size: 67098 bytes --]

             reply	other threads:[~2021-04-14 14:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-14 14:55 wolfgang häfelinger [this message]
     [not found] ` <60ca164c-f868-412d-bdcf-9f75e36f5317n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-04-14 16:11   ` John MacFarlane
     [not found]     ` <m2tuo8hmm0.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2021-04-15  6:35       ` wolfgang häfelinger
     [not found]         ` <9708c88a-0378-4a49-a7a9-20003d16e301n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-04-15 17:50           ` MarLinn
     [not found]             ` <6b87196f-8262-3147-fa5d-9f9f4a55ad83-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2021-04-19 15:42               ` wolfgang häfelinger

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=60ca164c-f868-412d-bdcf-9f75e36f5317n@googlegroups.com \
    --to=whaefelinger-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).