Not sure yet if it should be implemented as filter or third-party convertor.
Implementation questions:
should it support partial import?
how to choose resulting scheme if it can be implemented in a few different ways?
Not sure yet if it should be implemented as filter or third-party convertor.
Implementation questions:
- should it support partial import?
- how to choose resulting scheme if it can be implemented in a few different ways?
Actually, just loading .svg without any editing abilities should be very easy with svg renderer (in fact, .svg is also supported by <image> tag and thus Image node, but for some reason it is rasterized before transformations).
Actually, just loading .svg without any editing abilities should be very easy with svg renderer (in fact, .svg is also supported by `<image>` tag and thus Image node, but for some reason it is rasterized before transformations).
Not sure yet if it should be implemented as filter or third-party convertor.
Implementation questions:
Would be nice to have not only regular import, but also import node that would extract certain element from .svg file dynamically.
Actually, just loading .svg without any editing abilities should be very easy with svg renderer (in fact, .svg is also supported by
<image>tag and thus Image node, but for some reason it is rasterized before transformations).The best way to implement this would be to use generic transformation language.