Christina Roßmanith wrote:
> Then for the mixed case the problem could be solved by iterating
> over the polypolygon and calling writePathShape() with each
> individual subpolygon. Or are there reasons not to proceed this way?
>
Ah, good point - indeed that would be the best way around this. There
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 08.11.2015 um 01:43 schrieb Thorsten Behrens:
> Christina Roßmanith wrote:
>> I'm revisiting tdf#51165. It looks like rendering is the
>> problem, not importing the SVG file. To continue I'd need some
>> code pointers where rendering is implemented.
Christina Roßmanith wrote:
> I'm revisiting tdf#51165. It looks like rendering is the problem,
> not importing the SVG file. To continue I'd need some code pointers
> where rendering is implemented.
>
Hi Christina,
oh, this is an interesting corner case - the polypolygon in the bugdoc
has both cl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I'm revisiting tdf#51165. It looks like rendering is the problem, not
importing the SVG file. To continue I'd need some code pointers where
rendering is implemented.
Christina
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)
iQE
