search

nicehash / nheqminer

Equihash miner for NiceHash
https://www.nicehash.com
MIT License
768 stars 583 forks source link

Windows miner shows OS messages (like errors) in wrong charset, making them unreadable #51

Open the-Arioch opened 8 years ago

the-Arioch commented 8 years ago

see attached screenshot - the texts which should be OS-provided error descriptions are garbled 2016-10-30_00-25-06

Frederic94500 commented 8 years ago

I have the same error but i know what is the problem. The problem is simple, just server down :)

haycoin commented 8 years ago

I tryed eu, usa, jp .... all are down ???

the-Arioch commented 8 years ago

@Frederic94500 the problem in this bug report - is not that the server is down, but that the client garbles the OS-provided error text

I think it should use UNICODE API to write all those messages to screen - the xxxxxxxW half of Win32 functions.

Alternatively, the client should accommodate for locales with GetACP() != GetOEMCP() cases

Kayfolom commented 8 years ago

try http://superuser.com/questions/269818/change-default-code-page-of-windows-console-to-utf-8

the-Arioch commented 8 years ago

@Kayfolom in this specific screenshot the mirendered text clearly is not in UTF-7/UTF-8/UTF-16 charsets, judging by the look (I did not saved text log to pass through mis-coding detectors) it is most probably it is most probably case of 866/1251 screwing.

PS. checked the "шыш => или" hypothesis at www.arbatova.ru/recode.html It is 866/1251 blunder, it is not about Unicode - the Unicode should be implemented by the program code first, then AFAIR console codepage would not matter.

PPS. and yes, I know how to chcp 866 but that is not the point of the bug report :-)