On 5 Jul 2000, Lars Gullik Bjønnes wrote:
> | How exactly this should be done? I'm thinking of the following:
> | In encoding.h (or elsewhere):
> | typedef short int Uchar;
> | typedef std::vector<Uchar> Ustring;
>
> This is not enough, we also need to create char_traits<Uchar>
> (also that is bad... be want to use the basic_string to make strings,
> not std::vector)
If we consider a move to unicode in the base code it might be a good idea
to take a look at ustring which is a GPL implementation of a string class
which uses unicode characters.
Following is it's ANNOUNCE file:
======
The ustring C++ Unicode library provides a set of class
(http://ustring.sourceforge.net)
Description :
ustring targets the complete conformance of the Unicode 3.0
standard. It gives an easy access to the properties of each of the
10600 characters defined by the Unicode 3.0 standard (such as
uppercase or lowercase mapping, category and subcategory, character
name, bidirectional category, etc.). It provides an stl-compliant wide
string class, which implements a full Unicode normalizer, uppercase or
lowercase transformation, diacritical marks removing, etc. A Unicode
level-1 Regular Expression class is also provided.
--
Baruch Even
http://techst02.technion.ac.il/~sbaruch/ (My Site)
http://rpghost.com/jindor/ (My brothers AD&D site)
" Learn to laugh ... it's the path to true love! "
- The Angel in the movie Michael
