2010-12-03, 13:57
My bad. Didn't read the spec too carefully. In that case, the best option would be UTF-8 in both directions, IMO.
If I need to match a string, say a filename, in XBMC via JSON-RPC, must I first encode that string to the same encoding as used in XBMC before sending it?
XBMC: "Åland.mp3" (CP850)
Client: "\u00c5land.mp3" (UTF-8) -> "Åland.mp3" (CP850)
It would seem difficult to use the JSON-RPC API for international content if only the latin1 chars are available (barring content encoding)?
If I need to match a string, say a filename, in XBMC via JSON-RPC, must I first encode that string to the same encoding as used in XBMC before sending it?
XBMC: "Åland.mp3" (CP850)
Client: "\u00c5land.mp3" (UTF-8) -> "Åland.mp3" (CP850)
It would seem difficult to use the JSON-RPC API for international content if only the latin1 chars are available (barring content encoding)?