Herold Heiko [EMAIL PROTECTED] writes:
Yes, the windows and dos version (OS/2 too ?) can't use :,
so if we need
to choose a separator we could as well choose something which does
create as few as possible problems on most platforms.
Even if this does mean a slightly different syntax than the
"Dan Harkless" [EMAIL PROTECTED] writes:
I think the most straightforward mapping would also be the most attractive:
ftp/site/dir/file
http/site/dir/file
Don't forget the port, if you aim for completeness.
Wget should certainly have an option to make it behave this way. In
Hrvoje Niksic [EMAIL PROTECTED] writes:
"Dan Harkless" [EMAIL PROTECTED] writes:
I think the most straightforward mapping would also be the most attractive:
ftp/site/dir/file
http/site/dir/file
Don't forget the port, if you aim for completeness.
Yeah, you've probably seen
Hrvoje Niksic [EMAIL PROTECTED] writes:
"Dan Harkless" [EMAIL PROTECTED] writes:
Well, it wouldn't be very tough for them to adjust their archives by
moving the hostname directories into "ftp" or "http" directories.
Or else use the option that makes it leave off the protocol.
As long
Herold Heiko wrote:
I think the most straightforward mapping would also be the
most attractive:
ftp/site/dir/file
http/site/dir/file
Wget should certainly have an option to make it behave this
way. In fact,
I'd prefer it to behave that way by default, for the reasons
you
Jan Prikryl [EMAIL PROTECTED] writes:
Quoting Dan Harkless ([EMAIL PROTECTED]):
I don't see why we would use an '_' instead of a ':' on the second version
(except on Windows if the ':' character is a no-no there).
The colon is a relict of DOS path notation (C:\) so it cannot
appear
On Fri, 9 Feb 2001, Dan Harkless wrote:
Jan Prikryl [EMAIL PROTECTED] writes:
The colon is a relict of DOS path notation (C:\) so it cannot
appear in a filename.
Fine, but I'm not really up for obfuscating the URLs on UNIX just to make
DOS/Windows happy. Already the Windows port
