[Top][All Lists]

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

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

From: Andries E. Brouwer
Subject: Re: [Bug-wget] bad filenames (again)
Date: Tue, 18 Aug 2015 21:11:25 +0200
User-agent: Mutt/1.5.21 (2010-09-15)

On Tue, Aug 18, 2015 at 09:15:40PM +0300, Eli Zaretskii wrote:

> > Otherwise? Leave it as it is?
> No, encode it as %XX hex escapes, thus making the file name pure
> ASCII.  And have an option to leave it "as is", so people who want
> that could have that.

OK, I can live with that.

On Tue, Aug 18, 2015 at 09:32:16PM +0300, Eli Zaretskii wrote:

> Second, Windows stores file names in UTF-16, so it attempts to convert
> the byte stream into UTF-16 assuming the byte stream is in the current
> codepage (which is incorrect in most cases, as we get UTF-8 instead).
> The result is an utmost mess.

Yes, conversion always leads to a problems.
So, I see that you want to use iconv to convert UTF-8 to the current
codepage, so that Windows can convert that to UTF-16 again.
As stated several times already I have zero experience on Windows,
but is it possible to let wget change its current codepage to Unicode
so that the Windows conversion is close to the identity map?
It seems silly to have a double conversion with data loss
if just a format conversion would suffice.


reply via email to

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