> From: Arash Esbati <ar...@gnu.org> > Cc: gavinsmith0...@gmail.com, bug-texinfo@gnu.org > Date: Mon, 03 Apr 2023 18:32:13 +0200 > > > What happens if you invoke 'info' from the default Windows Command > > Prompt window? does the problem persist? > > My build looks like this in cmd.exe:
??? What is your console output codepage set to? Info detects the encoding to be used for the output and attempts to convert the UTF-8 encoded quotes (and other special characters) in the Info file into that encoding. The MinGW build detects the output encoding in the replacement for nl_langinfo function, defined in info/pcterm.c. It is supposed to report the console output codepage, and at least in my case that codepage doesn't support the Unicode quotes. When that happens, Info falls back to ASCII equivalents, see degrade_utf8 in info/scan.c. 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? Also, what is the font you are using on the console? does it support Unicode quotes? > and Msys2 info looks like this: Your MSYS2 Info was built without libiconv, right? > So the problem persists. The only change I see is that Msys2 info shows > only ' for ‘ and ’. That's the ASCII equivalents of the Unicode quote characters in action for you.
