I’m not saying svgo is worse than scour or svgcleaner, I’m just saying there exist three opimizers, which each one having their own advangages. Recommending without mentioning scour is absurd, since scour is a build-in-function, just save it as “Optimized SVG (*.svg)”, no need for installing anything additionally. Svgcleaner is much faster (whith the same cleaning ratio) als svgo, see
Scour and svgcleaner can be used to repair damaged (or wrong rendered) SVGs in which svgo imho can’t (few exceptions). Please read it has usefull information of different optimization tools (instead of one using in several implementations). Svgo is reported in as not developed any more, which is confimed by the developer: svgo is imho the bugiest one (at least for wikimedia-files) of those three optimizers. All three are not (actively) developed/bugfixed any more see References in. There are three (not one) common command-line-tools: scour, svgcleaner and svgo.
0 kommentar(er)
