Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date: Fri, 17 Oct 2003 15:56:28 +0200
From: Ilya Konstantinov <cygwin AT future DOT shiny DOT co DOT il>
Subject: Widechar file functions
To: cygwin AT cygwin DOT com
Message-id: <20031017135628.GA19242@furr.shiny.co.il>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline
User-Agent: Mutt/1.5.4i

Hello,

It would be nice to have Cygwin use Widechar file functions
such as CreateFileW where possible. Current Cygwin code uses ANSI
functions exclusively, which prevents Cygwin programs from getting
unmodified Unicode filenames from the underlying NTFS/VFAT filesystem.

I assume the correct way is to load the relevant Widechar functions via
GetProcAddress and use them if they exist AND a "Cygwin expects UTF-8
char* in file functions" flag was turned on.
This flag should be runtime rather than compile time, so that each
application could define it for itself.

Are there any plans to make those changes in the near future?
Please Cc me as I'm not subscribed to the list.

P.S. It might be important to note that Microsoft sees the Unicode
variant of its API as the future of the Win32 API.

--
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/