[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-wget] bad filenames (again)

From: Eli Zaretskii
Subject: Re: [Bug-wget] bad filenames (again)
Date: Tue, 18 Aug 2015 18:22:41 +0300

> Date: Mon, 17 Aug 2015 22:51:12 +0200
> From: "Andries E. Brouwer" <address@hidden>
> Cc: "Andries E. Brouwer" <address@hidden>, address@hidden,
>         address@hidden
> On Mon, Aug 17, 2015 at 10:31:13PM +0300, Eli Zaretskii wrote:
> > what do we want to achieve here, and why is what wget did
> > before your patch the wrong thing?
> Wget modified filenames, and users are unhappy.
> See
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=387745
> http://savannah.gnu.org/bugs/?37564
> http://stackoverflow.com/questions/22010251/wget-unicode-filename-errors
> http://stackoverflow.com/questions/27054765/wget-japanese-characters
> http://www.win.tue.nl/~aeb/linux/misc/wget.html
> etc.

There's no argument that wget currently doesn't cope well with these
cases.  The issue being discussed is what should it do instead.

> It is debatable what precisely would be the right thing,
> but my patch greatly increases the number of happy users.

AFAIU, it does that only when the target locale is UTF-8.  By using
iconv we can make wget DTRT in more locales.

> For example, nothing was changed yet for Windows, but also
> Windows users complain about this wget escaping.

If we convert the file names using iconv, Windows users will also be
happier, at least when the remote URL can be encoded in their system
codepage.  (To support characters outside of the system codepage,
deeper changes are needed in the Windows build of wget, for the
reasons I explained elsewhere in this thread.)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]