New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Strange Asian Characters in File Browser #5743
Comments
Commented by: johschmitz |
Commented by: johschmitz After deleting the database file "mixxxdb.sqlite" I could solve the problem. Maybe it was caused by an older version from ubuntu repository or the new beta version, both where installed before. |
Commented by: asantoni Thanks for reporting this bug Johannes. Can you please attach one of those MP3s to this bug report so that we Thanks, On Wed, Jan 5, 2011 at 2:52 PM, Johannes Schmitz wrote:
|
Commented by: asantoni Ok, thanks for letting us know Johannes. We have code to upgrade the We'll have to keep an eye on this... Thanks again, On Wed, Jan 5, 2011 at 3:06 PM, Johannes Schmitz wrote:
|
Commented by: johschmitz I am not completely sure anymore because it did not happen with all files and now it is gone. And I deleted the database file... |
Commented by: uklotzde Conversions between different character encodings have been fixed with the rework on the TagLib metadata handling. All metadata and cover art of the attached file is displayed correctly in version 1.12 and master (post-1.12-release). |
Issue closed with status Fix Released. |
Reported by: johschmitz
Date: 2011-01-05T22:52:17Z
Status: Fix Released
Importance: Medium
Launchpad Issue: lp697902
Tags: library, metadata, soundsource
Attachments: [screenshot of the problem](https://bugs.launchpad.net/bugs/697902/+attachment/1784521/+files/screenshot of the problem), [file with possibly broken tag](https://bugs.launchpad.net/bugs/697902/+attachment/1784557/+files/file with possibly broken tag)
Mixxx shows Chinese characters in the file browser. Version 1.8.2 on Ubuntu 10.10 64bit
This happens in the library/tags. Filenames seem to be correct.
The text was updated successfully, but these errors were encountered: