<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hello Antoine,<br>
<br>
Le 22/08/2018 à 15:19, <a class="moz-txt-link-abbreviated" href="mailto:antoine.monmayrant@laas.fr">antoine.monmayrant@laas.fr</a> a écrit :<br>
</div>
<blockquote cite="mid:c75c5a87-1882-0365-4b4a-83fa3e22854e@laas.fr"
type="cite">
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
<p>Hi all,</p>
<p>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).<br>
</p>
<p>As an example, the following code:<br>
grayplot()<br>
h=gcf();<br>
xs2svg(h,'grayplot.svg');<br>
results in a 3.7MB svg file with 93784 elements that cannot be
edited with Inkscape.<br>
</p>
<p>The issue is that xs2svg renders each patch of the grayplot
using two svg filled triangles.<br>
In <span class="quote">"he who must not be named"</span>¹, 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.<br>
This way, the svg file is really light, can be tweaked with any
svg compliant software (inkscape) and the result is really good.<br>
In practice, to get publication-quality grayplots, I tend to do
the following:<br>
-hide the grayplot, keep all the rest, export to svg,<br>
-hide everything but the grayplot, export to png,<br>
-use inkscape to include the png of the grayplot and hand-place
it in the svg.</p>
</blockquote>
<br>
Do you remember Calixte's answer to you about this topic in 2012?:<br>
<a class="moz-txt-link-freetext" href="http://bugzilla.scilab.org/show_bug.cgi?id=11195#c1">http://bugzilla.scilab.org/show_bug.cgi?id=11195#c1</a><br>
<br>
Cheers<br>
Samuel<br>
<br>
</body>
</html>