X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: "Cary Jamison" <Cary_Jamison AT Symantec DOT com>
Subject:  Re: fopen with UTF-8 chars in filenames
Date:  Thu, 16 Mar 2006 13:21:28 -0700
Lines: 29
Message-ID: <dvchcb$p9k$1@sea.gmane.org>
References:  <Pine DOT LNX DOT 4 DOT 63 DOT 0603141507100 DOT 23743 AT vgfl DOT cnhywyhpnf DOT bet> <dv7oht$t87$1 AT sea DOT gmane DOT org> <20060315010359 DOT GD15036 AT trixie DOT casa DOT cgf DOT cx>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

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 character, e.g., an 'e'
>>> with an accent, works fine with fopen() under Mac OS X.  The same
>>> JNI code under Cygwin fails.
>>
>> I'm not positive about this, but you may have to convert the UTF-8 to
>> UTF-16 (Windows unicode) and call wfopen() instead of fopen().  But
>> wfopen() is a Windows call, not a cygwin call :-(
>
> Which would strongly imply that calling wfopen was not the right
> solution for Cygwin.
>
> This is sort of like asking for an expert legal opinion on US law and
> quoting Canadian law...
>
> cgf

True, but at least I gave him options; no one else responded with even a 
'not possible on cygwin.'


Cary




--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/