Date: Sat, 29 Jan 2011 19:28:18 +0100
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com, bug-gnu-libiconv@gnu.org
Subject: Re: Bug in libiconv?
Message-ID: <20110129182818.GD1057@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com, bug-gnu-libiconv@gnu.org
Mail-Followup-To: cygwin@cygwin.com, bug-gnu-libiconv@gnu.org
References: <201101282312.50298.bruno@clisp.org> <20110129123014.GA8671@calimero.vinschen.de> <4D442DDA.4050807@redhat.com> <20110129160157.GA1057@calimero.vinschen.de> <4D444CAC.2010300@redhat.com> <20110129181231.GC1057@calimero.vinschen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20110129181231.GC1057@calimero.vinschen.de>
User-Agent: Mutt/1.5.21 (2010-09-15)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Jan 29 19:12, Corinna Vinschen wrote:
> On Jan 29 10:21, Eric Blake wrote:
> > In other words, cygwin IS being POSIX-compliant by advertising only the
> > Unicode 4.0 character set in the __STDC_ISO_10646__, while still

Btw., you are aware that Unicode 4.0 already defines more characters than
fit into the base plane, aren't you?

I chose the value in an attempt to be carefully conservative.  I'm not
100% sure if that's the right thing to do...

> > supporting Unicode 5.2 (should we upgrade to Unicode 6.0?) as an

Yeah, how could we live without emoticons all the time ;-)

But, sure, it would be nice to get contributions to to support 6.0
in the wctype functions.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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