Re: fopen with UTF-8 chars in filenames

2006-03-19 Thread Ross Smith
Igor Peshansky wrote: On Fri, 17 Mar 2006, Paul J. Lucas wrote: On Fri, 17 Mar 2006, Christopher Faylor wrote: Cygwin doesn't provide _wfopen. 1. I install Cygwin. 2. It's in stdio.h that gets installed as part of the Cygwin install. No, actually it's in stdio.h that's part of MinGW (and i

Re: fopen with UTF-8 chars in filenames

2006-03-17 Thread Igor Peshansky
On Fri, 17 Mar 2006, Paul J. Lucas wrote: > On Fri, 17 Mar 2006, Christopher Faylor wrote: > > > Cygwin doesn't provide _wfopen. > > 1. I install Cygwin. > 2. It's in stdio.h that gets installed as part of the Cygwin install. No, actually it's in stdio.h that's part of MinGW (and is installed as

Re: fopen with UTF-8 chars in filenames

2006-03-17 Thread Paul J. Lucas
On Fri, 17 Mar 2006, Christopher Faylor wrote: > Cygwin doesn't provide _wfopen. 1. I install Cygwin. 2. It's in stdio.h that gets installed as part of the Cygwin install. Therefore, as far as I'm concerned, it's in Cygwin. > So, if you are using _wfopen you stopped using Cygwin, then, too, pos

Re: fopen with UTF-8 chars in filenames

2006-03-17 Thread Christopher Faylor
On Fri, Mar 17, 2006 at 01:16:07PM -0800, Paul J. Lucas wrote: >On Thu, 16 Mar 2006, Christopher Faylor wrote: >>I don't know if doing what the OP wants is possible on Cygwin ... > >I solved my problem by using _wfopen() and converting the path to >UTF-16 first. Unless there's a way to work direct

Re: fopen with UTF-8 chars in filenames

2006-03-17 Thread Paul J. Lucas
On Thu, 16 Mar 2006, Christopher Faylor wrote: > I don't know if doing what the OP wants is possible on Cygwin ... I solved my problem by using _wfopen() and converting the path to UTF-16 first. Unless there's a way to work directly with UTF-8, I'll stick with that.

Re: fopen with UTF-8 chars in filenames

2006-03-16 Thread Christopher Faylor
On Thu, Mar 16, 2006 at 01:21:28PM -0700, Cary Jamison wrote: >Christopher Faylor wrote: >>On Tue, Mar 14, 2006 at 05:53:14PM -0700, Cary Jamison wrote: >>>Paul J. Lucas wrote: Is this known to work (or not work)? Apparently, it doesn't. FYI: I'm writing JNI code. The strings passed

Re: fopen with UTF-8 chars in filenames

2006-03-16 Thread Cary Jamison
Christopher Faylor wrote: > On Tue, Mar 14, 2006 at 05:53:14PM -0700, Cary Jamison wrote: >> Paul J. Lucas wrote: >>> Is this known to work (or not work)? Apparently, it doesn't. >>> >>> FYI: I'm writing JNI code. The strings passed from Java to C are >>> UTF-8. A string containing a non-ASCII c

Re: fopen with UTF-8 chars in filenames

2006-03-14 Thread Christopher Faylor
On Tue, Mar 14, 2006 at 05:53:14PM -0700, Cary Jamison wrote: >Paul J. Lucas wrote: >>Is this known to work (or not work)? Apparently, it doesn't. >> >>FYI: I'm writing JNI code. The strings passed from Java to C are >>UTF-8. A string containing a non-ASCII character, e.g., an 'e' with an >>acce

Re: fopen with UTF-8 chars in filenames

2006-03-14 Thread Cary Jamison
Paul J. Lucas wrote: > Is this known to work (or not work)? Apparently, it doesn't. > > FYI: I'm writing JNI code. The strings passed from Java to C > are UTF-8. A string containing a non-ASCII character, e.g., an > 'e' with an accent, works fine with fopen() under Mac OS X. The > same JNI code

fopen with UTF-8 chars in filenames

2006-03-14 Thread Paul J. Lucas
Is this known to work (or not work)? Apparently, it doesn't. FYI: I'm writing JNI code. The strings passed from Java to C are UTF-8. A string containing a non-ASCII character, e.g., an 'e' with an accent, works fine with fopen() under Mac OS X. The same