Enhancement to ID3v2.x TCON frame

[GoogleCodeExporter]

ID3v1.1 has a numeric Genre. In ID3v2.x you should have the genre string
set to tcon->text, or possibly with a proper reference to ID3v1.1 genre.
Here's the v2.3 specs about it:

   The 'Content type', which previously was stored as a one byte numeric
value only, is now a numeric string. You may use one or several of the
types as ID3v1.1 did or, since the category list would be impossible to
maintain with accurate and up to date categories, define your own.

   References to the ID3v1 genres can be made by, as first byte, enter "("
followed by a number from the genres list (appendix A) and ended with a ")"
character. This is optionally followed by a refinement, e.g. "(21)" or
"(4)Eurodisco". Several references can be made in the same frame, e.g.
"(51)(39)". If the refinement should begin with a "(" character it should
be replaced with "((", e.g. "((I can figure out any genre)" or "(55)((I
think...)". The following new content types is defined in ID3v2 and is
implemented in the same way as the numerig content types, e.g. "(RX)". 

And here's the v2.4 specs about it:

   The 'Content type', which ID3v1 was stored as a one byte numeric value
only, is now a string. You may use one or several of the ID3v1 types as
numerical strings, or, since the category list would be impossible to
maintain with accurate and up to date categories, define your own. Example:
"21" $00 "Eurodisco" $00

Parse this information further in the class (treats as text only currently).

Original issue reported on code.google.com by svollbehr on 10 Mar 2010 at 8:52

[GoogleCodeExporter]

Original comment by svollbehr on 10 Mar 2010 at 8:52

• Added labels: ID3v2

[GoogleCodeExporter]

Original comment by svollbehr on 13 Mar 2010 at 8:51

[GoogleCodeExporter]

Original comment by svollbehr on 26 Mar 2010 at 6:55

• Added labels: Type-Enhancement
• Removed labels: Type-Defect