Re: [Nautilus-list] [PATCH] location bar autocompletion
- From: Alex Larsson <alexl redhat com>
- To: David Emory Watson <dwatson cs ucr edu>
- Cc: nautilus-list lists eazel com, <gnome-vfs ximian com>
- Subject: Re: [Nautilus-list] [PATCH] location bar autocompletion
- Date: Mon, 25 Feb 2002 17:26:08 -0500 (EST)
On Mon, 25 Feb 2002, David Emory Watson wrote:
(David, I'll do the review later)
> On Sat, 2002-02-23 at 18:09, Alex Larsson wrote:
> > You need some more changes to handle the fact that all strings (even
> > filenames) in Nautilus now are in UTF8. This means that all arguments to
> > GtkEntry and GtkEditable that specify positions in the strings are
> > measured in number of characters from the start (called position), not the
> > number of bytes from the start (called index).
> Done. I only changed the code for "user visable strings" so uri's and
> strings created by gnome_vfs are still assumed to be straight ASCII.
What is the current assumptions about the encoding of gnome-vfs URIs?
Naturally escaped ones should be treated as ASCII only, but what happens
when you unescape them. How do we display them in e.g. nautilus? We can't
really rely on them being UTF8, since that might not work for non-file
In general, Gtk+ 2 / Gnome 2 treats local filenames as always in UTF8,
unless the G_BROKEN_FILENAMES environment variable is set.
Darin, how have you hadled these kinds of issues in nautilus before?
] [Thread Prev