In ID3v23 the spec states that some multiple values can be stored in one frame using the '/' character, we need to support this rather than using null seperator in all cases

[IJabz]

So for From https://java.net/jira/browse/JAUDIOTAGGER-414

TCOM TEXT TOLY TOPE TPE1

A second call to addField() should seperate with '/' not \0 for ID3v23 by default, but should be configurable. Will have to check for ID3v22

[IJabz]

Currently have no special support for reading '/' specially either, so if the value was 'Johnny Cash/June Carter' we would interpret that as single value 'Johnny Cash/June Carter', however it doesn't break it either so if calling application converted the value returned from 'Johnny Cash/June Carter' to 'Cash/Carter' then that is what would be written. So what this mean if an application supports displaying multiple for those fields using the '/' mechanism it can still do that as long as it parses the value returned by jaudiotagger itself, but if it uses jaudiotaggers own parsing of the value then it will see as one value, similarly it can write using '/' if it uses setField(). The other difference is that if jaudiotagger is used to convert an ID3v23 tag to a ID3v24Tag then it would not convert 'value1/value2' to 'value1\0value2' it would remain as 'value1/value2'