Hi Jan! On 05.01.2018 at 16:20, Jan Ehrhardt wrote:
> "Christoph M. Becker" in php.internals (Fri, 5 Jan 2018 15:53:23 +0100): >> On 05.01.2018 at 14:55, Jan Ehrhardt wrote: >> >>>>> The main reason why I prefer the github zips over the zips at >>>>> http://windows.php.net/download/ is some kind of mismatch in the UTF-8 >>>>> filenames: >>> >>> N:\php-sdk\win32sdk2 >>> $ unzip -h >>> UnZip 6.00 of 20 April 2009, by Info-ZIP. Maintained by C. Spieler. Send >>> bug reports using http://www.info-zip.org/zip-bug.html; see README for >>> details. >> >>From the release notes[1]: >> >> | Support for UTF-8 encoded entry names, both through PKWARE's "General >> | Purpose Flags Bit 11" indicator and Info-ZIP's new "up" unicode path >> | extra field. (Currently, on Windows the UTF-8 handling is limited to >> | the character subset contained in the configured non-unicode "system >> | code page".) >> >> So this might be a codepage issue. > > The warnings do not occur when processing the zips from > https://github.com/php/php-src/releases so we know it must be possible > to produce zip-files with Unicode filenames without mismatch. Big > question is: how? Frankly, I don't know. However, these message are indeed mere warnings; the log as well as the file system shows correct filenames after extracting. Furthermore, the messages 'continuing with "central" filename version' don't make sense to me, since the filenames in the local file headers are identical to those in the central directory headers. Anyhow, since everything appears to work with unzip 6.0.0 and there are better tools anyway, I don't think this issue deserves spending much time. :) -- Christoph M. Becker -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
