https://bugzilla.novell.com/show_bug.cgi?id=780658 https://bugzilla.novell.com/show_bug.cgi?id=780658#c6 Karl Ove Hufthammer <karl@huftis.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |karl@huftis.org --- Comment #6 from Karl Ove Hufthammer <karl@huftis.org> 2013-05-20 08:49:32 UTC --- It looks like the patch may have fixed the umlaut problem, but not the bug (this bug); it simply introduced a new bug. I’ll attach a file which exhibits this problem for Source RPM : taglib-1.8-3.5.3.src.rpm Build Date : Wed May 1 09:13:29 2013 To reproduce, open the file in Amarok, and edit the metadata fields to contain (for the fields Title, Composer and Album, for example) the following strings: Test TestÆØÅTest TestÆØÅΔTest The old behaviour was that the non-ASCII latin1 characters (ÆØÅ) was broken. Now this works (the second string), but the new behaviour is that non-ASCII non-latin1 characters are broken, so that in the last string the delta character is replaced by an invalid character (hex value 94, which is in the non-defined part of latin1/ISO-8859-1). The original taglib handles this perfectly, so it’s the OpenSuse-applied RusXMMS patches that is the problem. See also https://bugs.kde.org/show_bug.cgi?id=311399 for a more complete explanation (bug note that the behaviour is now changed from that described there – still broken, though). Personally, I think it would be much better if the RusXMMS patches were to disappear completely; they only seem to cause problems and break correct behaviour. -- 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.