Re: Glib::ustring tradeoffs?



Dear Matthias,

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.

Best Regards,

Vinzenz 'evilissimo' Feenstra

Matthias Kaeppler schrieb:

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

_______________________________________________
gtkmm-list mailing list
gtkmm-list gnome org
http://mail.gnome.org/mailman/listinfo/gtkmm-list







[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]