[GHC] #10762: On Windows, out-of-codepage characters can cause GHC build to fail

[GHC]

#10762: On Windows, out-of-codepage characters can cause GHC build to fail
---------------------------------+-----------------------------------------
        Reporter:  snoyberg      |                   Owner:
            Type:  bug           |                  Status:  new
        Priority:  normal        |               Milestone:
       Component:  Compiler      |                 Version:  7.10.2
      Resolution:                |                Keywords:
Operating System:  Windows       |            Architecture:  x86_64 (amd64)
 Type of failure:  None/Unknown  |               Test Case:
      Blocked By:                |                Blocking:
 Related Tickets:                |  Differential Revisions:
---------------------------------+-----------------------------------------

Comment (by snoyberg):

 > (To expand on the last point: If your terminal is not actually
 configured to interpret console output as UTF-8 then you will not be able
 to read the warnings if GHC insisted on outputting UTF-8. And if it is
 configured to do so then why is the code page not set to 65001?)

 The wonders of the Windows world still mystify me, so hopefully someone
 more informed can chime in. However, I was able to get both the standard
 Windows console and ConEmu to display non-ASCII characters (limited only
 by my font choice) by switching codepages.

--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/10762#comment:4>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler