MythFrontend failing to launch when its path has extended chars (OSX 10.5)

[dh.mythtv@…]

The downloaded binary for Mythfrontend on OSX had been working fine, then suddenly stopped launching. Checking the console log, the only clue was

12/9/09 17:52:12 [0x0-0x103002f].org.osx-bundler.MythFrontend[42147] 2009-12-09 17:52:12.788 Could not find theme: metallurgy

Eventually I figured out that the app was unable to find itself once I'd stored it with the other video applications, which had a path as follows:

/Applications/•Pictures/Video?

(In case the above gets mangled, there's a dot in front of "Pictures," which I believe is Unicode character 2022, "Bullet".) I strongly suspect that the mechanism Mythfrontend is using to access the file system is not Unicode compliant. I don't know if this is also true of the Linux implementation.

[robertm]

Worth asking, is this fixed if you compile with the script now (trunk only) as it compiles Qt 4.6 by default?

[anonymous]

I'm not willing to deal with compiling this thing, but the latest precompiled binary does appear to operate when placed in the location that the old one failed.