Hello it does not help ;

it is only a suggestion here to keep a compatibility layer to be able to
read from file but not be stuck with a ASCII file path [[or other 8bits
which should rest in the museum of encodings]] ; windows does not support
UTF-8 file path then the only solution is to use wfopen [even if the
program internally uses UTF-8 literals] you can safely translate to UTF-16
 then handling "wide" path ; feeding an fp to the interface instead of a
file-path ; gives you the opportunity to stay away from this matter.

Best

On Mon, Apr 6, 2015 at 9:17 AM, Daniel Stenberg <daniel_at_haxx.se> wrote:

> On Sun, 29 Mar 2015, mm.w wrote:
>
> SO this options could be added (1); making the life of many folks easier
>> which I think are in the same situation:
>>
>
> CURLOPT_CAINFO_FP
>> CURLOPT_SSLCERT_FP
>> CURLOPT_SSLKEY_FP
>>
>> where FP is not anymore a file-path but a file-descriptor ; handling
>> unicode paths on windows would be solved.
>>
>
> How will a file descriptor help when you want to provide the data straight
> from memory?
>
> --
>
> / daniel.haxx.se
> -------------------------------------------------------------------
> List admin: http://cool.haxx.se/list/listinfo/curl-library
> Etiquette: http://curl.haxx.se/mail/etiquette.html

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2015-04-06