2011-01-04, 15:58
I've just run into an issue concerning filenames.
When doing a VideoLibrary.GetMovies i get (among many others)
Note that the filename contains a UTF8 char (ö = ö) as well as a ISO char (the "ö" near the end).
This combination kills the Ocj-C JSON parser i'm using (YAJL).
I've implemented a workaround in my client by interpreting the JSON answer as Latin1, and trying to interpret each result string as utf8 afterwards, falling back to the Latin1 encoded result if the conversion to utf8 fails.
Unfortunately i can't really tell wether the problem is located with JSON, with XBMCs filehandling, or maybe even on the filesystem.
Is this known? Maybe even by design?
Edit:
Just found the same issue was discussed a few pages earlier. Damn, this thread is getting long...
When doing a VideoLibrary.GetMovies i get (among many others)
Code:
{
"fanart" : "special://masterprofile/Thumbnails/Video/Fanart/ccffb604.tbn",
"file" : "/home/xbmc/server/video/german/Haben Sie das von den Morgans gehört (2009)/Haben Sie das von den Morgans gehört (2009).avi",
"genre" : "Komödie / Drama / Romanze",
"label" : "Haben Sie das von den Morgans gehört?",
"movieid" : 56,
"thumbnail" : "special://masterprofile/Thumbnails/Video/c/ccffb604.tbn",
"year" : 2009
},
Note that the filename contains a UTF8 char (ö = ö) as well as a ISO char (the "ö" near the end).
This combination kills the Ocj-C JSON parser i'm using (YAJL).
I've implemented a workaround in my client by interpreting the JSON answer as Latin1, and trying to interpret each result string as utf8 afterwards, falling back to the Latin1 encoded result if the conversion to utf8 fails.
Unfortunately i can't really tell wether the problem is located with JSON, with XBMCs filehandling, or maybe even on the filesystem.
Is this known? Maybe even by design?
Edit:
Just found the same issue was discussed a few pages earlier. Damn, this thread is getting long...