Re: [Bug-wget] Question: It is possible to change/select local filesystem encoding?

[Micah Cowan]

On 10/30/2012 01:30 PM, Ángel González wrote:
> On 30/10/12 19:37, Alex wrote:
>> Greetings, Dmitry Bogatov.
>> Thanks for reply.
>> Yes, thanks it is may be possible to get all files list, convert it to
>> readable codepage and rename files. Sorry,  inertia of thinking - Far
>> 1.75 ever can't find|open this files, so i think that system also
>> (can't operate)/(badly work) with utf-8.
>> Check, it works (don't try mirroring with converting, only  several
>> files)
>>
>> But I still request "--local-filesystem-encoding", if it is possible.
>>
>> Best regars, Alex
> 
> It should be the default. It may be possible to merge it with
> --restrict-file-names

Note that we already have "--local-encoding", which is currently only
used to determine what encoding command-line arguments use. However, I
see no reason why it shouldn't also be the encoding used for transcoding
file names (defaulting to the locale settings in the environment, for
applicable systems).

The main issue would be in making sure that wget can find the files
again, for purposes of such flags as -N or -c, but I don't think that'd
be a difficult problem.

Another question is whether it's plausible that a user would be using a
terminal in a different encoding than their filesystem uses. I would
think the vast majority of cases would be "no", but it's conceivable,
especially if you're saving to an external or networked disk that has
different constraints from your normal operations, so I suppose a
--local-filesystem-encoding would still be useful as a separate option,
but should probably default to what --local-encoding is set to (which,
itself, defaults to what the environment says).

-mjc