The new v0.5.5.5381 testing release brings some exciting new features and enhancements. Remember that this is a testing release, and may contain more bugs than non-testing releases, though it should be very usable as it is.
Support for multiple hash display encodings: In addition to the traditional hexadecimal encoding, MIME Base 64, UUEncode, and XXEncode are now supported. When using the FVA and FVB file formats, information about the displayed encoding is retained, so that hashes are displayed in the intended encoding upon opening. Currently, the encodings are always stored in Hexadecimal encoding in FVA/FVB files, for backwards compatibility with older program version (though this may change in the future, as the program does currently detect other encodings when properly indicated). All other file formats use Hexadecimal encodings, as those formats are specific to other applications that do not support the format (except for CSV, which does not support the change yet either).
Support for BSD CKSUM formatted files: Files created by common BSD utilities such as cksum, md5, sha1, etc. are not in the same format as those created by md5sum, sha1sum, etc. These formats are now supported, for both reading and writing. The program will also automatically detect the format, unless explicitly given the format to use.
Reduction of flicker: Previous versions of the GUI client have had issues with flickering when resizing the main application window. Flicker has been nearly eliminated. There may be times when the window is not always repainted in certain small areas, but these instances are not common or very noticeable, and they have no impact on the usability.
Changes in names of certain algorithms: The names of several algorithms have changed. For example, SHA-1 is now known as SHA1, RIPEMD-160 is now known as RMD160, etc. This was done to improve compatibility with the BSD cksum tool and related programs. This will NOT break existing FVA, FVB, or CSV files, as the program will now accept several aliases for each algorithm. For example, RMD-128, RIPEMD128, and RIPEMD-128 all are aliases for RMD128, and the verification will work as expected.
Several other minor enhancements have been made. See the CHANGELOG for further details.