OOUI's svgo-optimized SVG files are not compatible with rsvg's broken SVG parsing.
svgo emits SVG like <path d="M-1-2 …"> or <path d="M.3.5 …"> which rsvg is unable to parse (this is valid path data fragment that represents a points (-1; -2) and (0.3; 0.5), and the SVG 1.1 spec even explicitly discusses this syntax). The same issue affects ImageMagick when compiled with rsvg support.
This means that some of OOUI's and VisualEditor's icons will not appear correctly e.g. when uploaded to Commons, and blocks T76473: Implement ResourceLoader module to ship CSS for sets of SVG+PNG icons to the user since we're unable to rasterize the SVGs to PNG.
This can be worked around using some search-and-replace, but this leaves some questions:
- Can this be fixed in rsvg? Gotta file a bug, even if it'll probably be ignored, and even if not no one is going to upgrade their copy.
- Where do we apply the workaround? To the files in git? During build process? In MediaWiki's RL module from T76473?
- Should we maintain the workaround ourselves somewhere, or maybe it could be upstreamed to svgo? (As a command-line option for people who want rsvg compatibility at the cost of a few bytes, like us?)