Compact, versatile and simple to implement. What we really need is a format like PNG for vector graphics. Chrome, Firefox and Edge show us a half-transparent red, while Inkscape and QtSvg show a black square.Īll of this stuff made me realize: XML is meant to be an authoring file for vector graphics like xcf or psd which contains not only the final graphic information, but also how that graphic is constructed piece by piece.
#FF000080 isn't a valid SVG color, but it's a valid HTML color. Files can be pulled in from external sources via xlink, file contents could be built by complex scripts, and so on. I thought that at least both files on my Linux machine look the same, but it seems like Firefox doesn't like the font-size specification, while Chrome and Edge do.Īnd there are more and more edge cases which make implementation SVG too complex. Otherwise, the file will look very different on each machine. and you have your final file which has all texts converted to paths. What some of you probably learned by now is that if you want to have a redistributable SVG file, you have to have your authoring file in Inkscape, Illustrator, Batik. Especially if that image contains, as it depends on the system.
SVG is so complex that different implementations of SVG disagree how an image should look. But even without that, implementing both a good XML and CSS parser is a lot of work. What it learned in the process that implementing a new SVG library is hard.įirst of all, SVG is built on top of several other technologies:įor the purpose of static graphics, we can ignore the scripting portion of that. I needed vector graphics for a Zig project and I figured that everyone inluding myself is using SVG.
0 kommentar(er)
