>> It's not completely off the table, but it seems to me that >> `svgnative' is preferable. > > Given that we want a pluggable renderer, the whole discussion is > moot.
It's not moot at all IMHO. I want to have a default that has as few dependencies as possible and is flexible. And `svgnative' seems like an ideal candidate for that. If people are going to use something else, they have to override the default. Of course, the forthcoming callback API should be generic enough to allow a broad range of libraries – please follow Moazin's attempts in the next few months and chime in in case you think something is missing or done in a non-optimal way. > For pangocairo, we're going to want to plug librsvg. You want that because you are going to use the `librsvg' (within pangocairo) for other purposes also? > First, SVG Native is still being designed. Nothing is set in stone. > As it is, it doesn't have many features. Patterns are out. Filters > are out. Anything other than simple gradients is out basically... > See my comment and Dirk's response at the bottom of this article: > > https://medium.com/adobetech/svg-native-open-sourcing-svg-native-viewer-988125328a07 > > Now, some would claim that that's exactly what is allowed in > OpenType. Again, that's what we will be discussing to make happen. > As it happens, there is no relationship between OpenType and SVG > Native. OK. Werner _______________________________________________ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
