On Mar 3, 2014, at 6:51 PM, Martin Owens wrote:
On Tue, 2014-03-04 at 03:25 +0100, Krzysztof Kosiński wrote:
URIs as used in Glib for file access should contain URL-escaped bytes in the filename encoding, so again there is little potential for error as long as we ignore old / strange Linux.
The functions Glib::filename_from_uri and Glib::filename_to_uri can be used to convert between local filenames and URIs.
OK, I'm going to need at least a few developers to confirm this consensus before I convert everything to using Glib uri handling instead of libxml2. The handling needs to support a few things, not just filenames/paths but also all the rest of the fields libxml2 provides.
Please confirm. std::ustring/GLib::ustring instead of std::string and filename_from_uri instead of libxml2/uri.h
Actually...
In the past we found the uri functions, including those, to be unusable as they strictly adhered to the RFC on URI and would fail/throw (depending on the glib or glibmm versions) on many of the cases we wanted to support
We would need to run some tests on all appropriate non-ASCII filenames to make sure things operate correctly.
Another of the points of failure we was was in the recently opened menu MRU support is a bit touchy in different gtk releases.