CVSROOT:        /cvs/gnome
Module name:    gnome-vfs
Changes by:     tml     05/09/29 08:34:30

Modified files:
        .              : ChangeLog 
        libgnomevfs    : gnome-vfs-configuration.c gnome-vfs-method.c 
                         gnome-vfs-uri.c 

Log message:
2005-09-29  Tor Lillqvist  <[EMAIL PROTECTED]>

* libgnomevfs/gnome-vfs-configuration.c
* libgnomevfs/gnome-vfs-method.c: Include
gnome-vfs-private-utils.h on Win32 to get the redefinitions of
GNOME_VFS_SYSCONFDIR and GNOME_VFS_LIBDIR so that we don't have
compile-time pathnames in the binary, and install-anywhere
actually works.

* libgnomevfs/gnome-vfs-uri.c (gnome_vfs_uri_new): Simplify the
Win32 code. Don't call gnome_vfs_escape_path_string() as the Unix
code doesn't either. Just turn backslashes into slashes.

I am still not sure whether it is correct for all use cases,
though. Unfortunately much GNOME software mixes URIs and pathnames
rather freely (which mostly works on Unix where pathname syntax
matches the local part of a file: URI). The parameter to this
function is called text_uri, and said to be "a string representing
a URI". What does that mean? Is it actually a pathname in the
so-called GLib file name encoding (on-disk encoding on Unix, UTF-8
on Windows), or a URI that already is properly URI-escaped?
Apparently currently it can be either, sigh.

URL : 
http://cvs.gnome.org/bonsai/cvsquery.cgi?branch=&dir=gnome-vfs&who=tml&date=explicit&mindate=2005-09-29%2008:33&maxdate=2005-09-29%2008:35

_______________________________________________
cvs-commits-list mailing list
cvs-commits-list@gnome.org
http://mail.gnome.org/mailman/listinfo/cvs-commits-list

Reply via email to