Werner LEMBERG <[email protected]> writes: >>>> It would seem like a better idea to explicitly establish a >>>> documentwide default of currentColor to black explicitly >>>> somewhere. >>> >>> Perhaps a `-dxxx' command-line option? >> >> Anything requiring explicit user effort in order to produce expected >> results is not going to mitigate the damage. > > Mhmm, `damage' is too big a word IMHO. This problem is already fixed > in the latest release of librsvg (and it wasn't present in some > earlier versions about a year ago; at least I was able to submit an > SVG to Wikipedia without any problems), and I believe that at least > Wikipedia will update within the next few months.
So a half-year outage of LilyPond on Wikipedia and a messup of Denemo and a number of other applications is not "damage". > The current default of Lilypond is not wrong, as far as I can see. Shrug. It doesn't matter whether we can nominally justify calling this "somebody else's problem". The fallout still piles up in our backyard. -- David Kastrup _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
