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 13:14:57 -0400
From: Christopher Faylor <cgf-rcm AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Cc: cygwin AT future DOT shiny DOT co DOT il
Subject: Re: Widechar file functions
Message-ID: <20031017171457.GB10723@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com, cygwin AT future DOT shiny DOT co DOT il
References: <20031017135628 DOT GA19242 AT furr DOT shiny DOT co DOT il>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20031017135628.GA19242@furr.shiny.co.il>
User-Agent: Mutt/1.4.1i
Note-from-DJ: This may be spam

On Fri, Oct 17, 2003 at 03:56:28PM +0200, Ilya Konstantinov wrote:
>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.

There is a lot more involved than that.  Many C strings would need to be
changed to Unicode.  This is a huge change.

>Are there any plans to make those changes in the near future?

No, there are no such plans.

cgf
--
Please use the resources at cygwin.com rather than sending personal email.
Special for spam email harvesters: send email to aaaspam AT sourceware DOT org
and be permanently blocked from mailing lists at sources.redhat.com

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