On Monday 21 February 2005 02:37 pm, you wrote: > Mauro Tortonesi <[EMAIL PROTECTED]> writes: > >> It is rather common that either the charset at the remote host or > >> the charset at the local host are set incorrectly. > > > > this is not a problem. actually (apart from the case of a document > > returned as an HTTP response) we cannot be sure that the charset > > used by the server is exactly our locale. the only two reasonable > > things we can do are: > > > > - assume all data is ASCII > > - assume all data is in our locale charset > > We should simply do the former, and escape non-ASCII stuff. See my > previous message for a more elaborate explanation of why that is > correct.
ok. > > the second assumption allows us to avoid problems like this one: > > > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=271931 > > The only reason why that bug occurred was the broken "hotfix" that > escaped *all* non-ASCII content printed by Wget, instead of only that > actually read from the network. We don't need iconv to fix that, we > need correct quoting. yes, you may be right. but simone and i were wondering if the interpolation of (even ASCII) data received by the server inside a string retrieved using gettext is safe. if we are using multi byte chars string with gettext then we may be in trouble. that's the reason for which we wanted to encode all wget internal strings using UTF8. -- 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
