Re: libzip and non-ascii home directories on Windows
On 28 April 2015 at 15:54, Dirk Hohndel d...@hohndel.org wrote: On Tue, Apr 28, 2015 at 02:16:32PM +0300, Lubomir I. Ivanov wrote: On 28 April 2015 at 11:55, Lubomir I. Ivanov neolit...@gmail.com wrote: On 28 April 2015 at 08:39, Dirk Hohndel d...@hohndel.org wrote: So this problem apparently still isn't fixed. How frustrating. The current 4.4.1 Windows binaries are build with libzip version 42199fe38a16 which should contain all the necessary fixes, yet exporting to divelogs.de still fails without any error. I have now created a new Windows VM where I was able to create a local user with the useful user name of Møtörhæđ Łüñçïß - and I can reproduce the problem. I built the latest master of libzip and dropped it into the program folder - still the same problem. Before I try to sprinkle the sources with tons of debug output... Lubomir, any idea what's up here? it works for me i.e. i can't seem to feed a unicode path that doesn't work for standalone libzip or the divelogs code. any technical output to base my research on is appreciated. Which version of libzip are you using in your tests? As usual, my understanding of all this is somewhat limited. Path handling on Windows makes no sense to me :-( I built a Subsurface binary with version 42199fe38a16 which appears to have all the relevant changes and all I can see is that it silently fails to export to divelogs.de for my new user Møtörhæđ Łüñçïß. I'll add a ton of debug output to see where exactly it fails and with which error... 56d3e8a2b3a8 lubomir -- ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: libzip and non-ascii home directories on Windows
On 28 April 2015 at 11:55, Lubomir I. Ivanov neolit...@gmail.com wrote: On 28 April 2015 at 08:39, Dirk Hohndel d...@hohndel.org wrote: So this problem apparently still isn't fixed. How frustrating. The current 4.4.1 Windows binaries are build with libzip version 42199fe38a16 which should contain all the necessary fixes, yet exporting to divelogs.de still fails without any error. I have now created a new Windows VM where I was able to create a local user with the useful user name of Møtörhæđ Łüñçïß - and I can reproduce the problem. I built the latest master of libzip and dropped it into the program folder - still the same problem. Before I try to sprinkle the sources with tons of debug output... Lubomir, any idea what's up here? it works for me i.e. i can't seem to feed a unicode path that doesn't work for standalone libzip or the divelogs code. any technical output to base my research on is appreciated. lubomir -- ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: libzip and non-ascii home directories on Windows
On Tue, Apr 28, 2015 at 02:16:32PM +0300, Lubomir I. Ivanov wrote: On 28 April 2015 at 11:55, Lubomir I. Ivanov neolit...@gmail.com wrote: On 28 April 2015 at 08:39, Dirk Hohndel d...@hohndel.org wrote: So this problem apparently still isn't fixed. How frustrating. The current 4.4.1 Windows binaries are build with libzip version 42199fe38a16 which should contain all the necessary fixes, yet exporting to divelogs.de still fails without any error. I have now created a new Windows VM where I was able to create a local user with the useful user name of Møtörhæđ Łüñçïß - and I can reproduce the problem. I built the latest master of libzip and dropped it into the program folder - still the same problem. Before I try to sprinkle the sources with tons of debug output... Lubomir, any idea what's up here? it works for me i.e. i can't seem to feed a unicode path that doesn't work for standalone libzip or the divelogs code. any technical output to base my research on is appreciated. Which version of libzip are you using in your tests? As usual, my understanding of all this is somewhat limited. Path handling on Windows makes no sense to me :-( I built a Subsurface binary with version 42199fe38a16 which appears to have all the relevant changes and all I can see is that it silently fails to export to divelogs.de for my new user Møtörhæđ Łüñçïß. I'll add a ton of debug output to see where exactly it fails and with which error... /D ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: libzip and non-ascii home directories on Windows
On 28 April 2015 at 16:00, Robert Helling hell...@atdotde.de wrote: Hi, On 28.04.2015, at 14:54, Dirk Hohndel d...@hohndel.org wrote: Path handling on Windows makes no sense to me :-( totally ignorant suggestion (by somebody who has no idea about windows paths): Could we use a relative path to avoid the problem (since that we might be able to choose with good characters). IIRC Qt can convert absolute to relative paths. the user can still install Subsurface in C:\Program Files\ translated to his home language (for some odd setup reason). the unicode support is kind of mandatory if we want to use the zip_open() interface and have permissions to write into a location. :( there is also the alternative to use the new libzip memory / buffer API, but i don't have the time to investigate into that ATM. lubomir -- ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: libzip and non-ascii home directories on Windows
On Tue, Apr 28, 2015 at 04:13:32PM +0300, Lubomir I. Ivanov wrote: Which version of libzip are you using in your tests? As usual, my understanding of all this is somewhat limited. Path handling on Windows makes no sense to me :-( I built a Subsurface binary with version 42199fe38a16 which appears to have all the relevant changes and all I can see is that it silently fails to export to divelogs.de for my new user Møtörhæđ Łüñçïß. I'll add a ton of debug output to see where exactly it fails and with which error... 56d3e8a2b3a8 Thanks. BTW: upstream master appears broken (at least it doesn't cross compile for me) I built with this version and there are no errors. libzip is convinced that it successfully created a zip file and added things. Except it didn't. I can see the temp file that we write to and read back (that's nuts, need to fix that), but not a sign of the zip file. Grmbl. /D ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: libzip and non-ascii home directories on Windows
On 28 April 2015 at 08:39, Dirk Hohndel d...@hohndel.org wrote: So this problem apparently still isn't fixed. How frustrating. The current 4.4.1 Windows binaries are build with libzip version 42199fe38a16 which should contain all the necessary fixes, yet exporting to divelogs.de still fails without any error. I have now created a new Windows VM where I was able to create a local user with the useful user name of Møtörhæđ Łüñçïß - and I can reproduce the problem. I built the latest master of libzip and dropped it into the program folder - still the same problem. Before I try to sprinkle the sources with tons of debug output... Lubomir, any idea what's up here? last time i tried, i made the divelogs code use a unicode path and libzip was able to open it (i.e. worked for me). i need to look into that again. lubomir -- ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: libzip and non-ascii home directories on Windows
On Tue, Apr 28, 2015 at 2:30 PM, Dirk Hohndel d...@hohndel.org wrote: Oh joy. Guess what, libzip has two different ways to build it (sound familiar, anyone)? And if you use autoconf then the Win32 specific path handling routines aren't even built. And of course I built all this with configure... But if you use CMake then it compiles different source files. Oh, and the library then has a different name (libzip.dll vs libzip-2.dll). But if you rename the library and plop it in place in an existing install, things appear to work (I'm waiting for the user who reported the issue to report back if it fixed things for him as well). For now I tested it here on Windows XP (yay!) and my buddy Møtörhæđ Łüñçïß was able to create a zip file for upload to Divelogs.de... Urgh. /D ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: libzip and non-ascii home directories on Windows
Oh joy. Guess what, libzip has two different ways to build it (sound familiar, anyone)? And if you use autoconf then the Win32 specific path handling routines aren't even built. And of course I built all this with configure... But if you use CMake then it compiles different source files. Oh, and the library then has a different name (libzip.dll vs libzip-2.dll). But if you rename the library and plop it in place in an existing install, things appear to work (I'm waiting for the user who reported the issue to report back if it fixed things for him as well). For now I tested it here on Windows XP (yay!) and my buddy Møtörhæđ Łüñçïß was able to create a zip file for upload to Divelogs.de... /D ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
Re: libzip and non-ascii home directories on Windows
On 28 April 2015 at 20:30, Dirk Hohndel d...@hohndel.org wrote: Oh joy. Guess what, libzip has two different ways to build it (sound familiar, anyone)? And if you use autoconf then the Win32 specific path handling routines aren't even built. And of course I built all this with configure... But if you use CMake then it compiles different source files. Oh, and the library then has a different name (libzip.dll vs libzip-2.dll). But if you rename the library and plop it in place in an existing install, things appear to work (I'm waiting for the user who reported the issue to report back if it fixed things for him as well). For now I tested it here on Windows XP (yay!) and my buddy Møtörhæđ Łüñçïß was able to create a zip file for upload to Divelogs.de... yeah, i used cmake to build. it's hard to get configure to work. lubomir -- ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
libzip and non-ascii home directories on Windows
So this problem apparently still isn't fixed. How frustrating. The current 4.4.1 Windows binaries are build with libzip version 42199fe38a16 which should contain all the necessary fixes, yet exporting to divelogs.de still fails without any error. I have now created a new Windows VM where I was able to create a local user with the useful user name of Møtörhæđ Łüñçïß - and I can reproduce the problem. I built the latest master of libzip and dropped it into the program folder - still the same problem. Before I try to sprinkle the sources with tons of debug output... Lubomir, any idea what's up here? Thanks /D ___ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
