The development of Automation 4 was much on and off, standing still for months at a time. Lots of people had been crying for other languages, especially Perl and Python, so support for multiple scripting languages went into the core design. Automation 4, unlimited feature works?Īs the flaws of Automation 3 started showing through the design of Automation 4 begun. In the end Automation 3 did prove very successful though and has done a great job. Unfortunately the overall architecture of Automation 3 in the end didn't allow it to be extended either way, and the first rough ideas for Automation 4 started forming. Originally Automation 3 was also intended to be somewhat extensible and down the road support more than just the basic modification of subtitle lines, this is evident from the kind="basic_ass" statement required in all Automation 3 scripts. This proved to work and ended up as the Automation 3 system. Automation 3, back to Lua and something usableĪfter the fiasco of Automation 2 and Python I went "browsing languages" again and ended up going back to Lua, and also went for a much less ambitious design. The main thing to be said about it is that the current Automation 4 achieves everything Automation 2 was intended to be, and even more. I don't think there's much of any proof of the work on Automation 2 left now. Instead I started looking into Lua again and drafting what became Automation 3. It just proved to be an overall bad design (which on hindsight might have been a good thing) and it was never implemented. It was planned to use Python for scripting language and be quite flexible.
Aegisub manual download download#
If you want to try this relic from the museum, you can download it here: Automation 2, the Python engine that never happenedĪutomation 2 was intended to be the scripting system in Aegisub, I drafted the specifications for it while Aegisub was still only in internal pre-alpha development. It basically allowed creating effects similar to what the simple-k-replacer script from Automation 3 does, but in a more complicated and not as usable way. This use of Lua is the primary reason I even call it "Automation 1" today.
It was written in Borland Delphi and used Lua 5.0 for scripting. The Karaoke Effector program was originally created for making karaoke effects for a small translation project, that later died. Automation 1, really just Karaoke Effector Here's a short account of its history, from the principal author of the systems. Add to dictionary - adds the found word to the dictionary so it will not be detected as misspelled again.Īt the bottom of the dialog box there is a dropdown box to choose the spell checker language.Īegisub comes with a whole library of dictionaries, but don't lose hope if your language isn't included with the default installation.The Automation system in Aegisub has evolved from a very basic and hardly useful stand-alone system for creating basic karaoke effects into a very powerful extension mechanism.Ignore All - ignores all instances of this word.
Ignore - ignores this instance of the misspelled word.Replace All - replaces all instances of the found misspelled word in the entire script with the chosen replacement.Replace - replaces the found misspelled word with the chosen replacement.The area in the lower left of the box displays suggestions to replace the misspelled word with to the right there are a number of buttons: The spell checker dialog will go through all misspelled words it can find in your script. It also spell-checks as you type and can to some degree be controlled from the subtitle edit box's right-click menu (see editing subtitles). It can be found in the Subtitles menu -> Spell Checker. It uses the Hunspell library, which is based on 's MySpell, which means it's at least as good as one you'd find in a sophisticated word processing program. To help you with quality assurance of your subtitle scripts, Aegisub features a complete spell checker.
0 kommentar(er)
