From: Graham (Graham_at_[hidden])
Date: 2005-08-19 13:33:34
int_fast32_t char_to_Unicode( char c );
int_fast32_t wchar_to_Unicode( wchar_t c )
will require processing of surrogates on order to be Unicode 4
A Unicode library is currently under development that will give access
to the surrogate ranges directly from the ucd to allow this to be done
Please bear with us.
>Date: Fri, 19 Aug 2005 17:15:03 +0400
>From: Vladimir Prus <ghost_at_[hidden]>
>Subject: Re: [boost] Should we add two simple character-to-Unicode
>Content-Type: text/plain; charset=us-ascii
>Daryle Walker wrote:
>> Nothing fancy, just something like:
>> int_fast32_t char_to_Unicode( char c );
>> int_fast32_t wchar_to_Unicode( wchar_t c );
>> that converts a native character to a Unicode value.
>Maybe, but it's hard to comment as you haven't even explained what
>function will do. What's a "native character" and what a "Unicode
>and how the conversion will be done? If the first function does
>from local 8 bit encoding to unicode then:
> - do you have a working implementation?
> - isn't dealing with individual characters too slow?
BEng, ACGI, MCSD/ MCAD .Net, MCSE/ MCSA 2003, CompTIA Sec+
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk