The inkscape converter definition in
./TeXmacs/progs/convert/images/init-images.scm: (converter svg-file postscript-file (:require (url-exists-in-path? "inkscape")) (:shell "inkscape" "-z" "-f" from "-P" to)) is pretty fine; in outputting postscript it is resolution neutral. The rsvg definition (which is preferred by TeXmacs and used during postscript definition) is rotten: (converter svg-file png-file (:require (url-exists-in-path? "rsvg")) (:shell "rsvg" "-f png" from to)) It allows rsvg to choose the generated output size regardless of the TeXmacs global dpi or graphics size. And I find the resolution to be pretty rotten. I think that --dpi-x and --dpi-y should be specified to the global dpi (for the benefit of any px units in the svg) and also -w and -h should be specified as given in the <postscript|...> node. I'm still trying to locate the implementation of the <postscript tag so I can hazard a patch. Best candidate so far is image->postscript in ./TeXmacs/progs/kernel/texmacs/tm-convert.scm but I'm not convinced. In more exciting news I want to add mail-merge sort of stuff to SVG - so I can take a screen shot (maybe from a config screen), import into an SVG and add some named text fields - and then I can re-use the same screen-shot with different config values! Doing with graphics what texmacs makes so easy with text. But this also depends on being able to pass text arguments down to the converter as rsvg needs... Any hints? Sam --
Sam's signature |
Archive powered by MHonArc 2.6.19.