[Scilab-users] xs2svg and complex grayplot: room for improvements?

antoine.monmayrant at laas.fr antoine.monmayrant at laas.fr
Wed Aug 22 15:19:13 CEST 2018


Hi all,

xs2svg is not working well with big grayplots: the resulting svg file is 
too big and contains too many elements to be usable. Worse, for really 
big grayplots, the export fails (not enought memory).

As an example, the following code:
     grayplot()
     h=gcf();
     xs2svg(h,'grayplot.svg');
results in a 3.7MB svg file with 93784 elements that cannot be edited 
with Inkscape.

The issue is that xs2svg renders each patch of the grayplot using two 
svg filled triangles.
In "he who must not be named"¹, the svg export is using a more pragmatic 
approach: everything is rendered as svg path/text/whatever, except from 
the intensity maps (grayplots, surf, ...) that are rendered as bmp and 
included in the svg file.
This way, the svg file is really light, can be tweaked with any svg 
compliant software (inkscape) and the result is really good.
In practice, to get publication-quality grayplots, I tend to do the 
following:
-hide the grayplot, keep all the rest, export to svg,
-hide everything but the grayplot, export to png,
-use inkscape to include the png of the grayplot and hand-place it in 
the svg.

Could xs2svg be modified to implement this approach automatically (maybe 
using an optional parameter)?
Could this be the basis for a SEP?

Thanks for you feedback,

Antoine

¹ Matlab


-- 
+++++++++++++++++++++++++++++++++++++++++++++++++++++++

  Antoine Monmayrant LAAS - CNRS
  7 avenue du Colonel Roche
  BP 54200
  31031 TOULOUSE Cedex 4
  FRANCE

  Tel:+33 5 61 33 64 59
  
  email : antoine.monmayrant at laas.fr
  permanent email : antoine.monmayrant at polytechnique.org

+++++++++++++++++++++++++++++++++++++++++++++++++++++++

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.scilab.org/pipermail/users/attachments/20180822/d0af5edd/attachment.htm>


More information about the users mailing list