bug-wget
[Top][All Lists]
Advanced

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

Re: [Bug-wget] GNU wget 1.17.1 released


From: Ander Juaristi
Subject: Re: [Bug-wget] GNU wget 1.17.1 released
Date: Sun, 13 Dec 2015 14:08:10 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0

Hi Andries,

On 12/11/2015 09:03 PM, Andries E. Brouwer wrote:
On Fri, Dec 11, 2015 at 08:22:23PM +0100, Giuseppe Scrivano wrote:
Hello,

I am pleased to announce the new version of GNU wget.  We consider it a
bug fixes release as it addresses issues found in 1.17, which contained
quite a few new features.

Please report any problem you may experience to the address@hidden
mailing list.

Four months ago I mentioned two bugs:
1. Non-ASCII filenames are mistreated
2. The progress bar is broken when the filename is non-ASCII.
And I provided patches that fix 2, and fix 1 on Unix.

Tim Ruehsen polished the second patch a bit more, and then
nothing more was heard about it.
The first patch was for Unix, and there was some amount of discussion
of the Windows situation with Eli Zaretskii. But nobody offered
a Windows patch, and my patch is OK, but Unix-only.


True.

For me, there's no problem in applying the patch for Unix only (disable the 
code on Windows via preprocessor firewalling) and it'll be ready when we 
release 1.17.2. And in the meanwhile maybe someone comes with a working windows 
port.

What do the others think?

Now that wget-1.17.1 is out, let me try it on the Russian Wikipedia page
for the page "heart", Сердце, the same example we used last August.

With my patch I get:

Saving to: ‘Сердце’

With wget-1.17.1 I get:

% wget/wget-1.17.1/src/wget 
https://ru.wikipedia.org/wiki/%D0%A1%D0%B5%D1%80%D0%B4%D1%86%D0%B5

Saving to: ‘Се\321%80д\321%86е’.
Here wget saves to a name that is not a legal name on this filesystem.
The progress bar is still broken and contains illegal characters.

So, I find that wget-1.17.1 is still broken, and no good for downloading
files with UTF-8 filename from an UTF-8 site to a local UTF-8 site.
There is some default built-in ISO 8859-* ugliness.

Andries


Regards,
- AJ



reply via email to

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