1
Предложения / Suggestions / Re: Multi Genres parsing split character + ignore trailing spaces
« on: May 07, 2020, 01:29:57 »
Ok thanks for explanations !
I found these specifications a little bit confusing
https://id3.org/id3v2.3.0/#:~:text=category
https://en.wikipedia.org/wiki/ID3#ID3v2
https://en.wikipedia.org/wiki/ID3#ID3v2_frame_specification
But I think I get the point :
- technically AIMP recognizes foreslash separator between each TCOM values (correct with what i see in an hexadecimal editor)
- in UI, the genres separator is displayed as semi colon to end user, this is not what is technically stored in the file header
- follow the standard so only one separator recognized, not a good practice to handle extra other separators
I found these specifications a little bit confusing
https://id3.org/id3v2.3.0/#:~:text=category
Quote
TCONNo real mention of foreslash separator in official specification for 2.3 version ?
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)".
https://en.wikipedia.org/wiki/ID3#ID3v2
Quote
ID3v2.3
v2.3 expanded the frame identifier to four characters, and added a number of frames. A frame can contain multiple values, separated with a null byte. This is the most widely used version of ID3v2 tags.
https://en.wikipedia.org/wiki/ID3#ID3v2_frame_specification
Quote
Notes :=> Separator mentioned in wikipedia but v2.3 uses "generally" the nul separator for any frame but TCOM uses foreslash ?
c. TCOM, TEXT, TOLY, TOPE, and TPE1 can contain multiple values separated by a foreslash ("/").
Version 2.4 of the specification prescribes that all text fields (the fields that start with a T, except for TXXX) can contain multiple values separated by a null character. The null character varies by character encoding.
But I think I get the point :
- technically AIMP recognizes foreslash separator between each TCOM values (correct with what i see in an hexadecimal editor)
- in UI, the genres separator is displayed as semi colon to end user, this is not what is technically stored in the file header
- follow the standard so only one separator recognized, not a good practice to handle extra other separators