[BUG] Redirected stdout (pipe or file) on windows has wrong encoding about fd

[jeffrson]

I had seen this other report, so I checked chcp which had been 65001 already.

I wasn't aware that this might be a shell related issue, thanks for pointing this out. I'm using PowerShell Core, "Windows PowerShell" (5.1) and cmd behave differently.

Then I found PowerShell/PowerShell#17523 which helped:
[Console]::InputEncoding = [Console]::OutputEncoding = $OutputEncoding = [System.Text.UTF8Encoding]::new($false)

I compared original values of [Console]::OutputEncoding and realized it still was set to codepage 850 (despite chcp 65001).

Anyway, I guess this could be considered "fixed" (non bug) :-)

[tavianator]

That looks like some unholy combination of UTF-8, Latin-1, and codepage 437:

>>> ftfy.fix_and_explain('\x68\xe2\x94\x9c\xc3\xb1\x6c\x66\x74\x65')
ExplainedText(text='hälfte', explanation=[('encode', 'latin-1'), ('decode', 'utf-8'), ('encode', 'cp437'), ('decode', 'utf-8')])

Are you using PowerShell? There was a similar report in #1047 but it was fixed by switching the system to UTF-8. Your system is already on it (codepage 65001) so I don't know why it's not working. Unfortunately I am not a Windows expert so we may need some outside help for this.