Added a new COMM field to test.mp3 in UTF-16 with the Description: "✓"
and text "✓". Opening and closing it two times without a panic should
ensure that it is working.
Also added a few lines to the open test to explicitly test to make sure
that these UTF-16 fields are being read properly.
Previously when trying to write a null terminated string it simply wrote
a single 0 byte for the null character. This fails for utf16 where the
null character is two bytes of zeros.
fixed the way that we WriteNullTermString with utf16
Originally this function was just writing a 0x00 byte, which does not
work for utf16.
fixed mistake when merging changes
- change encodedBytes.Reader's ReadNullTermString behavior to strip off
null byte(s)
- add WriteNullTermString function to encodedBytes.Writer
- include NullLength information in encodingbytes.EncodingMap
- increase size of UnsynchTextFrame by the null length of the encoding
- automatically null-terminate description string in
UnsynchTextFrame.Bytes()
casept