From: Lars Ingebrigtsen <larsi@gnus.org>
To: ynyaaa@gmail.com
Cc: 26978@debbugs.gnu.org
Subject: bug#26978: 25.2; incomplete display of SVG image
Date: Thu, 26 Sep 2019 17:37:10 +0200 [thread overview]
Message-ID: <87lfubrrvd.fsf@gnus.org> (raw)
In-Reply-To: <8760gyeb4l.fsf@gmail.com> (ynyaaa@gmail.com's message of "Thu, 18 May 2017 19:02:18 +0900")
ynyaaa@gmail.com writes:
> test-svg/appearance-png.png is for test-svg/sample-png.svg
> (a scaled emacs icon, expected image).
The file is:
<svg xmlns="http://www.w3.org/2000/svg" width="100" height="100"
xmlns:xlink="http://www.w3.org/1999/xlink">
<rect fill="blue" width="100" height="100"/>
<image xlink:href="emacs.png" width="100" height="100"/>
</svg>
If we change that to an absolute path (and add the "file://" bit), it
does display correctly here on this Debian Buster machine:
<svg xmlns="http://www.w3.org/2000/svg" width="100" height="100"
xmlns:xlink="http://www.w3.org/1999/xlink">
<rect fill="blue" width="100" height="100"/>
<image xlink:href="file:///tmp/test-svg/emacs.png" width="100" height="100"/>
</svg>
As Eli says, it's probably due to differences in SVG libraries and what
they allow. But interestingly enough, using "display" on the original
file works, and "display" uses rsvg, too. (Emacs uses rsvg, right?)
So I'm wondering whether there's something we can tell the rsvg library
to make it find these sub-images, or something. I mean, we could also
pre-process the SVG files, but that's more than a bit hacky...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-09-26 15:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 4:24 bug#26978: 25.2; incomplete display of SVG image ynyaaa
2017-05-18 4:55 ` Eli Zaretskii
2017-05-18 5:19 ` Eli Zaretskii
2017-05-18 10:02 ` ynyaaa
2017-05-18 15:34 ` Eli Zaretskii
2019-09-26 15:37 ` Lars Ingebrigtsen [this message]
2019-09-26 15:50 ` Lars Ingebrigtsen
2019-09-26 15:53 ` 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
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=87lfubrrvd.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=26978@debbugs.gnu.org \
--cc=ynyaaa@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 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).