Re: php can't resolve 8.3 paths to unicode filenames, is that expected ?
| From: | Pierre Joye | Date: | Sat, 17 Aug 2013 07:41:38 +0000 |
| Subject: | Re: php can't resolve 8.3 paths to unicode filenames, is that expected ? | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 | Groups: | php.windows |
| Request: | Send a blank email to php-windows+get-31134@lists.php.net to get a copy of this message | ||
On Sat, Aug 17, 2013 at 7:17 AM, Pierre Joye <pierre.php@gmail.com> wrote:
> On Fri, Aug 16, 2013 at 9:40 AM, R. S. <rsk82@live.com> 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 :)
Ok, it looks like a found a bug, not in php but in the windows API.
Which PHP version do you use (newest version uses a different CRT)?
--
Pierre
@pierrejoye | http://www.libgd.org