[Bug-wget] SINGLE QUOTE in wget output is replaced by UTF-8 value of SINGLE QUOTE

2012-08-09 Thread Avinash
Hi, 1) I have taken wget-1.12 source 2) Have built a rpm on top of this source for FEDORA CORE 3 3) It get installed correctly on FC3 and wget downloads files as well 4) But the output of wget shows UTF-8 value of SINGLE QUOTE instead of showing SINGLE QUOTE i.e. ' It shows 2012-08-09 16:24:37

Re: [Bug-wget] SINGLE QUOTE in wget output is replaced by UTF-8 value of SINGLE QUOTE

2012-08-09 Thread Petr Pisar
On Thu, Aug 09, 2012 at 04:50:46PM +0530, Avinash wrote: 2) Have built a rpm on top of this source for FEDORA CORE 3 Do you know this is really ancient piece of software? 3) It get installed correctly on FC3 and wget downloads files as well 4) But the output of wget shows UTF-8 value of

Re: [Bug-wget] SINGLE QUOTE in wget output is replaced by UTF-8 value of SINGLE QUOTE

2012-08-09 Thread Avinash
locale is UTF-8, but it was true with wget-1.10.2-0 as well. If I install 'wget-1.10.2-0' RPM then SINGLE QUOTE is not replaced even though locale is UTF-8. When I install 'wget-1.12-0'(created on top of 1.12 source) then only I see the issue. 2012-08-09 16:24:37 (13.3 MB/s) -

Re: [Bug-wget] SINGLE QUOTE in wget output is replaced by UTF-8 value of SINGLE QUOTE

2012-08-09 Thread Jochen Roderburg
Zitat von Petr Pisar petr.pi...@atlas.cz: On Thu, Aug 09, 2012 at 06:02:55PM +0530, Avinash wrote: locale is UTF-8, but it was true with wget-1.10.2-0 as well. If I install 'wget-1.10.2-0' RPM then SINGLE QUOTE is not replaced even though locale is UTF-8. When I install 'wget-1.12-0'(created

[Bug-wget] wget1.14: warc.c: compilation fails due to C++ comments

2012-08-09 Thread John Cornes
Dear Maintainers, I'd like to report a minor issue: when compiling wget 1.14 on AIX 7.1 configured with --disable-ssl, using V12.1 of IBM's XL C for AIX compiler, compilation failed in warc.c due to the presence of C++ style comments (//): warc.c, line 535.3: 1506-046 (S) Syntax error. warc.c,

Re: [Bug-wget] Connection closed vs read error

2012-08-09 Thread Micah Cowan
On 08/09/2012 12:42 AM, ptrk mj wrote: Greetings everyone, I'd like to know what is the technical difference between Connection closed at byte x. and Read error at byte x/y (Connection timed out). AIUI, Connection closed at byte x means that the remote end closed the connection while

Re: [Bug-wget] Connection closed vs read error

2012-08-09 Thread ptrk mj
Thanks for sheding light on it. It's important to understand what's going on. ptrkmj On 8/9/12, Micah Cowan mi...@cowan.name wrote: On 08/09/2012 12:42 AM, ptrk mj wrote: Greetings everyone, I'd like to know what is the technical difference between Connection closed at byte x. and Read