|
From: | Patrice Levesque |
Subject: | SVG style and contributing barrier to entry |
Date: | Thu, 16 Apr 2020 05:00:54 -0400 |
Hi! I just discovered that the “style” tag created inside svg output uses the wrong syntax, e.g. <style text="style/css"> Should be: <style type="text/css"> Reference: https://www.w3.org/TR/SVG/styling.html#StyleElement A trivial one-line patch to fix this (based on git master): diff --git a/scm/framework-svg.scm b/scm/framework-svg.scm index 0abb430fe3..07d4d9e3ec 100644 --- a/scm/framework-svg.scm +++ b/scm/framework-svg.scm @@ -56,7 +56,7 @@ `(viewBox . ,(ly:format "~4f ~4f ~4f ~4f" (third rest) (fourth rest) (fifth rest) (sixth rest)))) - (eo 'style #t '(text . "style/css")) + (eo 'style #t '(type . "text/css")) "<![CDATA[ tspan { white-space: pre; } ")) Wanting to submit this patch, I've looked at the LilyPond Contributor's guide¹, and frankly, I'm amazed by the height of the barrier to entry:
I don't expect to become a LilyPond developer in this lifetime, so the above represents an investment I'm not willing to make. The other option — subscribe to yet another mailing list (bug-lilypond) that I'll need to use for a very limited time span and that will spam me with bug reports I don't care about until I unsubscribe — feels awkward to me. I understand the limited resources the LilyPond team can count on and that dealing with spam wastes lots of precious time. Still, I believe there must be a smoother way to help with the project that doesn't involve such intense commitment. Sorry for the rant, I *love* LilyPond and I've been a faithful user for years, but I can't help but think the above processes likely prevent involvement from irregular contributors like me. Have a nice day, 1) https://lilypond.org/doc/v2.21/Documentation/contributor-big-page.html -- · Patrice Levesque · http://ptaff.ca/ · address@hidden -- |
signature.asc
Description: Digital signature
[Prev in Thread] | Current Thread | [Next in Thread] |