https://bugzilla.novell.com/show_bug.cgi?id=780658 https://bugzilla.novell.com/show_bug.cgi?id=780658#c9 --- Comment #9 from Karl Ove Hufthammer <karl@huftis.org> 2013-05-21 20:09:08 UTC --- Thanks for looking into this, Suren. I have now tested the following: 1. Current (latest openSUSE 12.3) version of taglib with friends (libtag-extras1 &c.). 2. Latest version of taglib with friends in Factory (includes r8 patch). 3. Plain taglib + libtag-extras, compiled from source. I did the test as described above, using Amarok and the MP3 I supplied for testing. The versions in 1 and 2 both corrupt the Δ character. However, using normal taglib without the RusXMMS patches, everything works *perfectly*. Based on this, and on the comments from the Amarok authors, I conclude that the RusXMMS patches are still buggy, and causes data corruption / data loss. Details on what is stored when using the official taglib (3): Test: Stored as ISO-8859-1 (latin1) with correct character encoding byte (00) TestÆØÅTest: Stored as ISO-8859-1 (latin1) with correct character encoding byte (00) TestÆØÅΔTest: Stored as UTF-8 with correct character encoding byte (03) In other words, taglib only uses the smallest character encoding needed to encode the text (i.e., latin1 and UTF-8 with string contains characters outside latin1). The RusXMMS patches obviously break this. With these patches, all strings use the latin1 character encoding byte, and in addition the non-latin1 character (two bytes in UTF-8) is changed to an invalid one-byte character. Note that when *reading* the valid ID3 metadata (generated by unpatched taglib), everything seems to work fine, even with the RusXMMS patches. (But there are problems reading the invalid metadata no matter what version one uses.) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.