Finally nailed the font issue!
The bottom line was that the canonical type on OS X is UTF-32LE, not UTF-16LE as on Windows, or WCHAR_T as on Linux (which is a pseudo-encoding anyhow, which means “the system dependent and locale dependent wide character encoding”). On OS X using WCHAR_T defaulted to UTF-8, which – while it is a great encoding – didn’t jive with the rest of XBMC.
I can’t believe that took around 6 hours to figure out…
13 Comments so far
Leave a reply
w00t!!
Many thanks!
The Spanish community blesses you!
Wohoo! Good one!
Perhaps we’ll get a new build just with that implementation.
Great work Elan, I can’t wait for the next release to sink my beta jaws in!
Actually, I’m still tracking down some filesystem character issues. For some reason directory/filenames are still screwed up…
I hope that this also fixs the problem with Swedish fonts (I assume so). I am so close to get myself a MacMini and that is all due to your work with XBMC… I want to be abl to retire my old Xbox:)
dos that explain the odd characters used in the RSS feed & weather etc ?
@madmax: Yes!
@Jalle: No reason why it shouldn’t.
[...] Vía: AppleWeblog Más información: OSXBMC [...]
elan: Are there any plans, in the future, to implement Sparkle auto-update functionality? I’d assume “no until we get to ‘stable’” but I’ve been asked this around and thought it made sense (I don’t know if there are plans for version-checking in other platforms but the same functionality could call platform-specific functions in each).
eduo: Yes, but I’d be happier if Sparkle supported incremental updates, as the full package is quite large.
elan: http://sparkle.andymatuschak.org/wiki/Sparkle2/IncrementalUpdates
@eduo: Saw that. Looks like vaporware at the moment