Boost logo

Boost :

Subject: [boost] [review] Last day to send your review of Nowide (Unicode)
From: Frédéric Bron (frederic.bron_at_[hidden])
Date: 2017-06-21 10:04:12

Dear all,

This is the last day to submit your review of Artyom Beilis' Nowide library.

So far, 12 people participated to the review (not counting the author
and the review manager):
- Andrzej Krzemienski
- Chris Glover
- Degski
- Edward Diener
- Gavin Lambert
- Niall Douglas
- Norbert Wenzel
- Paul Groke
- Peter Dimov
- Vadim Zeitlin
- Yakov Galka
- Zach Laine

8 reviews where received including

* 6 reviews said nowide should be accepted (with conditions):
- Degski,
- Peter Dimov
- Andrzej Krzemienski
- Chris Glover
- Norbert Wenzel
- Yakov Galka

* 1 review did not choose between accept/do not accept:
- Paul Groke

* 1 review said nowide should not be accepted as is:
- Zach Laine

Your participation is encouraged, as the proposed library is
uncoupled, focused and rather small. Nowadays, everyone needs to
handle Unicode but this is very difficult using only the standard
library in a platform independant way. Nowide offers a very simple way
to handle Unicode the same way on

Key features:

* work with UTF-8 in your code, Nowide converts to OS encoding
* Easy to use functions for converting UTF-8 to/from UTF-16
* A class to fixing argc, argc and env main parameters to use UTF-8
* UTF-8 aware functions:
  - stdio.h functions (fopen, freopen, remove, rename)
  - stdlib.h functions (system, getenv, setenv, unsetenv, putenv)
  - fstream (filebuf, fstream/ofstream/ifstream)
  - iostream (cout, cerr, clog, cin)


  git clone

Latest tarballs:
- to be unzipped in boost source:
- as a standalone library:

Nowide has standard boost layout. So, just put it into the boost
source tree under libs/nowide directory for building and running
Or alternatively - for header only part of the library add the
nowide/include path to the include path of your projects.

Please post your comments and review to the boost mailing list
(preferably), or privately to the Review Manager (to me ;-). Here are
some questions you might want to answer in your review:

- 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
- How much effort did you put into your evaluation? A glance? A quick
reading? In-depth study?
- Are you knowledgeable about the problem domain?

And most importantly:
- Do you think the library should be accepted as a Boost library? Be
sure to say this explicitly so that your other comments don't obscure
your overall opinion.

For more information about Boost Formal Review Process, see:

Thank you very much for your time and efforts.


Boost list run by bdawes at, gregod at, cpdaniel at, john at