Re: Exposing get_filename_charset
- From: Federico Mena Quintero <federico ximian com>
- To: Owen Taylor <otaylor redhat com>
- Cc: "gtk-devel-list gnome org" <gtk-devel-list gnome org>, Alexander Larsson <alexl redhat com>
- Subject: Re: Exposing get_filename_charset
- Date: Thu, 28 Oct 2004 10:55:56 -0500
On Thu, 2004-10-28 at 10:42 -0400, Owen Taylor wrote:
> Well, you wouldn't want exactly that, perhaps, since G_FILENAME_ENCODING
> is defined as a comma-separated list of encodings and
> get_filename_charset() just returns the first one.
>
> The other question is whether we could push down what you are doing
> in Nautilus to GLib with a
> 'g_filename_display_name (const char *filename)' or something like
> that.
Such a function would be very useful.
We also need something for URIs, but encoding for unescaped URIs is not
well defined. See http://bugzilla.gnome.org/show_bug.cgi?id=148620 for
how I "fixed" this in EggRecent --- it simply checks to see if the
unescaped base name is valid UTF-8; otherwise, it replaces invalid
characters by "?".
Also, there's http://bugzilla.gnome.org/show_bug.cgi?id=154695 in which
glib and gnome-vfs disagree on how to escape URIs.
Should we put all the URI-escaping/unescaping and charset conversion
stuff in glib, and simply make gnome-vfs use it? Or are some of thoses
out of the scope of glib?
Federico
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]