#26 ID3v2 comment field returns extra leading byte

[Geert Vandensteen]

When reading the comment field of the ID3v2 field, there
seems to be an extra byte in the beginning of the String.
You can clearly see this by doing mp3file.getComment
().getBytes().length.
This extra byte is displayed as a square, when
displaying the comment field in a JTable.

[Andreas Grunewald]

Logged In: YES
user_id=571171

We'll work on that first of all i'll try to redesign major
parts of the lib, parallel we will start solving bugs.

[Jan van Oosterom]

Logged In: YES
user_id=661657

The cause is the method: ID3v2Frame.getDataString()
It ignores the "Short content description", so it returns
the fields "Short content description" and "The actual
text", seperated by a 0 byte (the one you "see" in the
JTable) as one String.

This is the definition of the Comment field:

<Header for 'Comment', ID: "COMM">
Text encoding $xx
Language $xx xx xx
Short content description <text string according to
encoding> $00 (00)
The actual text <full text string according to
encoding>