[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug-wget] --remote-encoding and --local-encoding seem to have no effect
From: |
jean-christophe.coynel |
Subject: |
[Bug-wget] --remote-encoding and --local-encoding seem to have no effect for FTP transfer |
Date: |
Wed, 23 Dec 2009 04:33:49 +0100 (CET) |
Hello,
I am using wget to perform a daily backup of my website hosted remotely. This
is done using FTP.
The names of some folders contain accented characters, and despite the fact
that I do have wget 1.12 with NDI support enabled, I always get corrupt file
names on my local copy. The OS is Ubuntu 9.10, here is a sample of the wget
output :
--2009-12-23 04:11:22--
ftp://xxx.net/Hangzhou%2C%20ao%FBt%202006/DSC_3983%20copy.jpg
=> «xxx.net/Hangzhou, ao\373t 2006/DSC_3983 copy.jpg»
regardelss of the values I use for --local-encoding or --remote-encoding, this
does not seem to have any effect : the local file names are corrupt the exact
same way. Using options like --restrict-file-names does seem to have some
effect (but does not solve my problem)
For what it is worth, I had a quick look at the code and it seemd that ftp.c
does not have any reference to any of those options, while it seems there is
for http.c. Maybe this is not implemented in FTP?
Does anybody have a suggestion?
Thank you.
V.
Laposte.net vous souhaite de Joyeuses Fêtes de fin d'année.
Je crée ma boîte mail www.laposte.net
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Bug-wget] --remote-encoding and --local-encoding seem to have no effect for FTP transfer,
jean-christophe.coynel <=