From: Alan Third <alan@idiocy.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Clément Pit-Claudel" <cpitclaudel@gmail.com>, 34024@debbugs.gnu.org
Subject: bug#34024: Segfault when resizing SVG images
Date: Fri, 11 Jan 2019 09:27:01 +0000 [thread overview]
Message-ID: <20190111092701.GA23164@breton.holly.idiocy.org> (raw)
In-Reply-To: <83muo7hck9.fsf@gnu.org>
On Fri, Jan 11, 2019 at 09:35:02AM +0200, Eli Zaretskii wrote:
> > Cc: 34024@debbugs.gnu.org
> > From: Clément Pit-Claudel <cpitclaudel@gmail.com>
> > Date: Thu, 10 Jan 2019 18:27:53 -0500
> >
> > > And we hope we will soon
> > > have on master image resize capability that doesn't need ImageMagick,
> > > courtesy of Alan Third.
> >
> > This sounds very exciting. I tried the latest master, which IIUC contains (some of?) Alan's changes, but it doesn't fix the issue yet.
>
> Please read the thread discussing Alan's code. I think you are
> supposed to disable ImageMagick to see the native resizing in action.
> Alan, please correct me if I'm wrong.
Yes, at the moment image-mode still defaults to ImageMagick, and
resizing any image will fallback to ImageMagick if available. More
work needs to be done in image.el (and possibly image-mode.el, I only
realised this second file exists last week) to stop it using
ImageMagick when it doesn’t need to.
One thing to note about SVG images is that the native resizing only
handles bitmaps, so the SVG is converted to a bitmap, then resized.
librsvg and the like don’t allow you to resize SVG files when you
convert them to bitmaps, we’d have to use Cairo or something similar
for lossless resizing.
--
Alan Third
next prev parent reply other threads:[~2019-01-11 9:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 22:00 bug#34024: Segfault when resizing SVG images Clément Pit-Claudel
2019-01-10 3:39 ` Eli Zaretskii
2019-01-10 13:39 ` Clément Pit-Claudel
2019-01-10 14:38 ` Eli Zaretskii
2019-01-10 23:27 ` Clément Pit-Claudel
2019-01-11 7:35 ` Eli Zaretskii
2019-01-11 9:27 ` Alan Third [this message]
2019-02-12 19:15 ` Clément Pit-Claudel
2019-02-12 23:00 ` Alan Third
2019-09-24 16:42 ` Lars Ingebrigtsen
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=20190111092701.GA23164@breton.holly.idiocy.org \
--to=alan@idiocy.org \
--cc=34024@debbugs.gnu.org \
--cc=cpitclaudel@gmail.com \
--cc=eliz@gnu.org \
/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.