From: Miro Jurisic (macdev_at_[hidden])
Date: 2004-10-19 00:50:54
In article <cl268e$okv$1_at_[hidden]>, "Robert Ramey" <ramey_at_[hidden]> wrote:
> I think you should spend a little more time investigating the following:
> a) The "vault" files section has code by A Barbati which addresses issue
> related to unicode.
> b) Ron Garcia contributed codecvt facets for unicode that have been
> incorporated into boost are currently used by two boost libraries
> (serialization and program options.)
> c) asni library functions exist for converting strings and characters
> to/from wstrings/wchar s in accordance with the currently selected locale.
> Not all libraries implement these functions however.
> So its not clear to me what exactly needs to be done here - other than
> fixing up some older stdandard libraries. I don't think that's what you had
> in mind.
There is a lot Unicode work to be done in the standard C++ library and boost.
C++ currently has no Unicode-aware string abstraction, and this is a big problem
for anyone who has to deal with Unicode strings in C++ code. std::string is
poorly suited for any Unicode-savvy work, for many reasons -- mainly having to
do with the fact that std::string and STL and boost algorithms using
std::string::iterator don't know how to handle strings in accordance with the
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk