On Monday 21 February 2005 04:23 pm, Hrvoje Niksic wrote: > Mauro Tortonesi <[EMAIL PROTECTED]> writes: > >> 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 that weren't safe, Wget would (along with many other programs) have > been broken a long time ago. In fact, if that were the case, I would > never have even accepted adding support for gettext in the first > place.
well, theoretically it could happen. suppose gettext returns UTF16 encoded string for example... ;-) -- 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
