RE: wget 1.8beta - handling of non-ascii characters in URL

2001-12-10 Thread Herold Heiko
cember 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. Apparen

Re: wget 1.8beta - handling of non-ascii characters in URL

2001-12-07 Thread Hrvoje Niksic
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 ca

Re: wget 1.8beta - handling of non-ascii characters in URL

2001-12-07 Thread Andre Majorel
On 2001-12-07 15:10 +0100, Hrvoje Niksic wrote: > But: a character being unsafe for URL doesn't mean that the same > character must be unsafe for the file name. Wget currently contains > the two, and that's a bug. I'll try to fix that bug by adding another > bitflag to the table, e.g. "F" which

Re: wget 1.8beta - handling of non-ascii characters in URL

2001-12-07 Thread Hrvoje Niksic
Jochen Roderburg <[EMAIL PROTECTED]> writes: > Do I understand you right? You mean it is a new feature of the wget > version 1.8 that the brackets are now promoted to 'unsafe > characters' ? You are both right. Yes, Wget is giving the brackets the status of unsafe chars because rfc1738 mandates

Re: wget 1.8beta - handling of non-ascii characters in URL

2001-12-06 Thread Lachlan Cranswick
At 22:16 06/12/01 +0100, Jochen Roderburg wrote: >> >> You could be describing a feature here - on how WGETn handles unsafe >> characters. >> >> >wget.18 http://www.polscan.hg.pl/scans/[GmbH]_Scenery_9.csv >> >--21:40:51-- http://www.polscan.hg.pl/scans/%5BGmbH%5D_Scenery_9.csv >> >

Re: wget 1.8beta - handling of non-ascii characters in URL

2001-12-06 Thread Jochen Roderburg
> > You could be describing a feature here - on how WGETn handles unsafe > characters. > > >wget.18 http://www.polscan.hg.pl/scans/[GmbH]_Scenery_9.csv > >--21:40:51-- http://www.polscan.hg.pl/scans/%5BGmbH%5D_Scenery_9.csv > > => `%5BGmbH%5D_Scenery_9.csv' > > Do I understand you

Re: wget 1.8beta - handling of non-ascii characters in URL

2001-12-06 Thread Lachlan Cranswick
You could be describing a feature here - on how WGETn handles unsafe characters. I have modified my WGET 1.7 webpage with information on how you can turn this off in the compiling for designated characters: http://www.ccp14.ac.uk/mirror/wget.htm Under: Optimising and Compiling WGET

wget 1.8beta - handling of non-ascii characters in URL

2001-12-06 Thread Jochen Roderburg
Hello wget developers, Found a new bug in wget 1.8 beta: wget.17 http://www.polscan.hg.pl/scans/[GmbH]_Scenery_9.csv --21:39:00-- http://www.polscan.hg.pl/scans/%5BGmbH%5D_Scenery_9.csv => `[GmbH]_Scenery_9.csv' wget.18 http://www.polscan.hg.pl/scans/[GmbH]_Scenery_9.csv --21:40:51-