Opened 20 years ago
Closed 20 years ago
Last modified 20 years ago
#449 closed patch (invalid)
MythMusic can mangle extended characters
Reported by: | Owned by: | Isaac Richards | |
---|---|---|---|
Priority: | minor | Milestone: | unknown |
Component: | mythmusic | Version: | 0.18.1 |
Severity: | medium | Keywords: | |
Cc: | Ticket locked: | no |
Description
My music collection includes works by Frédéric Chopin as well as the musical Les Misérables. The file names include the accented e (é). When I tried to play these works, I got "Unable to open file. Error 5".
Investigating found that the filenames had been mangled in MySQL. Fixing the database entries did not make it work. Thus, there are really two problems: filenames can be mangled before going into the database and filenames are mangled upon query.
To fix this, I changed all of the filename conversions to use ASCII instead of Unicode. This fixed my problem, but I have not extensively tested it to determine whether it causes other problems. Will attach patch.
Attachments (1)
Change History (3)
Changed 20 years ago by
Attachment: | mythmusic.patch added |
---|
comment:1 Changed 20 years ago by
Milestone: | → unknown |
---|---|
Resolution: | → invalid |
Severity: | high → medium |
Status: | new → closed |
Version: | → head |
The DB entries should be in UTF8, then you can convert from that to ascii before accessing the file system. The messed up DB entries you saw were probably the UTF8 escape codes for the character you wanted. QString has facilities to translate from your locale to UTF8 and from UTF8 to your locale.
I'm marking this as invalid until the patch is fixed.
comment:2 Changed 20 years ago by
Version: | head → 0.18.1 |
---|
I cannot reproduce with current version. I had the problem when running 0.18.1, but have since moved to head.
Lacking a 0.18.1 box, I do not forsee fixing the patch as danielk describes.
Patch to change filename conversions to ASCII from UTF8.