Am 19.09.2010 15:16, schrieb Torsten Schoenfeld:
utf8::decode() fixes this because it sets the utf8 flag (and avoids
double encoding).
Does this mean that it is safe to keep my workaround (utf8::decode) even
though the error gets fixed in a new release?
On 20.09.2010, at 09:58, Mario Kemper wrote:
Am 19.09.2010 15:16, schrieb Torsten Schoenfeld:
utf8::decode() fixes this because it sets the utf8 flag (and avoids
double encoding).
Does this mean that it is safe to keep my workaround (utf8::decode)
even though the error gets fixed in a new
On 16.05.2010 17:42, Mario Kemper wrote:
However, it doesn't seem to return a valid utf-8 string, e.g. german
umlauts are not correctly displayed. I've attached an example program
where this problem is illustrated. If a use utf8::decode on the returned
string everything is fine.
That's indeed
Hi,
I've a simple question about the correct usage of
Gnome2::VFS-format_uri_for_display.
This is what the docs say:
Filter, modify, unescape and change URIs to make them appropriate to
display to users. The conversion is done such that the roundtrip to
UTF-8 is reversible.
Returns : a newly
