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:  Tue, 14 Mar 2006 17:53:14 -0700
Lines: 17
Message-ID: <dv7oht$t87$1@sea.gmane.org>
References:  <Pine DOT LNX DOT 4 DOT 63 DOT 0603141507100 DOT 23743 AT vgfl DOT cnhywyhpnf DOT bet>
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

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 :-(


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/