It turns out that the missing id3v2 tags can be written in latin1 (1 byte) characters when the locale is set to 'C', just by using the --id3v2-latin1 switch. I thought I'd already tried that, but I suspect I may have missed off the '1' at the end of the switch.
The other character encoding switch, --id3v2-utf16, doesn't do anything when the locale is "C" I don't know enough about character encoding to sound knowledgable here, but it seems the only way to get UTF16 characters into the id3v2 tag fields (which I believe is the preferred format for id3v2), is to set the locale to a UTF-8 variant. ------------------------------------------------------------------------ chill's Profile: http://forums.slimdevices.com/member.php?userid=10839 View this thread: http://forums.slimdevices.com/showthread.php?t=111997 _______________________________________________ ripping mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/ripping
