Feature request: Optional tag delimiters

[simoncn]

(12-08-2013 03:56)AMP Wrote:  There may be more than one "TXXX" frame in each tag, but only one with the same description.

So, it would appear that multiple TXXX frames for multiple values won't work and based on looking at the behavior of many tagging programs none take this approach...

Thanks for pointing this out. I hadn't noticed this statement in my previous reading of the ID3 specs.

Quote:I've seen it mentioned elsewhere on this forum that your interpretation of the standard is that the NULL delimiter doesn't apply to TXXX frames, and having read the spec I can see that interpretation. Unfortunately, it would appear that few others are reading it that way and instead are creating multiple-entry TXXX frames using the null character. I've yet to find a program which will write a multiple-value tag out as multiple TXXX frames with the same descriptor.

Given that multiple TXXX strings with the same description aren't allowed, and the statement in the ID3v2.4 spec that the TXXX frame 'is intended for one-string text information concerning the audio file in a similar way to the other "T"-frames' (which do allow null separators), I think it's reasonable for MinimServer to treat null characters in ID3v2.4 TXXX tags as separators for multiple values.

My previous opinion was based on the statement in section 4.2.6 of the ID3v2.4 spec that defines the Value field as "<text string according to encoding>", which doesn't match the line in section 4.2 that defines the Information field as "<text string(s) according to encoding>". Your investigations have convinced me that the 4.2.6 words are an incorrect carry-over from the corresponding section in the ID3v2.3 spec, and should have been changed to match the 4.2 words.

I'm still of the opinion that MinimServer shouldn't split an ID3v2.3 TXXX frame into multiple values if the Information field contains '/' characters, but should interpret these '/' characters as valid text in the frame's (single) value.