Re: Glib::ustring tradeoffs?

[Frank Naumann <fnaumann boerde de>]

Hello!

> Since there is a operator std::string() in Glib::ustring you will be abled 
> using everything what wants a std::string, but I don't think that neither 
> the algorithms nor boost::filesystem will work with a utf8 encoding. So you 
> might use locale_from_utf and locale_to_utf functions to convert between 
> encodings if it possible at all.

For paths and filenames it's better to use Glib::filename_from_utf8 and
Glib::filename_to_utf8, e.g. convert to/from utf8 if you pass data in/out 
from gtkmm.


Regards,
Frank