The love can't run on when fold name has UNICODE words

[poorenglish]

Hi
The *.love,or game.exe(create by love) are also can't run when the fold contain the UNICODE words,such Chinese words,Japanese words.
stderr.txt

Game (D:\Program Files\复件 LOVE\Test1) does not exist.

the words which you can't recongise are chinese words.
as I know,the lua support the UNICODE words.
An extra question,is there some video control functions?
I think I can't find any function about the love.video.

Plz forgive my poor English,I hope you can understand what I say.

[nevon]

Yeah. It's a known bug from what I've heard. Hopefully it'll be fixed by the 0.6 release, although I don't know for sure if it will.

[Robin]

It's a problem in the virtual filesystem (PhysFS) -- that bug was fixed in version 2.0 of it, I believe. I'm not sure whether LÖVE 0.6.0 will include. Any developer around who has the answer?

[bmelts]

I can attest to Unicode paths working properly under LÖVE 0.6.0 on Mac OS X.

(Then again, they also work properly under LÖVE 0.5.0 on Mac OS X, so I don't know...)

[nevon]

They work fine in Linux as well.

[bartbes]

I think the actual builds will all use PhysFS 2.0, at least the windows build will, and it appears the others didn't even have the 'bug'.

[rude]

I've actually discovered that it's not (only) because of PhysicsFS. It's a Visual Studio project setting. I'm not sure how much work is required to fix it. I don't think just switching on Unicode in the project file will do the trick.

But yeah, it must clearly be fixed ASAP.

[Jasoco]

I can use unicode paths in LÖVE on OS X, (As all my .love files are in a folder entitled "LÖVE" and work with no problems.) but if I use a "game name" with a unicode character in it it refuses to run.

[Sardtok]

Try renaming the LÖVE folder: "愛" and see if it works.
Thing is ö is an ISO-8859-1 character, although ISO-8859-1 shouldn't be used for folder names on systems using Unicode. *shrug*

[rude]

The problem was SDL not properly supporting Unicode in Windows (I was in denial about this for a while). An epic workaround is included in 748b5b952576, which seems to work. Some testing would be appreciated, especially on Win XP.