4 ms·
W3C is defining SVG Native [1], which is a subset of the full SVG spec. The plan is to use it in font files and it should be a nice format for native apps. It r
by gardaani 6y ago
W3C is defining SVG Native [1], which is a subset of the full SVG spec. The plan is to use it in font files and it should be a nice format for native apps. It removes support for CSS, the style attribute and lots of extra syntax. Even the XML parsing is made simpler by not requiring support for XML entities. Compression with gzip should create fairly small files.
By reusing the SVG format, it is still compatible with existing tools, such as Adobe Illustrator and Inkscape (meaning that they can open SVG Native files).
Adobe even has an open source renderer for SVG Native [2].
[1] https://svgwg.org/specs/svg-native/ https://svgwg.org/specs/svg-native/
[2] https://github.com/adobe/svg-native-viewer https://github.com/adobe/svg-native-viewer
- masklinn 6y ago> W3C is defining SVG Native [1], which is a subset of the full SVG spec. Cool, that's only the third time they do that (after Tiny and Basic).
- dukoid 6y agoIt's even less than Tiny (= no CSS). I wrote some SVG manually recently and in my opinion SVG is quite fine for that purpose.
- vesinisa 6y agoThey have also defined SVG Tiny, which is basically SVG without CSS and scripting support. Which seems to be more or less what OP is calling for in the blog post. Why the need to reinvent the wheel? For once, we have massive industry-wide momentum behind a unified vector graphics format. It can be very hard to swim against that current.