Re: info '(latex2e)\indent & \noindent' doesn't work with Msys2

[Arash Esbati]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Arash Esbati <arash@gnu.org>
>> Cc: GavinSmith0123@gmail.com,  bug-texinfo@gnu.org
>> Date: Tue, 04 Apr 2023 09:35:07 +0200
>> 
>> > ??? What is your console output codepage set to?
>> 
>>   C:\>chcp
>>   Aktive Codepage: 850.
>
> That's likely the problem: this codepage doesn't support Unicode
> quotes.  What remains to be understood is why doesn't info.exe act
> accordingly.

Yes, this seems to be the issue.  In my bash (MinGW64 shell running
inside Windows Terminal), I did:

  $ chcp.com 1252
  $ /c/pathto/my/native/info.exe dir-test-no-coding

which looks like this:

The other file provided by Gavin and my first example with dir look also
good.  So Eli is right here with why info.exe doesn't DTRT with codepage
850.

> Run info.exe under a debugger and step into the functions I mentioned
> to see what's going on there.

Ok, I will give it a try.

> Is your info.exe built with libiconv, btw?

I only pass a --prefix to configure and looking at config.log, it has:

  configure:11566: checking how to link with libiconv
  configure:11568: result: -liconv
  configure:11579: checking whether iconv is compatible with its POSIX signature
  configure:11604: gcc -c -g -O2  conftest.c >&5
  configure:11604: $? = 0
  configure:11613: result: yes

So I'd say yes.

> "In bash" when using what console window?  (Please always state these
> facts, because otherwise what you tell is ambiguous and can easily
> mislead.  This issue is complicated and messy enough already, we don't
> need more complications and confusions.)

Sure, sorry for being imprecise.  My setup is all the time bash in a
MinGW64 shell using Windows Terminal.  I start bash like this:

  c:/msys64/msys2_shell.cmd -defterm -no-start -mingw64

where -defterm means don't use mintty.

Best, Arash