>From just looking at files, one thing to consider is that this has > changed from 1.4.x to 1.5.x. Basically what POCOOR is doing is > describing the path for an object, so in 1.4.x we might have this for a > text frame (units in points): > >POCOOR="0 0 0 0 256 0 256 0 256 0 256 0 256 72 256 72 256 72 256 72 0 72 >0 72 0 72 0 72 0 0 0 0 " > > Starting from the left-upper corner, we go to the X position at 256 > points, 0 points in the Y, then stay at 256 points X position, move to > 72 points Y position, after that completing the frame back to 0,0. What > I don't understand are the duplications of the numbers, which to me > looks like some eclectic invented thing unique to Scribus.
Thanks for the answer. It looked bit mysterious when I looked to files. > In 1.5.x we now have a more sensible plan as in SVG, so POCOOR has > become path: > > path="M0 0 L256 0 L256 72 L0 72 L0 0 Z" > > This would be a valid SVG description for this rectangular object, M > being the starting point, L denotes a (straight) line, and Z the end of > the path. > > I would recommend therefore that you go with the 1.5.x syntax and forget > about POCOOR. OK. I will wait till 1.5 release and I will support only 1.5.x files. I have already written map > SVG conversion, so I will have bits of code for free. -- Mikol?? ?trajt / Sever?k / http://severak.svita.cz/
