>> Well, we are not in the market for SVG compliance testing. If >> there are reasonably simple changes we can make to LilyPond in >> order to avoid/sidestep triggering this librsvg bug, > > I don't know about *this* bug,
BTW, can you reproduce the problem that I've shown in my previous
e-mail?
Werner
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
