Re: [groff] devutf8 on Windows

2019-02-25 Thread Jeff Conrad
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, ev

Re: [groff] devutf8 on Windows

2019-02-25 Thread Eli Zaretskii
On February 25, 2019 11:47:43 AM GMT+02:00, Jeff Conrad wrote: > 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 'wr

Re: [groff] devutf8 on Windows

2019-02-25 Thread Jeff Conrad
On Monday, February 25, 2019 2:09 AM, Eli Zaretskii wrote: > What exactly do you mean by "directly to the console"? Running something like groff -Tutf8 rather than something like groff -Tutf8 | more or groff -Tutf8 > Jeff

Re: [groff] devutf8 on Windows

2019-02-25 Thread Eli Zaretskii
On February 25, 2019 12:17:19 PM GMT+02:00, Jeff Conrad wrote: > On Monday, February 25, 2019 2:09 AM, Eli Zaretskii wrote: > > > What exactly do you mean by "directly to the console"? > > Running something like > > groff -Tutf8 > > rather than something like > > groff -Tutf8 | mor

Re: [groff] devutf8 on Windows

2019-02-25 Thread Jeff Conrad
Monday, February 25, 2019 2:35 AM, Eli Zaretskii wrote: > > Running something like > > > > groff -Tutf8 > > > > rather than something like > > > > groff -Tutf8 | more > > > > or > > > > groff -Tutf8 > > > > > Jeff > > Yes, I tried all of the above. The last method ends up with co

Re: [groff] devutf8 on Windows

2019-02-25 Thread Eli Zaretskii
On February 25, 2019 1:44:07 PM GMT+02:00, Jeff Conrad wrote: > Monday, February 25, 2019 2:35 AM, Eli Zaretskii wrote: > > > > Running something like > > > > > > groff -Tutf8 > > > > > > rather than something like > > > > > > groff -Tutf8 | more > > > > > > or > > > > > > groff -T

Re: [groff] devutf8 on Windows

2019-02-25 Thread Jeff Conrad
On Monday, February 25, 2019 4:03 AM, Eli Zaretskii: > The only explanation I could come up with regarding your simple program is > that VS linked it against static libraries, I’m sure I’m linking statically. > In any case, the conclusion remains that UTF-8 console output on Windows is > unrelia

Re: [groff] devutf8 on Windows

2019-02-25 Thread Eli Zaretskii
> From: Jeff Conrad > CC: "groff@gnu.org" > Date: Mon, 25 Feb 2019 12:12:39 + > > On Monday, February 25, 2019 4:03 AM, Eli Zaretskii: > > > The only explanation I could come up with regarding your simple program is > > that VS linked it against static libraries, > > I’m sure I’m linking s

Re: [groff] devutf8 on Windows

2019-02-25 Thread Ralph Corderoy
Hi Jeff, > Would it then make sense to include a devcp1252, which—though it may > make purists nauseous—would at least give reasonable, reliable output > for a high percentage of documents? I don't have any valid input to that, but to wonder if there's an recode(1) or iconv(1) available to you fo

Re: [groff] devutf8 on Windows

2019-02-25 Thread Jeff Conrad
On Monday, February 25, 2019 7:58 AM, Eli Zaretskii wrote: > > You can verify the results with a dependency walker: > > http://www.dependencywalker.com/ > > Or, if you have GNU Binutils, you do this: > > objdump -x PROGRAM.exe | fgrep "DLL Name:" > > where PROGRAM.exe is your test program.

Re: [groff] devutf8 on Windows

2019-02-25 Thread Jeff Conrad
On Monday, February 25, 2019 7:51 AM, Ralph Corderoy wrote: Hi Ralph, > > Would it then make sense to include a devcp1252 > > I don't have any valid input to that, but to wonder if there's an > recode(1) or iconv(1) available to you for translating to CP 1252 or > transliterating to UCS-2BE with