-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Thorsten,
could it be that after breaking an inserted or opened SVG in Draw, a
path isn't known any longer as SVG path but as some general manually
closed polygon which is closed and to which different stroking rules
apply than to manually closed SVG paths?
Just for the records a small example:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<svg
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:cc="http://creativecommons.org/ns#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:svg="http://www.w3.org/2000/svg"
xmlns="http://www.w3.org/2000/svg"
version="1.1"
width="210mm"
height="297mm">
<g>
<path
d="m 20,40, 0,-20 80,10 -80,10"
style="fill:none;stroke:#00b300;stroke-width:6;stroke-linejoin:round;st
roke-miterlimit:10;" />
</g>
</svg>
Steps to reproduce:
- - Insert or open SVG
- - Break it (right mouse click in graphic - context menu)
- - Watch the changing stroking
Christina
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJVDSvRAAoJEN/hiApPuw9SRYoH/02+bvPcQbtvtD5d8O48bxgp
D1el7g9SLHHY4p0byFq16F56AjZfVNxALyor2gMhUwBSgCOtV1kmbVZlqW8Vc6Pw
PbhtaNg+SrSDzQcN+nPdl1GmT13NbsEM6Vojzr7GKxagsmE5lUIenhtMdmd3hzrZ
FdFpUikMCtWTs65k17dUDLDmE4JTEEMfiE3RbIw+x726LnWJfJtscSupY5MsHpcH
MsQs95c3xXmrEeLc9YB4v+9Jufa+y2nKKWygTqNYzjZIXsPX2yhOcG5Qm/UGeD1S
fuPXBIcOpuvt0fUx4rtPooG+Ia7I6Ht9Q+jw7J2BQMLVgFWhaltD7Tj8V3dHW0w=
=jVyK
-----END PGP SIGNATURE-----
Context
- SVG & Break · Chr. Roßmanith
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.