public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Dylan Muir <dylan.richard.muir-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Control resolution for converting .EPS figures, when writing to .DOCX
Date: Tue, 29 Aug 2017 23:21:54 -0700 (PDT)	[thread overview]
Message-ID: <01c22f32-d780-4ebd-b8bb-64cf8f029ea1@googlegroups.com> (raw)


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

Hi,

I am using pandoc to convert a latex manuscript to Word DOCX. My latex 
document has several figures in EPS format. These are successfully included 
in the DOCX output, but only at low resolution. The bounding box of the EPS 
figures is set to a reasonable size (e.g. 85mm), and the contents of the 
EPS files are vectors.

How can I control the resolution that pandoc uses when rasterising the 
figures to include in the DOCX output? I have tried setting the --dpi 
option to pandoc ("--dpi=300"), but this didn't increase the resolution of 
the final images.

Thanks,
Dylan Muir.

-- 
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/01c22f32-d780-4ebd-b8bb-64cf8f029ea1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

                 reply	other threads:[~2017-08-30  6:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=01c22f32-d780-4ebd-b8bb-64cf8f029ea1@googlegroups.com \
    --to=dylan.richard.muir-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).