Todd Fleming

I just released it wouldn't get confused. It'd break apart the paths at the intersections then reform them to do this if I add inner-to-outer: 

@jorgerobles I don't understand your question.

reduceCamPaths will need changes. Maybe an earlier function will mark inside-outside relationships and reduceCamPaths will obey the constraints while reordering.

It is a support question because it's a known issue. A closed line represents 0 area, throwing off polygon algorithms. The volunteers at https://plus.google.com/communities/115879488566665599508 know how to instruct new users...

Here's the problem: if I don't lock issues like that one and this one, then they'll continue to attract new users like moths to a flame.

It'd be nice if there was a good way to filter potential contributors from people who just need the support the G+ community provides.

It treats open paths separately since the polygon algorithms can't handle them. That handling isn't nearly as capable, so it doesn't treat closed paths that way.

f0x52's example looked exactly like mistakes new users produce until the volunteers in the community explain how to do it correctly.

That workaround is worth considering.

The advantage of locked is that it doesn't hide it from the default search. I want most new users to go through G+ first, especially with SVG issues.