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

[Eli Zaretskii]

> 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.

> > What do you get from rpl_nl_langinfo in your case, and what happens in
> > copy_converting, where degrade_utf8 is supposed to be called when
> > Unicode quotes aren't supported?
> 
> Sorry, I don't follow.  What should I do in order to answer the question
> above?

Run info.exe under a debugger and step into the functions I mentioned
to see what's going on there.  Is your info.exe built with libiconv,
btw?

> > Also, what is the font you are using on the console? does it support
> > Unicode quotes?
> 
> In cmd.exe, it is Consolas, in Terminal, it is SourceCodePro.  They both
> support Unicode quotes.  But cmd.exe doesn't show them.  This small
> text file (dir.txt):
> 
>   10.2 ‘dir’: Briefly list directory contents
>   ===========================================
> 
>   ‘dir’ is equivalent to ‘ls -C -b’; that is, by default files are listed
>   in columns, sorted vertically, and special characters are represented by
>   backslash escape sequences.
> 
>      *Note ‘ls’: ls invocation.
> 
> looks like this in cmd.exe with 'type dir.txt' or 'more dir.txt':

This is because the text is encoded in UTF-8, and cmd.exe assumes it's
encoded in codepage 850.  This is not relevant.

> cat dir.txt in bash works as expected.

"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.)