Re: w3 on native-build mswindows
Jonathan Harris <jhar(a)tardis.ed.ac.uk> writes:
The enclosed patch against package version 1.06 of w3 makes w3
mostly
work on the native mswindows build of XEmacs. The patched function
url-basepath has actually changed since 1.06 so this patch won't apply,
but that's OK beause I'm really just asking for advice.
The problem that the patch fixes is that w3 calls XEmacs path handling
functions on URL paths. That doesn't work under mswindows because these
path handling functions convert path separators into '\\' because that is
the native path separator on Win32. The attached patch replaces two
occurrences in url-basename of such calls with manual string-matches.
I would say that the file munging routines under win32 should NOT change
the path separators. They should leave them the same as what they got.
So:
(file-name-directory "/foo/bar/baz")
=> "/foo/bar"
(file-name-directory "\\foo\\bar\\baz")
=> "\\foo\\bar"
(file-name-nondirectory "/foo/bar/baz")
=> "baz"
Alternatively, is there a better approach than manually replacing
selective calls to XEmacs path handling functions with string matches?
I would ask someone to implement the above... at least for
the file-name-(non)*directory functions.
-bill p.