Arnav Singh

It's not impossible, though it will require the codegen process to keep track of cross-module dependencies. Eg everything depends on meta/v1, so enabling anything else should also enable the meta/v1...

The build step uses the typescript compiler API rather than `tsc` directly to add JSDoc annotations to the output (`@constructor`, `@enum`, `@memberof`, etc) and for generating the docs, both of...

>So I need to update the build step to use the new compiler API in order to make it work with the new Typescript version. To clarify what I said,...

In terms of priorities, the work is: 1. Update TS to current version, even if at the cost of not having custom build steps for docs or synthesized JSDoc comments....

Yes, the only properties parsed for Events are Style, Start, End, Layer and Text. So MarginL, MarginR and MarginV (and other style properties in general) are ignored. The only workaround...

The quirk with how this library is compiled is that it's written as modules but the release is a single JS object with everything loaded up-front. The eager-loading is intentional...

Yes, every `Dialogue` serializes its own copy of a `Style` object, so the deserialized `Dialogue` has an independent `Style` object unrelated to the one deserialized into `ASS.styles`. One way to...

I'll keep this open since it's a bug. You can unsubscribe from it if you don't want notifications.

Yes, it applies the outer margin (bottom margin for \an2, etc.) to every dialogue, whereas VSFilter / libass only apply it to the outermost dialogue and use no margin for...

Actually, the real behavior is more complex. The margin is always applied from the bottom of the viewport. If you have two subs in \an2 with vertical margin == 20px,...