Split glyph runs early

The "bitmap runs" that are currently used only when combining bitmaps
are also relevant at other stages, mainly for VSFilter compatibility.
They are not currently used because this information is not available
until bitmap combining (except during shaping, which has its own "shape
runs" that duplicate a good chunk of the "bitmap run" logic).

Move some code around to compute run boundaries as early as possible.
This lays the foundation for future commits that will make use this
information in more places where it can simplify code or improve
VSFilter compatibility.

For VSFilter compatibility, rather than break runs immediately upon line
breaks, break runs after line-leading whitespace, even in the first line.

These runs correspond to VSFilter's CWord instances.

1 files changed, 0 insertions, 1 deletions

diff --git a/libass/ass_parse.c b/libass/ass_parse.c
index 4134987..bb6fcff 100644
--- a/libass/ass_parse.c
+++ b/libass/ass_parse.c
@@ -1016,7 +1016,6 @@ void process_karaoke_effects(ASS_Renderer *render_priv)
                     cur2->effect_type = s1->effect_type;
                     cur2->effect_timing = x - d6_to_int(cur2->pos.x);
                 }
-                s1->effect = 1;
             }
         }
     }