[Boost-announce] [locale] Formal review of Boost.Locale library starts tomorrow

Subject: [Boost-announce] [locale] Formal review of Boost.Locale library starts tomorrow
From: Chad Nelson (chad.thecomfychair_at_[hidden])
Date: 2011-04-06 17:29:21

The formal review of the Boost.Locale library by Artyom Beilis starts
tomorrow, April 7th, and is scheduled to last through April 16th.

***************
* Its Purpose *
***************

Boost.Locale provides thorough localization features to C++ programs by
way of std::locale facets. Excerpted from the introduction:

    C++ offers a very good base for localization via the existing C++
    locale facets [...] But these are very limited and sometimes buggy
    by design. Support for localization varies [...], and there are
    frequently incompatibilities between them.

    On the other hand, there is a great, well debugged, high quality,
    widely used ICU library that gives all of the goodies. But it has a
    very dated API that mimics Java behavior, completely ignores the
    STL, and provides a useful API only for UTF-16 encoded text,
    ignoring other popular Unicode encodings like UTF-8 and UTF-32 and
    limited but still popular national character sets like Latin1.

    Boost.Locale provides the natural glue between the C++ locales
    framework, iostreams, and the powerful ICU library.

Although it can use the ICU library, it supports several other
processing options as well.

*******************
* Where to get it *
*******************

You can find the "boost_locale_for_review" version here:

    https://sourceforge.net/projects/cppcms/files/boost_locale/

The HTML documentation can also be seen at:

    http://cppcms.sourceforge.net/boost_locale/html/index.html

********************
* Writing a review *
********************

The reviews and all comments should be submitted to the developers list,
and the email should have "[locale]" at the beginning of the subject
line to make sure it's not missed.

Please explicitly state in your review whether the library should be
accepted.

The general review checklist:

    - What is your evaluation of the design?
    - What is your evaluation of the implementation?
    - What is your evaluation of the documentation?
    - What is your evaluation of the potential usefulness of the
      library?
    - Did you try to use the library?  With what compiler?  Did you
      have any problems?
    - How much effort did you put into your evaluation? A glance? A
      quick reading? In-depth study?
    - Are you knowledgeable about the problem domain? 

-- 
Chad Nelson
Oak Circle Software, Inc.
*
*
*