The main edit box now supports dead keys on OS X (but sadly still does not support IMEs). The spellchecker now does a much better job of splitting words at the right places rather than assuming that all languages use English's word-splitting rules. InternationalizationĬase-insensitive searching now works correctly with non-latin alphabets, such as Greek and Cyrillic. The color picker now has a slider for alpha. The styling buttons finally have hotkeys, and split line at cursor can have a hotkey assigned. This displays the number of characters on the longest line of the currently selected subtitle (treating only \N as line breaks), and changes the background color if the customizable maximum is exceeded. There is now a basic character counter for subtitles. 3.1 addresses this by adding an option to show the text of the line when you first selected it in addition to the current text of the line, as shown above. One of the common complaints about the removal of committing changes in the 3.0 release is that when editing subtitles or translating subtitles into another language, it's often useful to be able to see the original version of the line as you work. Some of the highlights are: Edit box improvements Better than 3.0, I guess.įor a full list of changes see the changelog. Only eight months later than originally planned this time. 3.2 has reversed this trend somewhat and significantly reduces both the download and install size: While programs naturally grow over time, 3.1 had gotten somewhat excessively large. Other languages which have a similar concept of pending input that needs to be displayed should work as well, but have not been tested as heavily. Japanese input in the main edit box now actually mostly works. More of the visual typesetting tools handle modifying all selected lines at once rather than just the selected line, and the edit box style buttons (bold, italic, colors, etc.) actually try to do the right thing when multiple lines are selected rather than setting all of the selected lines to the active line's text. Improvements to editing multiple lines at once In addition, the lfs and luabins modules are now available in the Automation environment, and the Lua io functions have been patched to support Unicode paths on Windows. This is mostly backwards-compatible with existing scripts, but LuaJIT's parser is a little stricter than standard Lua's. This typically results in them being significantly faster, and gives them access to LuaJIT's powerful ffi. LuaJITĪutomation scripts are now run using LuaJIT in Lua 5.2 mode rather than Lua 5.1. The default thresholds for the coloring are based on English professional subtitling standards, and can be adjusted to more suitable values for other languages in the Interface preferences. The background color of the CPS column gradually transitions towards red as the CPS value gets higher to help you spot lines at a glance. The loading progress is shown in the audio display's scrollbar:Ī new column has been added to the subtitles grid which displays the Characters Per Second (CPS) for each line, to help you avoid having lines which are too long for the viewer to read in the time they are visible. Loading audio files in Aegisub is now done in the background, so that you can continue to use Aegisub while audio is decoding, and can even begin working with the beginning of the audio while the full file is loaded. Some of the highlights are: Background Audio Loading mp4.For a full list of changes see the changelog. However, the frequency at which it crashes gets so ridiculous that several times I’ve nearly quit using it. I am using Aegisub on a mac, and have really enjoyed all the functionality it offers for free.
0 Comments
Leave a Reply. |