On Monday 21 February 2005 09:49 am, DraÅen KaÄar wrote: > Hrvoje Niksic wrote: > > 2) Server messages printed by Wget in normal operation, such as the > > "200 Ok" message. That one is printed just for the "fun factor" > > anyway, we could as well print just the response code. However, I > > don't see a problem with simply filtering out the non-ASCII's from > > the response code. People who put non-ASCII messages in server > > response lines won't be able to see them properly in Wget's output, > > but I honestly couldn't care less. > > Those messages are using Latin 1. HTTP/1.0 worked that way and it was not > changed in HTTP/1.1 for compatibility reasons. I don't expect that > non-ASCII characters are used much, though. I've only seen the status > messages translated to French, once. > > The Warning header carries text intended for the user and it's the only > such header, AFAIK. Again, text defaults to Latin 1 and the usual MIME-ish > complications can be used for other character sets.
the problem is not with HTTP response messages, but with HTTP resources (which can be for example binary data or multibyte char text - in this case you really want to escape unprintable data while printing all the valid multibyte chars you can using current locale if the user has for instance specified -O -) and eventually with FTP response messages. -- Aequam memento rebus in arduis servare mentem... Mauro Tortonesi University of Ferrara - Dept. of Eng. http://www.ing.unife.it Institute of Human & Machine Cognition http://www.ihmc.us Deep Space 6 - IPv6 for Linux http://www.deepspace6.net Ferrara Linux User Group http://www.ferrara.linux.it
