2013-01-11, 21:53
JSON rpc is a protocol if the data sent does not follow the protocol how do you want the client to understand ?
The specification is very clear about the fact that strings must be UTF-8 encoded, efficient json parsing needs a stream parser that analyse data as it comes, when some data should not be in the middle the parsers have no way to recover from that.
Xbmc should not be able to send data that does not follow the standard but it does if the data in it's database is not UTF-8 witch was possible until recent Frodo builds. (And will be in Frodo if you don't rescrape the bad data when updating from Eden).
This issue will be recurrent during update until all users rescrapes but well it was the chosen path by the Xbmc team.
The specification is very clear about the fact that strings must be UTF-8 encoded, efficient json parsing needs a stream parser that analyse data as it comes, when some data should not be in the middle the parsers have no way to recover from that.
Xbmc should not be able to send data that does not follow the standard but it does if the data in it's database is not UTF-8 witch was possible until recent Frodo builds. (And will be in Frodo if you don't rescrape the bad data when updating from Eden).
This issue will be recurrent during update until all users rescrapes but well it was the chosen path by the Xbmc team.