Re: [svg-strokes] … stroke width for subpaths …

Thanks Nikos!

On Thu, May 26, 2016 at 10:31 PM, Nikos Andronikos <
Nikos.Andronikos@cisra.canon.com.au> wrote:

> Hi Susan,
>
> On 27 May 2016, at 1:15 PM, Susan Spencer <susan.spencer@gmail.com> wrote:
>
> Hello SVG-strokes team,
>
> Thanks for your work to develop this recent draft.
>
> I would like to re-open the discussion about supporting the ability to
> define the stroke width separately for each subpath along a closed path.
>
> The stroke width for each subpath would be non-negative, and at least one
> subpath's stroke width would be greater than zero.
>
> My application Valentina (valentina-project.org) could use the ability to
> set narrow seam allowances along an armscye curve, and deep seam allowances
> along a hem. I am also working with AYAB <http://www.ayab-knitting.com/>
> and others to develop knitted patterns.
>
> We are trying to break open the fashion industry with open source tools
> and open data formats, and remove barriers to entry into a very sick
> fashion industry.  It would be superbly fantastic if SVG supported stroke
> widths per subpath. This will help us define patterns in non-proprietary
> formats so that anyone can be a designer or a manufacturer in the 2nd
> biggest industry on the planet.
>
> There may be additional applications for this feature, but even if
> patternmaking were the only beneficiary then the impact would still be
> tremendous.  Everyone on the planet wears clothes.
>
> If you have any questions or comments please feel free to email me.
>
> Again, thanks for your work with SVG specs.
>
>
> Thanks for raising this feature request.
>
> We’re using GitHub now for tracking issues and requests, so I’ve created
> an entry for this.
> See https://github.com/w3c/svgwg/issues/147
>
> I’ll post some comments there.
>
> Nikos.
>
> The information contained in this email message and any attachments may be
> confidential and may also be the subject to legal professional privilege.
> If you are not the intended recipient, any use, interference with,
> disclosure or copying of this material is unauthorised and prohibited. If
> you have received this email in error, please immediately advise the sender
> by return email and delete the information from your system.
>

Received on Friday, 27 May 2016 03:39:04 UTC