X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Message-ID:	<17405074.post@talk.nabble.com>
Date:	Thu, 22 May 2008 07:09:43 -0700 (PDT)
From:	jadooo <vnair AT linx DOT co DOT uk>
To:	cygwin AT cygwin DOT com
Subject:	Re: wstring support in GCC 4.1.2 in Cygwin 1.5.25-11
In-Reply-To:	<4833813A.7B6F7FAF@dessent.net>
MIME-Version:	1.0
X-Nabble-From:	vnair AT linx DOT co DOT uk
References:	<17275355 DOT post AT talk DOT nabble DOT com> <17290164 DOT post AT talk DOT nabble DOT com> <4830F08D DOT 6040505 AT cygwin DOT com> <17345729 DOT post AT talk DOT nabble DOT com> <4833813A DOT 7B6F7FAF AT dessent DOT net>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
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

I just come across one article in google about UTF-8 Cygwin

http://www.okisoft.co.jp/esc/utf8-cygwin/

Just wanted to check about this. As per the documentation here
it says that the Cygwin it is providing will suport Unicode. 

Is it worth to go back and try this out. 


Brian Dessent wrote:
> 
> jadooo wrote:
> 
>> Please let me know if I am doing anything wrong.
> 
> Yes, you are misunderstanding the nature of the problem.
> 
> In order to support the wstring class, gcc relies on the platform's libc
> supporting wide character C99 functions.  newlib does not have the
> necessary support[1] so until that work is contributed, the wstring
> class cannot be enabled in libstdc++.  And even then, you'd have to
> rebuild libstdc++ which means rebuilding all of gcc.
> 
> Cygwin 1.7 currently contains support for unicode characters in
> filenames, but this is a far cry from general wide character string
> support (e.g. wprintf) so simply upgrading to 1.7 will not do anything. 
> Larry's suggestion that this will start working in 1.7 is premature,
> unless somebody contributes the necessary newlib improvements before 1.7
> is released.
> 
> Brian
> 
> [1] For a list of the missing features see
> http://cygwin.com/ml/cygwin-developers/2008-04/msg00094.html
> 
> --
> 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/
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/wstring-support-in-GCC-4.1.2-in-Cygwin-1.5.25-11-tp17275355p17405074.html
Sent from the Cygwin list mailing list archive at Nabble.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/

- Raw text -