Hi,
I read the planned Metalink support in wget, so I post this message.
I've started the project named libmetalink, which is a Metalink library
written in C language. It is intended to provide the programs written in
C to add Metalink functionality such as parsing Metalink XML files.
The
Micah Cowan wrote:
Unfortunately, nothing really comes to mind. If you'd like, you could
file a feature request at
https://savannah.gnu.org/bugs/?func=additemgroup=wget, for an option
asking Wget to treat URLs case-insensitively.
To have the effect that Allan seeks, I think the option would
standard: the URL are case-insensitive
you can adapt your software because some people don't respect standard,
we are not anymore in 90's, let people doing crapy things deal with
their crapy world
Cheers!
On Fri, Jun 13, 2008 at 2:08 PM, Tony Lewis [EMAIL PROTECTED] wrote:
Micah Cowan wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tony Lewis wrote:
Micah Cowan wrote:
Unfortunately, nothing really comes to mind. If you'd like, you
could file a feature request at
https://savannah.gnu.org/bugs/?func=additemgroup=wget, for an
option asking Wget to treat URLs
In the VMS world, where file name case may matter, but usually
doesn't, the normal scheme is to preserve case when creating files, but
to do case-insensitive comparisons on file names.
From Tony Lewis:
To have the effect that Allan seeks, I think the option would have to
convert all URIs to
mm w wrote:
standard: the URL are case-insensitive
you can adapt your software because some people don't respect standard,
we are not anymore in 90's, let people doing crapy things deal with
their crapy world
You obviously missed the point of the original posting: how can one
conveniently
Steven M. Schweda wrote:
From Tony Lewis:
To have the effect that Allan seeks, I think the option would have to
convert all URIs to lower case at an appropriate point in the process.
I think that that's the wrong way to look at it. Implementation
details like name hashing may also need
Hi, after all, after all it's only my point of view :D
anyway,
/dir/file,
dir/File, non-standard
Dir/file, non-standard
and /Dir/File non-standard
that's it, if the server manages non-standard URL, it's not my
concern, for me it doesn't exist
On Fri, Jun 13, 2008 at 3:12 PM, Tony Lewis [EMAIL