unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 44065@debbugs.gnu.org, Sheng Yang <styang@fastmail.com>
Subject: bug#44065: 28.0.50; SVG image not shown completely
Date: Sun, 18 Oct 2020 18:24:58 +0200	[thread overview]
Message-ID: <874kmrijs5.fsf@gnus.org> (raw)
In-Reply-To: <83pn5fqzqc.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 18 Oct 2020 19:13:15 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> Does anyone else succeed in reproducing the problem?

The svg image is cropped for me (Debian bullseye) to the right in Emacs
28.  Firefox displays it correctly, but Imagemagick display refuses to
show the image:

larsi@xo:~/src/emacs/trunk$ display /tmp/1.svg
display-im6.q16: must specify image size `/tmp/magick-GeZIabcfFHYCvUwmkbtM-oODO_uzDIU-' @ error/mvg.c/ReadMVGImage/186.


-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2020-10-18 16:24 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 [this message]
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
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874kmrijs5.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=44065@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).