- From: Dr. Olaf Hoffmann <Dr.O.Hoffmann@gmx.de>
- Date: Fri, 9 Oct 2009 13:06:37 +0200
- To: www-svg@w3.org
Hello, yes, I have such problems too. Especially already years ago I created a PHP script to clean up path data created by potrace+inkscape, because I did not find a possibility to specify the number of digits required for my application. To reduce file size for some applications I do additionally a combination of transform scale and an internal multiplication of path data to get the data in a range with less required digits and a range, where precision errors of viewers are not so dominant (notwithstanding to specification the precision of several viewers depend directly on the number range of the path data). I think, some programs do such (arbitrary?) scaling and even metamorphoses from basic shapes to arbitrary path data too, without understanding the purpose or importance of the current appearance of data. On the other hand it is annoying, if authoring tools change already optimised code without any notification or agreement from the current author. For many authors might be important to have influence on such changes too, just to avoid a loss of semantical meaning and to avoid a 'pessimisation' by such scripts and programs. Not simple to solve this maybe and more an issue for such programs changing existing code to ask the user interactively about the purpose of the code instead of changing everything without knowing the purpose of the already existing code. On the other side, if an author runs such an optimisation script as mine for known content there are not many problems and such an attribute including a hint is more useful to bring back to mind, why things were done with such a result in the past. As long as there is no such indication within current SVG versions, there is more than one option to indicate this anyway: 1. An extension using its own namespace 2. Using information embedded in the metadata element. 3. Using RDFa attributes (as available already in SVG tiny 1.2) referring to an external specification for some 'precision markup'. Well, someone has to write such a specification or proposal - as a first step maybe already useful to see what can be embedded later into SVG directly? Olaf
Received on Friday, 9 October 2009 11:14:26 UTC