From: Eli Zaretskii <eliz@gnu.org>
To: Jim Porter <jporterbugs@gmail.com>
Cc: george@feyor.sh, 71913@debbugs.gnu.org
Subject: bug#71913: 29.1; shr: shr-resize-image does not behave as expected
Date: Fri, 12 Jul 2024 08:58:44 +0300 [thread overview]
Message-ID: <86zfqnkv6z.fsf@gnu.org> (raw)
In-Reply-To: <a4a59311-ee79-6ee5-f20d-087a23f8f6fb@gmail.com> (message from Jim Porter on Thu, 11 Jul 2024 16:51:53 -0700)
> Cc: 71913@debbugs.gnu.org
> Date: Thu, 11 Jul 2024 16:51:53 -0700
> From: Jim Porter <jporterbugs@gmail.com>
>
> On 7/10/2024 12:02 PM, George Huebner wrote:
> > As I understand it, this decision was likely made because the dimensions
> > of SVGs is weird; they aren't inherently required to have a size, but
> > the SVG itself can define a viewbox with accompanying width and height
> > (full disclosure: I have no idea what I'm talking about).
>
> I think this was just a mistake. I tried getting rid of the special case
> for SVG and everything works just fine in builds with or without SVG
> support. (In builds without SVG support, you just get the empty string
> where an SVG would be, before and after this patch.)
What version of librsvg did you test this with? Please test also with
librsvg 2.40.x, as that was the last version which didn't need a Rust
compiler to build, and so some people (including yours truly) stay
with those old versions to this day.
Thanks.
next prev parent reply other threads:[~2024-07-12 5:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 6:37 bug#71913: 29.1; shr: shr-resize-image does not behave as expected George Huebner
2024-07-03 15:48 ` Jim Porter
[not found] ` <m25xtmz0fj.fsf@feyor.sh>
2024-07-05 18:11 ` Jim Porter
2024-07-10 19:02 ` George Huebner
2024-07-11 23:51 ` Jim Porter
2024-07-12 5:58 ` Eli Zaretskii [this message]
2024-07-13 4:11 ` Jim Porter
2024-07-13 6:20 ` Eli Zaretskii
2024-07-13 17:29 ` Jim Porter
2024-07-13 17:39 ` Eli Zaretskii
2024-07-13 18:54 ` Jim Porter
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=86zfqnkv6z.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=71913@debbugs.gnu.org \
--cc=george@feyor.sh \
--cc=jporterbugs@gmail.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.