public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Richard Huntsinger <rhuntsinger-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: How to size images?
Date: Thu, 21 Jul 2022 13:35:53 -0700 (PDT)	[thread overview]
Message-ID: <bbdf0806-8476-43af-bce7-47a17343e8f4n@googlegroups.com> (raw)
In-Reply-To: <87tu7bdbfl.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>


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

Thanks, that works well.

Another solution I've come to is to just display jpeg's from code cells 
rather than from markdown cells, like this: display_jpeg(file="img.jpg", 
width=400).  pandoc's normal behavior then just converts the sized image to 
\includegraphics[width=..., height=...]{images/...}



On Wednesday, July 20, 2022 at 8:57:26 AM UTC-7 Albert Krewinkel wrote:

>
> Richard Huntsinger <rhunt...-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org> writes:
>
> > Is there a way, perhaps with a lua filter, to capture the <img
> > src="image.jpg" width=600> with the sizing
> > information [...]
>
> Lua filter to do this:
>
> ``` lua
> function RawInline (raw)
> if raw.format:match 'html' then
> return pandoc.utils.blocks_to_inlines(
> pandoc.read(raw.text, 'html').blocks
> )
> end
> end
> ```
>
> This tries to convert *all* inline HTML code. Modify the `if` condition
> in case you want this behavior only for images:
>
> if raw.text:match '^<img' and ...
>
>
> -- 
> Albert Krewinkel
> GPG: 8eed e3e2 e8c5 6f18 81fe e836 388d c0b2 1f63 1124
>

-- 
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/bbdf0806-8476-43af-bce7-47a17343e8f4n%40googlegroups.com.

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

      parent reply	other threads:[~2022-07-21 20:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-19 21:52 Richard Huntsinger
     [not found] ` <7aa4ae72-1fae-49a3-bb91-035b78b92dean-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-07-20 13:54   ` Albert Krewinkel
     [not found]     ` <87tu7bdbfl.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-07-21 20:35       ` Richard Huntsinger [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=bbdf0806-8476-43af-bce7-47a17343e8f4n@googlegroups.com \
    --to=rhuntsinger-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).