Mac Os X could have some special characters. Future OSs could have some special characters. A BeOs port could appear.
If wget is going down that road (would be really nice) I'm wondering if it would be "better" having a/several internal defaults (general unix and windows at least) AND some way to specifiy a different table in .wgetrc - this would end the hassle for everybody who's changing the default currently because he's mirroring something and doesn't want ~ to be encoded, or because wget is mirroring on unix but exporting to windows with samba, or has just some special needs. Heiko -- -- PREVINET S.p.A. [EMAIL PROTECTED] -- Via Ferretto, 1 ph x39-041-5907073 -- I-31021 Mogliano V.to (TV) fax x39-041-5907087 -- ITALY > -----Original Message----- > From: Hrvoje Niksic [mailto:[EMAIL PROTECTED]] > Sent: Friday, December 07, 2001 4:24 PM > To: Wget List > Subject: Re: wget 1.8beta - handling of non-ascii characters in URL > > > Andre Majorel <[EMAIL PROTECTED]> writes: > > > Which of course is another can of worms because it's heavily > > platform dependant. Apparently FAT and VFAT do not have the same set > > of forbidden characters. > > Then maybe such processing will be in a totally independent table and > function, so that it can be implemented differently for different file > systems. In reality, we will hopefully only need to differentiate > between Unix-like and Windows-like file systems. >
