build: use --export-png to support Inkscape 0.9.x #1

Merged
shizmob merged 1 commit from main into main 2021-04-20 08:29:50 -05:00
shizmob commented 2021-01-15 15:59:46 -06:00 (Migrated from github.com)

Older Inkscape versions do not have -o, only -e/--export-png.
Inkscape 1.x seems to have removed -e, but retained --export-* for backwards compatibility

Older Inkscape versions do not have -o, only -e/--export-png. Inkscape 1.x seems to have removed -e, but [retained --export-* for backwards compatibility](https://gitlab.com/inkscape/inkscape/-/blob/INKSCAPE_1_0_1/src/inkscape-main.cpp#L153)
marcan (Migrated from github.com) approved these changes 2021-01-23 07:04:43 -06:00
marcan commented 2021-01-23 07:05:04 -06:00 (Migrated from github.com)

Looks good, but please fix the conflict :)

Looks good, but please fix the conflict :)
baryluk commented 2021-02-05 03:42:44 -06:00 (Migrated from github.com)

Hmm. On the topic of inkscape. Maybe consider cairosvg -f png -d DPI ... -o OUTPUT INPUT, or resvg (rendersvg - older versions used cairo or Qt, newer ones used Skia, but not it uses pure Rust's tiny-skia). resvg is extremely robust, conformant and fast.

Just informing. If it works then it works :)

Hmm. On the topic of inkscape. Maybe consider `cairosvg -f png -d DPI ... -o OUTPUT INPUT`, or resvg (`rendersvg` - older versions used cairo or Qt, newer ones used Skia, but not it uses pure Rust's `tiny-skia`). resvg is extremely robust, conformant and fast. Just informing. If it works then it works :)
Sign in to join this conversation.
No description provided.