Older wget versions did some some other character translation, but that had other bigger sideeffects, and has been partially substituted by the current translation table. Some time ago there had been extensive discussions regarding this (at the time of Dan iirc), and there had been some agreement there wasn't any perfect solution working for every case except if wget keeps an external database (say, a file in every directory) where to record exactly which translations have been made, in order to be able to send back the correct urls to web servers when necessary. 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: Alan Eldridge [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, December 18, 2001 3:35 PM > To: Herold Heiko > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: Re: parameters in the URL > > > On Tue, Dec 18, 2001 at 03:11:51PM +0100, Herold Heiko wrote: > >More probably the usual (sigh) file system unusuable > character problem ( > >'?' in this case ). I can;t do it now, try something like > > Depends. Not on Unix: the only character not allowed in a > filename is '/'. > > A Micro$**t OS? Then that's probably it, and wget should > %-escape those > characters (translating back and forth as necessary for -nc checking). > > -- > Alan Eldridge > Just another $THING hacker. >
