From: Alan Third <alan@idiocy.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 44065@debbugs.gnu.org, larsi@gnus.org, styang@fastmail.com,
stephen.berman@gmx.net
Subject: bug#44065: 28.0.50; SVG image not shown completely
Date: Wed, 21 Oct 2020 20:03:46 +0100 [thread overview]
Message-ID: <20201021190346.GA47992@breton.holly.idiocy.org> (raw)
In-Reply-To: <83ft67mth5.fsf@gnu.org>
On Wed, Oct 21, 2020 at 07:31:02PM +0300, Eli Zaretskii wrote:
> > Date: Tue, 20 Oct 2020 20:54:44 +0100
> > From: Alan Third <alan@idiocy.org>
> >
> > I suppose if we're very concerned about it, we can remove the ability
> > to resize and set colours when using librsvg < 2.45 and therefore get
> > rid of this bug everywhere.
>
> Sounds too drastic to me. The bug seems to affect rare images, and
> then only crops a few pixels (I initially didn't even see the
> cropping). By contrast, losing the background feature is quite a
> loss. And with my relatively ancient version of librsvg I see the bug
> even before the face background feature was installed, so this is not
> a regression for me.
That seems fair. I'd forgotten that the cropping is visible even with
the old code.
> Can't we just say this bug will persist unless new enough librsvg is
> used?
Should I put that note in documentation somewhere or just leave it as
a comment in the code?
--
Alan Third
next prev parent reply other threads:[~2020-10-21 19:03 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-17 23:27 bug#44065: 28.0.50; SVG image not shown completely styang
2020-10-18 15:17 ` Eli Zaretskii
2020-10-18 16:02 ` Sheng Yang
2020-10-18 16:13 ` Eli Zaretskii
2020-10-18 16:24 ` Lars Ingebrigtsen
2020-10-18 17:03 ` Eli Zaretskii
2020-10-18 17:42 ` Stephen Berman
2020-10-18 17:48 ` Eli Zaretskii
2020-10-18 18:00 ` Stephen Berman
2020-10-18 18:03 ` Eli Zaretskii
2020-10-19 8:43 ` Lars Ingebrigtsen
2020-10-19 9:10 ` Stephen Berman
2020-10-19 20:43 ` Alan Third
2020-10-19 22:34 ` Sheng Yang
2020-10-20 12:31 ` Alan Third
2020-10-20 17:15 ` Sheng Yang
2020-10-20 19:54 ` Alan Third
2020-10-21 10:54 ` Lars Ingebrigtsen
2020-10-21 15:58 ` Corwin Brust
2020-10-21 16:31 ` Eli Zaretskii
2020-10-21 17:28 ` Sheng Yang
2020-10-21 19:03 ` Alan Third [this message]
2020-10-22 11:42 ` Lars Ingebrigtsen
2020-10-22 12:51 ` Eli Zaretskii
2020-10-22 19:11 ` Alan Third
2020-10-19 14:51 ` Eli Zaretskii
2020-10-18 19:18 ` Sheng Yang
2020-10-18 23:13 ` Alan Third
2020-10-23 20:17 ` Andy Moreton
2020-10-24 7:09 ` Eli Zaretskii
2020-10-24 17:01 ` Alan Third
2020-10-24 17:04 ` Eli Zaretskii
2020-10-24 10:43 ` Andy Moreton
2020-10-25 12:26 ` Andy Moreton
2020-10-25 16:25 ` Alan Third
2020-10-25 17:12 ` Andy Moreton
2020-10-25 17:27 ` Eli Zaretskii
2020-10-25 23:12 ` Alan Third
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=20201021190346.GA47992@breton.holly.idiocy.org \
--to=alan@idiocy.org \
--cc=44065@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=stephen.berman@gmx.net \
--cc=styang@fastmail.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.