tatarize

This may relate to #186

First, let me say currently this is not done by the library. The clip-paths are not actually clips they are rendered clips. So effectively the geometry within the clip-path is...

Should be fixed in the 1.9.4

Yeah, I needed to look more into symbol. I didn't really have a use for it enough to flesh it out with more fully processed objects and I don't think...

Since I wrote this version later and based on libembroidery's work it has a built in encoder and the rest of the tweaks that I realized were needed this is...

The general rule of thumb is that it's a list of coords and type of stitch. I think you can call `getX(index)` and `getY(index)` for each of the various indexes....

https://github.com/EmbroidePy/EmbroideryIO/commit/6711cd91192bf5d845c1fc670bbeb49804b5832c Added in the rest. The indexes are between 0 and `patttern.size()`. So if there's 50 stitches then each of those between 0..49 will have a stitch data.

0.0.2 is released. It might have some better luck. I did some corrections to some parsing especially with regard to names of shapes within the file. If that still fails...