![]() While this is usually also the version of Aegisub I'm currently using, I make no promises on stability. Partly, this is also because any big refactors would make it harder to pull these changes into upstream repositories or future forks. This fork collects new features and critical bugfixes, but won't be putting extra time into maintenance aspects like cleanup and refactors. Still, the general mission hasn't changed. At this point it's probably too late to still be saying this. It's a collection of new feature additions which I built myself, together with some of the most important new features floating around other forks. I try to convince myself that this isn't really a "fork" in the traditional sense - one which aims to provide extended support and stability fixes. Only PR'ing the changes in here to various forks would cause even more chaos It's the base for this fork, and I hope to one day merge most of these additions into it. The TypesettingTools fork is the one that will one day become the upstream version and builds relatively effortlessly on all operating systems, but at the moment it's not moving much.AegisubDC has the most modern features (in particular video-panning), but is Windows-only and not actively maintained anymore.It's missing most of the modern features. wangqr's fork is actively maintained, but focussing more on stability.None of the existing forks are completely satisfying at the moment: ![]() We absolutely do, and I'm aware that adding another one doesn't sound like a good idea on paper. Don't we have enough Aegisub forks already?
0 Comments
Leave a Reply. |