UTF-16 handling of COMM frames is incorrect

ID3v2CommentFrameData.unpackFrameData attempts to find the description and comment for a COMM frame by searching for terminators.  However, it does this by iterating across the bytes searching for 0.  In the case of UTF-16, any code points below  U+256 (most western text) will cause the termination code to trigger early.  When searching for a terminator in text encoding 1 or 2, you should be grabbing byte pairs, and comparing the pair to 0, rather than searching for a single byte terminator.    See section 4 here:  http://www.id3.org/id3v2.4.0-structure