emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#44206: closed (28.0.50; SVG image fail to show)


From: GNU bug Tracking System
Subject: bug#44206: closed (28.0.50; SVG image fail to show)
Date: Tue, 10 Nov 2020 10:46:03 +0000

Your message dated Tue, 10 Nov 2020 10:45:05 +0000
with message-id <20201110104505.GB36769@breton.holly.idiocy.org>
and subject line Re: bug#44206: 28.0.50; SVG image fail to show
has caused the debbugs.gnu.org bug report #44206,
regarding 28.0.50; SVG image fail to show
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
44206: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=44206
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: 28.0.50; SVG image fail to show Date: Sat, 24 Oct 2020 22:25:03 -0500
Some SVG images fail to show due to regression caused by:
b42481e22e * | Fix SVG image dimension calculations (bug#44065)

Please find the offending SVG file in attachment (in fact, all custom avatars 
in telega.el are not showing). When opened via `emacs -Q 222.svg`, it shows an 
empty box, with the following message in *Messages*

Invalid image size (see ‘max-image-size’)
Error parsing SVG image ‘(image :type svg :file /tmp/222.svg :scale 1 
:max-width 1229 :max-height 585 :format nil)’


Affected librsvg version: 2:2.50.1-1 in Archlinux, and 2.44.10-2.1 in Debian.

Attachment: 222.svg
Description: SVG



-- 
Sheng Yang(杨圣), PhD student
Computer Science Department
University of Maryland, College Park
E-mail: styang@fastmail.com
E-mail(old): yangsheng6810@gmail.com

--- End Message ---
--- Begin Message --- Subject: Re: bug#44206: 28.0.50; SVG image fail to show Date: Tue, 10 Nov 2020 10:45:05 +0000
On Mon, Nov 09, 2020 at 06:54:22PM -0600, Sheng Yang wrote:
> It has been some time since the last activity on this bug report,
> and the broken SVG display can be annoying for uses that need it,
> e.g. telega users.
> 
> @Alan: Is there any particular reason for not merging your patch to
> the master?

Hi, sorry for the delay, it was pushed to master yesterday.
-- 
Alan Third


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]