Eli, On Sunday, February 24, 2019 7:53 AM, Eli Zaretskii wrote:
> It is a known problem with the Windows console: you cannot reliably > write UTF-8 encoded text to it using the ANSI/Posix emulation > functions like 'write', 'printf', and their C++ equivalents, and > expect the correct display, even if you set the codepage to 65001. > You need to use Unicode (a.k.a. "wide") APIs instead, like WriteFileW > etc., and you need to feed them text converted into UTF-16. > > This is not a Groff problem, the problem is with the Windows console > device. In all the excitement, I somehow missed the obvious question: do you get similar results if you send grotty output directly to the console, either with cmd or a *nix-type shell? Regards, Jeff
