- From: Paul LeBeau <paul.lebeau@gmail.com>
- Date: Sun, 16 Jun 2013 01:55:17 +1200
- To: www-svg <www-svg@w3.org>
- Message-ID: <CACfsppDnASt6jbucyvaoyPraAS6cQEDbhjoNOBdYce3Y=wu=BA@mail.gmail.com>
Err. Okay then :) Thanks you for correcting the misunderstanding. On 15 June 2013 23:19, Dr. Olaf Hoffmann <Dr.O.Hoffmann@gmx.de> wrote: > Hello, > > just to avoid misunderstandings. > In the definition of the stroke proptery it is defined, that > "A subpath (see Paths) consisting of a single moveto shall not be stroked." > http://www.w3.org/TR/2011/REC-SVG11-20110816/painting.html#StrokeProperty > > Of course stroke-linecap applies only to stroked subpaths: > "‘stroke-linecap’ specifies the shape to be used at the end of open > subpaths > when they are stroked.' > > http://www.w3.org/TR/2011/REC-SVG11-20110816/painting.html#StrokeLinecapProperty > > > Therefore in the following path only the last subpath results in a visible > presentation, if stroke-linecap is round or square, but not the previous > moves: > d="M50,50m1400,-1200m-500,-200 0,0" > This notation of two or more m-commands can be pretty useful to move > around larger amounts of path data containing only relative commands, > possibly realised with path fragments represented by own entities. > The rule above ensures, that these additional moves have no > visual residuals... > > On the other hand the following path creates three stroked subpaths > of zero length, which become visible, if stroke-linecap is round or > square: > d="M50,50 50,50m1400,-1200 0,0m-500,-200 0,0" > > > Olaf > > -- Phone: +64 3 9423700 / Mobile: +64 21 1666127 Skype: paul.lebeau / XMPP: paul.lebeau@gmail.com Twitter: @paullebeau
Received on Saturday, 15 June 2013 13:56:03 UTC