FS#15559 - [audacious] non-UTF-8 tag encodings don't work in 2.1-1

Attached to Project: Arch Linux
Opened by Roman Kyrylych (Romashka) - Saturday, 18 July 2009, 12:08 GMT
Last edited by Andrea Scarpino (BaSh) - Saturday, 03 October 2009, 14:51 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Alexander Fehr (pizzapunk)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 7
Private No

Details

Description:

"Auto charecter encoding detector" and "Fallback character encodings" settings in audacious-2.1-1 don't have any effect. The result is that files with tags in non-UTF-8 encodings produce ??? instead of correct chars.

I am not sure if this is upstream bug.


Steps to reproduce:

Load mp3 files with tags encoded in windows-1251 or other non-UTF-8 encoding.
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Saturday, 03 October 2009, 14:51 GMT
Reason for closing:  Fixed
Additional comments about closing:  audacious 2.1-2
Comment by Nagy Gabor (combo) - Saturday, 05 September 2009, 11:10 GMT
The same for me. I set iso8859-2 to fallback encoding, but it doesn't seem to work.
Comment by Gicu Gorodenco (medved) - Tuesday, 22 September 2009, 15:22 GMT
This guy here explains what's the problem and solution.
I changed the PKGBUILD accordingly and that solved my problem.

To maintainer: Just take the attached files and put them into next mainstream build

To all who want a solution before it comes to repository build - read the AUR manual ;-)
   PKGBUILD (1.1 KiB)
   chardet.c.patch (0.7 KiB)