You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Original issue 1290 created by galkinvv on 2013-11-07T18:34:32.000Z:
I'm using quodlibet 3.0.2 with Python 2.7.5+ on Debian ~testing
- What did you try to do?
Start quodlibet for the firts time (to create config file)
Close quodlibet
Set id3encoding = cp1251 in config file
Start quodlibet, add folder with lot of mp3s with cp1251 encoding tags
- What did you expect to happen?
Songs load displaying cyrillic characters for tags.
This DID wok in some previous versions of quodlibet
- What did happen instead?
Songs load displaying "random" latin-1 chars for tags
I debugged the reason of problem: config is loaded in main() with config.init(const.CONFIG)
But this parameter is read from config by the id3FILE class earlier while loading of quodlibet/formats/_id3.py during
from quodlibet import browsers.
The attached quite ugly but simple patch solves the issue for me.
The text was updated successfully, but these errors were encountered:
Original issue 1290 created by galkinvv on 2013-11-07T18:34:32.000Z:
I'm using quodlibet 3.0.2 with Python 2.7.5+ on Debian ~testing
- What did you try to do?
Start quodlibet for the firts time (to create config file)
Close quodlibet
Set id3encoding = cp1251 in config file
Start quodlibet, add folder with lot of mp3s with cp1251 encoding tags
- What did you expect to happen?
Songs load displaying cyrillic characters for tags.
This DID wok in some previous versions of quodlibet
- What did happen instead?
Songs load displaying "random" latin-1 chars for tags
I debugged the reason of problem: config is loaded in main() with config.init(const.CONFIG)
But this parameter is read from config by the id3FILE class earlier while loading of quodlibet/formats/_id3.py during
from quodlibet import browsers.
The attached quite ugly but simple patch solves the issue for me.
The text was updated successfully, but these errors were encountered: