Oleg Oshmyan

@MrSmile, do _you_ maybe have an idea how we could detect zero-area (sub)shapes and avoid stroking them? Maybe there’s a way you could do it directly in the stroker.

> The other examples I posted and then deleted were indeed fixed in recent versions of libass, possibly commit ad6510b. I think it was pull request #236. At least the...

>> I think “zero-area” is pretty clearly defined. > > It's not. Given that coordinates are floating-point, area is floating-point too and checking floating-point numbers for exact equality is common...

Oh, so, looking at the title of this issue and given that the other examples of already-fixed bad stroking have been removed, I guess this is technically a duplicate of...

> But physically it's not and I consider rendering more on physics (optic) side. This discussion is getting out of hand :-) When I say “zero”, I usually mean zero,...

> All samples in this issue is not 2-point contours. It's coinciding lines from the same or different contours. While handling of 2-point contours is simple and straightforward, general case...

> If I'm reading that correctly, then we can probably just treat any case of an m followed by another m as an l Nope. - An `m` followed by...

It is impossible to have multiple `\pos` tags per Dialogue event. Just split them into multiple Dialogue events. Given that every one of your lines has a `\pos`, this is...

Ah, if this is still blocked on something (32-bit x86 asm), can we merge the non-blocked parts in the meantime?

The ASS consists of the exact same event repeated 596 times with the only differences being the primary colour (but not alpha) and rectangular clip, and with the clips animated...