2013-05-03, 03:39
(2013-05-03, 00:04)HeresJohnny Wrote:I'm sorry, but I'm not able to fix this problem. It is over my knowledge... and I do not understand why it happen. Paths containing non-ascii characters are stored and send correctly to the python function starting the command line... but the python function do not recognize the path correclty. Encoding paths to the system encoding before send it to the function generate en error. More stangely this problem only occurs under Windows... and all is working correctly under Linux.(2013-04-30, 18:26)Angelscry Wrote: Are you under Windows or Linux operating system?
It's Windows 7 x64,
Display language: English
Codepage for non-unicode programs: German (Germany)
XBMC set to English, Default codepage
Some more info on import behaviour:
Scanning items (automatically):
ßäöü in folder names => Items within that folder are not parsed
ßäöü in file names only => umlauts are erased (Der große Graben => Der groe Graben)
Adding items manually:
Titles are preserved correctly, because XBMC pops up the naming dialogue.
However, files that were entered with their correct umlauts cannot be opened.
The movie component of XBMC doesn't have this problem, i.e. the movie "Die tödliche Maria" in a folder with the same name can be opened without problems.
So... if someone could bring its help and take a look at the Advanced Launcher code, it will be welcome.