Zitat von Hrvoje Niksic [EMAIL PROTECTED]:
Only the bare minimum of characters should be encoded. The ones that
come to mind are '/' (illegal), '~' (rm -r ~foo dangerous), '*' and
'?' (used in wildcards), control characters 0-31 (controls), and chars
128-159 (non-printable).
Hrvoje Niksic wrote:
Sorry about the extended absence. I've been extremely busy at work
and will continue to do so for a while.
If someone wants to get write access to apply bug fixes and do
development, please let me know.
It would probably be nice to release 1.9 before doing
George Prekas [EMAIL PROTECTED] writes:
Give some details about file name sanity.
Currently Wget encodes unsafe characters in file names according to
the rules defined for URLs: by replacing unsafe characters with a %hh
representation. The original rationale for this was to prevent
creation
On 2002-07-26 01:59 +0200, Hrvoje Niksic wrote:
Only the bare minimum of characters should be encoded. The ones that
come to mind are '/' (illegal), '~' (rm -r ~foo dangerous), '*' and
'?' (used in wildcards), control characters 0-31 (controls), and chars
128-159 (non-printable).
lobbying
Sorry about the extended absence. I've been extremely busy at work
and will continue to do so for a while.
If someone wants to get write access to apply bug fixes and do
development, please let me know.
It would probably be nice to release 1.9 before doing destablizing
changes. However, I
