public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Thomas Blom <blomcode-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: docx -> markdown: image width and height doesn't respect --dpi?
Date: Tue, 29 Aug 2017 08:01:05 -0700 (PDT)	[thread overview]
Message-ID: <16de6b70-107f-41ab-9b2c-73c330a0fca2@googlegroups.com> (raw)
In-Reply-To: <20170829060923.GF59266-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>


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

Ok, thanks for looking into this!

-Thomas

On Tuesday, August 29, 2017 at 1:09:32 AM UTC-5, John MacFarlane wrote:
>
> With -t markdown_strict, the dev version gives 
>
> > <img src="media/image1.png" alt="MacSSD:Users:kajohnson:Dropbox:Kinetics 
> Book:Chapter 2:Table 2-1.png" style="width:4.61686in" style="height:2.5in" 
> /> 
>
> So it looks as if this issue has been fixed in the dev 
> version.  (Sort of...I need to investigate the duplicated 
> style attributes in the HTML fallback.) 
>
> +++ Thomas Blom [Aug 28 17 18:40 ]: 
> >   In my example command illustrating the issue, I am using "-t 
> >   markdown_strict". 
> >   I assume you are using "-t markdown" ? 
> >   I am not using the dev version of pandoc, but am using the latest 
> >   release as installed by Homebrew on OSX (1.19.2.1). 
> >   Thanks! 
> >   On Monday, August 28, 2017 at 7:13:17 PM UTC-5, John MacFarlane wrote: 
> > 
> >     With the dev version of pandoc, when I convert this to 
> >     Markdown I get: 
> >     > ![MacSSD:Users:kajohnson:Dropbox:Kinetics Book:Chapter 2:Table 
> >     > 2-1.png](foo/media/image1.png){width="4.616858048993876in" 
> >     > height="2.5in"} 
> >     So the Markdown writer doesn't convert the size to pixels; 
> >     if it's doing that for you, the behavior has been changed. 
> > 
> >   -- 
> >   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-discus...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>. 
> >   To post to this group, send email to 
> >   [2]pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>. 
> >   To view this discussion on the web visit 
> >   [3]
> https://groups.google.com/d/msgid/pandoc-discuss/11b99952-c27d-4a1a- 
> >   b689-d0e915d886dc%40googlegroups.com. 
> >   For more options, visit [4]https://groups.google.com/d/optout. 
> > 
> >References 
> > 
> >   1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:> 
> >   2. mailto:pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:> 
> >   3. 
> https://groups.google.com/d/msgid/pandoc-discuss/11b99952-c27d-4a1a-b689-d0e915d886dc-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer 
> >   4. https://groups.google.com/d/optout 
>
>

-- 
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/16de6b70-107f-41ab-9b2c-73c330a0fca2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

      parent reply	other threads:[~2017-08-29 15:01 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
     [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 [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=16de6b70-107f-41ab-9b2c-73c330a0fca2@googlegroups.com \
    --to=blomcode-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).