Re: php can't resolve 8.3 paths to unicode filenames, is that expected ?

Pierre Joye <[email protected]>
Newsgroups gmane.comp.php.windows
Message-ID <CAEZPtU6W4Fdv1XF=RQR8JBQjwGfRBnPnaG9GP9UcW+o5duaLsQ@mail.gmail.com>
On Fri, Aug 16, 2013 at 9:40 AM, R. S. <[email protected]> wrote:
> Hello Pierre,
>
> Friday, August 16, 2013, 5:38:01 AM, you wrote:
>
>> and  'TESTUN~1.PHP' has unicode, created using CreateFileW with
>> 'testunicode-ßäü123-öâ.php' as path. Fetch the 8.3 path and use it to
>> open the file using php, works. In other words. exactly what your COM
>> script does. Now, why you come to the conclusion that PHP can't open
>> 8.3 path is a misery to me right now. It can and without issue.
>
> It still seems you didn't read my examples, but this time your fresh mind
> actually helped narrowing the problem and thanks
> for that !
>
> Indeed 'testunicode-ßäü123-öâ.php' works without
> any issue. It seems that only some character ranges
> are making php unable to get to the file, like russian or greek.
>
> if you make files like:
> testunicode-Ελλάδα or testunicode-Россия
>
> Then php can't get handle to these files with errors like:
>
> Warning: fopen(C:\TESTUN~3.PHP): failed to open stream: Invalid argument
> in C:\test.php on line 7



> So the problem is even stranger.

Ok, now I can reproduce it. That's actually weird and have to look at it :)

> How the php filesystem function is ever supposed to
> know that the path contain unicode letter since it was given the shorth path.

Again, it does not. Nothing in php deals with unicode paths.

> It really looks like someone tried to implement unicode filename handling in PHP
> but stopped in middle.

No, nobody tried in any acitve branches, nor in master (not released
yet). And believe me, I know that very well.

Cheers,
-- 
Pierre

@pierrejoye | http://www.libgd.org

-- 
PHP Windows Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.