Most ID3v2 frames should be unique
The ID3v2 (both 2.3 and 2.4) specification requires most frames to be unique : all text frames but TXXX (see section 4.2), most URL link frames (section 4.3), etc. Conversely, "all text information frames supports multiple strings, stored as a null separated list" in 2.4 ('/'-separated in 2.3).
However, Kid3 allows the user to add, for instance, as many "Artist" fields as she wants, and write them as distinct TPE1 frames. It also allows to use '|' as separator (and converts it as needed).
Kid3 should either :
- prevent the user from creating multiple fields of the same type, and let the behaviour of '|' as it is
- let the interface as it is, but merge the correlated fields into one unique ID3 frame. In this case, we might also consider disabling '|'.
Imported from SourceForge, author: noctiflore