On 16 Jan 2002 at 8:02, David Robinson (AU) wrote: > In the meantime, however, '?' is problematic for Win32 users. It stops WGET > from working properly whenever it is found within a URL. Can we fix it > please.
My proposal for using escape sequences in filenames for problem characters is up for discussion at the moment, but I'm not sure if they really need to be reversible (except that it helps to reduce the chances of different URLs being saved to the same filename). Would it be sufficient to map all illegal characters to '@'? For Windows, the code already changes '%' to '@' and it could just as easily change '*', '?', etc. to '@' as well.
