From: Eli Zaretskii <eliz@gnu.org>
To: Evgeny Zajcev <lg.zevlg@gmail.com>
Cc: 59075@debbugs.gnu.org
Subject: bug#59075: 29.0.50; Image transforms not applied to svg images
Date: Sun, 06 Nov 2022 14:33:30 +0200 [thread overview]
Message-ID: <83leoo1cv9.fsf@gnu.org> (raw)
In-Reply-To: <CAO=W_Zp4tSV3qTDQ1usD4kKuY5Qr3uC86uP2Ob8RaY4k6wHFTw@mail.gmail.com> (message from Evgeny Zajcev on Sun, 6 Nov 2022 14:52:17 +0300)
> From: Evgeny Zajcev <lg.zevlg@gmail.com>
> Date: Sun, 6 Nov 2022 14:52:17 +0300
> Cc: 59075@debbugs.gnu.org
>
> If this is caused by upgrading to a newer librsvg, why are you certain
> that it's an Emacs bug and not a librsvg bug?
>
> Newer librsvg is known to have few bugs that we have already reported to the librsvg community.
> However, in this particular case I'm not sure this is caused by librsvg side, why transforms starts to apply
> after changing image type in the image spec?
I don't know. I'm not sure it's a librsvg bug, I'm just saying it
could be theirs as well as ours. We need a librsvg expert to tell.
Anyone?
next prev parent reply other threads:[~2022-11-06 12:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-06 10:16 bug#59075: 29.0.50; Image transforms not applied to svg images Evgeny Zajcev
2022-11-06 11:02 ` Eli Zaretskii
2022-11-06 11:52 ` Evgeny Zajcev
2022-11-06 12:33 ` Eli Zaretskii [this message]
2022-11-06 13:02 ` Stephen Berman
2022-11-06 16:07 ` Evgeny Zajcev
2022-11-06 16:50 ` Stephen Berman
2022-11-07 0:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-07 10:26 ` Evgeny Zajcev
2022-11-07 12:21 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-07 12:24 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-12 9:48 ` Evgeny Zajcev
2022-11-12 11:04 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-13 8:57 ` Evgeny Zajcev
2022-11-13 9:31 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=83leoo1cv9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=59075@debbugs.gnu.org \
--cc=lg.zevlg@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.