Re: how to handle multi value tags?

Petteri Hintsanen <[email protected]> writes:

> =E0=A4=B8=E0=A4=AE=E0=A5=80=E0=A4=B0 =E0=A4=B8=E0=A4=BF=E0=A4=82=E0=A4=B9=
 Sameer Singh <[email protected]> writes:
>
>>   - In emms-info-native.el defcustomed a list of info fields which may
>> have multiple values, if these are ever encountered while parsing,
>>     then append the values into a list.
>
> Good that you found out that field names are not required to be unique.
> I did not catch this when I wrote emms-info-native.  According to the
> spec it is even encouraged:
>
>   "Field names are not required to be unique (occur once) within a commen=
t header. As an example, assume a track was recorded by three well know art=
ists; the following is permissible, and encouraged:
>
>   1ARTIST=3DDizzy Gillespie
>   2ARTIST=3DSonny Rollins
>   3ARTIST=3DSonny Stitt"
>
> (from https://xiph.org/vorbis/doc/Vorbis_I_spec.html#x1-820005)
>
> But why defcustom?  Why not support multiple values for any field?  The
> spec does not restrict that, and in my opinion we should not either.
>

Sure, this can be done. Also on that note, why do we restrict what tags
could be written or read from the tag? Will it not be better to read all
of the tracks and also write all?

One more question I have is: The tracktag program is used to write
metadata to opus files. AFAICS tracktag has not been updated for about
10 years. Can we deprecate that and use something like "opusenc" from the
opus-tools package?

> --
> Petteri

Thanks