public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: docx -> markdown: image width and height doesn't respect --dpi?
Date: Mon, 28 Aug 2017 07:57:32 -0700	[thread overview]
Message-ID: <20170828145732.GI57370@Johns-MacBook-Pro.local> (raw)
In-Reply-To: <692f87e9-d992-4d10-a29a-77165f5d5771-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

Can you give us a simple docx file to test with?

+++ Thomas Blom [Aug 27 17 20:21 ]:
>   Hi,
>   I convert docx to markdown using pandoc 1.19.2.1 on OSX 10.12 with
>   pandoc -t markdown_strict --dpi=128 --extract-media=images mydoc.docx
>   -o mydoc.md
>   I find that the image sizes in the markdown appear to be based on a
>   96dpi image resolution no matter what --dpi I specify, and also no
>   matter the meta-data in the files embedded in the (word for mac 2011)
>   document (PNG, 144dpi).
>   For example, one image in Word has been sized by the author to be
>   ~4.65inches wide.  The resulting markdown for this image specifies a
>   width of 443 pixels.  So I see that markdown is using a dpi of 443/4.65
>   =~ 96 regardless of efforts on my part to change this.
>   I would like to adjust this because the images appear smaller at this
>   pixel size than the same images in Word.  I can of course write a
>   post-processing script to adjust sizes on the markdown document, but
>   would prefer to avoid.  It seems like the --dpi option makes sense to
>   address my situation?
>   Thanks,
>   Thomas Blom
>
>   --
>   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 [1]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To post to this group, send email to
>   [2]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To view this discussion on the web visit
>   [3]https://groups.google.com/d/msgid/pandoc-discuss/692f87e9-d992-4d10-
>   a29a-77165f5d5771%40googlegroups.com.
>   For more options, visit [4]https://groups.google.com/d/optout.
>
>References
>
>   1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   2. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   3. https://groups.google.com/d/msgid/pandoc-discuss/692f87e9-d992-4d10-a29a-77165f5d5771-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
>   4. https://groups.google.com/d/optout


  parent reply	other threads:[~2017-08-28 14:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-28  3:21 Thomas Blom
     [not found] ` <692f87e9-d992-4d10-a29a-77165f5d5771-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-08-28 14:57   ` John MacFarlane [this message]
     [not found]     ` <20170828145732.GI57370-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2017-08-28 15:57       ` Thomas Blom
     [not found]         ` <591842f3-2fcf-4a1b-b031-9b2c4f8dad05-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-08-29  0:13           ` John MACFARLANE
     [not found]             ` <20170829001310.GA75750-nFAEphtLEs/fysO+viCLMa55KtNWUUjk@public.gmane.org>
2017-08-29  1:40               ` Thomas Blom
     [not found]                 ` <11b99952-c27d-4a1a-b689-d0e915d886dc-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-08-29  6:09                   ` John MacFarlane
     [not found]                     ` <20170829060923.GF59266-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2017-08-29 15:01                       ` Thomas Blom

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=20170828145732.GI57370@Johns-MacBook-Pro.local \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@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).