The comment vectors are structured similarly to a UNIX environment variable. That is, comment fields consist of a field name and a corresponding value and look like:
comment[0]="ARTIST=me";
comment[1]="TITLE=the sound of Vorbis";
The field name is case-insensitive and may consist of ASCII 0x20 through 0x7D, 0x3D ('=') excluded. ASCII 0x41 through 0x5A inclusive (characters A-Z) is to be considered equivalent to ASCII 0x61 through 0x7A inclusive (characters a-z).
The field name is immediately followed by ASCII 0x3D ('='); this equals sign is used to terminate the field name.
0x3D is followed by 8 bit clean UTF-8 encoded value of the field contents to the end of the field.
Les tags vorbis sont en principe stoques nativement en UTF8. A priori, si tu les as autrement, soit ta lib est hackee, soit tu utilises des tags ID3.
[^] # Re: UTF-8 le standard des noms de fichier
Posté par imalip . En réponse à la dépêche GTK+ 2.6 est disponible. Évalué à 10.
Et hop, un coup de doc Vorbis :
http://www.xiph.org/ogg/vorbis/doc/Vorbis_I_spec.html#id4744873(...)
The comment vectors are structured similarly to a UNIX environment variable. That is, comment fields consist of a field name and a corresponding value and look like:
comment[0]="ARTIST=me";
comment[1]="TITLE=the sound of Vorbis";
The field name is case-insensitive and may consist of ASCII 0x20 through 0x7D, 0x3D ('=') excluded. ASCII 0x41 through 0x5A inclusive (characters A-Z) is to be considered equivalent to ASCII 0x61 through 0x7A inclusive (characters a-z).
The field name is immediately followed by ASCII 0x3D ('='); this equals sign is used to terminate the field name.
0x3D is followed by 8 bit clean UTF-8 encoded value of the field contents to the end of the field.
Les tags vorbis sont en principe stoques nativement en UTF8. A priori, si tu les as autrement, soit ta lib est hackee, soit tu utilises des tags ID3.