On Wed, Jun 22, 2011 at 18:01, Jasper van de Gronde <th.v.d.gronde@...226...> wrote:
... What you can do is to force Inkscape to use absolute coordinates and convert those to relative coordinates yourself when processing them. Also
Alright then, if this is the only way then this is it, we'll have to live with this. I guess a dedicated script could be written to parse the path string and fiddle with the numbers only... although I'd need to make sure the right coordinates are calculates at each point.
- indeed, many times I get values like "113.000006" (in which case I am
manually editing my path -- counterproductive) or perhaps even more confusing values such as "4.35838e-5"... which is practically equal to zero.
Without knowing exactly how such values are produced it is hard to tell where the problem lies, but such values are not uncommon, nor unexpected. Basically there is no way for Inkscape to know that you did not actually mean to have such values.
Oh, that's very simple: in my case, I get these values when snapping to grid. Simply, I take a path away from its fixed coordinates, then move it back with snap to grid... my impression was that snapping makes the coordinates exact, but I might not understand very well how it works.
The reason for which I need the shortest possible string is to use it in a webpage via Javascript code. As the number of objects tends to increase as the webpage gets more and more complicated, I am concerned with loading time.
Nevertheless, Inkscape is a great program and (besides these trivial and manually correctable issues), it answers all my current needs.
Best wishes, Adrian