Generic API useless with Unicode for ID3v2?
lists at informa.tiker.net
Wed Oct 17 03:06:48 CEST 2007
Hi Scott, all,
A Tagpy user reported an issue where a unicode tag was not written to a
ID3v2-tagged file properly, and I traced the issue to the fact that TagLib
won't change the encoding of an existing TextIdentificationFrame when setting
new text, even if leaving the encoding as Latin1 means losing (potentially
unicode-encoded) data. If that is really true, that's horrible. Losing data
as default behavior is not acceptable.
In particular, that means you can't reliably use the generic API with Unicode
data on ID3v2 files.
Can this be fixed?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/taglib-devel/attachments/20071016/937eea65/attachment.pgp
More information about the taglib-devel