Glib::ustring tradeoffs?

[Matthias Kaeppler <matthias finitestate org>]

Hi,

I am considering to completely remove std::string from my application in 
favor of Glib::ustring, but I stumbled across some problems:
For one, I am using STL algos such as std::lexicographical_compare. Will 
they work with a Glib::ustring?
Also I am using boost::filesystem, which is based around std::string. I 
guess it doesn't make sense to use both the functions from 
boost::filesystem AND Glib::ustring, because boost::fs will probably 
break as soon as I'm feeding it with Unicode strings?

What are your thoughts about this?

Regards,
Matthias