Change History (7)
comment:1 by , 5 years ago
comment:2 by , 5 years ago
An additional point, when we get to a place where we can think about building this version, is that the release notes suggest some existing svg files might need to be edited. From the Release announcement:
- Librsvg's XML parser now supports namespaces (xmlns), and is stricter than before about it. Files may fail to parse if there are attributes or elements with namespace prefixes (e.g. foo:bar instead of plain bar), but without a corresponding namespace declaration (e.g. xmlns:foo="http://example.com/foo"). This may happen especially with incorrectly-written SVGs that use xlink:href or xi:include attributes without the corresponding namespace declarations. If you run into this, just add the following to your toplevel SVG element: <svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xi="http://www.w3.org/2001/XInclude"> ^^^^^^^^^ these ones
comment:3 by , 5 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
I've been testing this (i.e. opening existing files) in my normal build. I _think_ that firefox picks up librsvg via gtk, and ImageMagick7 ('display') definitely picks up librsvg.
Tests with both of those were ok.
With gimp (librsvg probably pulled in via babl and gegl) tests mostly ok, but one file from the firefox source which I tried, firefox-68.5.0-c1/third_party/python/Click/artwork/logo.svg, reported 'unsupported file format' (other files I tried worked ok.
That file displays ok in 'display', firefox and indeed in inkview (it was created in inkscape).
I also used asymptote to create an svg via dvisvgm, again that opened fine in 'display'.
To me, this looks as if only seamonkey is stopping us from updating to rustc-1.39.0 and then using this version of librsvg.
However, I have not yet managed to build libreoffice (and no useful error messages from that), so I suppose I need to get that built and working before confirming this version of librsvg is ok.
comment:4 by , 5 years ago
For seamonkey, both fedora and slackware (or maybe it was slackbuilds) are using a set of patches, and I got lucky via a link at AUR discussing how to update to 2.53.1 which posted links to patches.
The upstream bug (still at mozilla!) is https://bugzilla.mozilla.org/show_bug.cgi?id=1617782
Will create a ticket for seamonkey.
With rustc-1.39.0, both firefox-68.6.0 and thunderbird-68.5.0 build ok. But seamonkey-2.53.1 does not: