Josh Hatwich

Here is the one I was looking at where I noticed it first... (could be other issues at play too)... https://drive.google.com/a/601t.com/file/d/0B1M3zV5eEym9OVlvdk5nNk1mdTg/edit?usp=sharing

For simple shapes it seems like we could work-around by writing the equivalent raw path and compare it to see if has been transformed... hackey, but seems like it might...

blocked on the generator-core bug. considering adding an errors.txt warning.

@dirkschulze suggestion seems good to me. I think keeping the definition compatible with Ai will be a theme for 2015!

Renamed from Empty to Inaccurate since it isn't empty any more but it isn't right either :bug:

@dirkschulze do you think we should make a preference where-by we rasterize any layers we know to be unsupported?

Seems reasonable to me.

I think this one is fixed, please close it if you agree @dirkschulze

@dirkschulze is this in the case when we are isolating a single layer or for a whole document? I don't see the problem if I do an isolated layer export...

We are padding the bounds appropriately, but the path is not positioned properly within the bounds. This only affects paths, not simple shapes. We should probably stop using the pre-computed...