[haskeline] #94: Use ghc-6.12's new Unicode I/O

[haskeline]

#94: Use ghc-6.12's new Unicode I/O
------------------+---------------------------------------------------------
Reporter:  judah  |        Owner:     
    Type:  task   |       Status:  new
Priority:  major  |    Milestone:     
 Version:  0.6    |   Resolution:     
Keywords:         |  
------------------+---------------------------------------------------------

Comment(by judah):

 Replying to [comment:2 guest]:
 > Replying to [comment:1 judah]:
 >
 > ghc-7.2.1 improved Unicode Support.
 http://www.haskell.org/ghc/docs/7.2.1/html/users_guide/release-7-2-1.html#id567292
 >
 > Okay, I know that some problems are left now.
 http://hackage.haskell.org/trac/ghc/wiki/Status/Encoding-Tickets But I
 want know what is current problem to switch GHC's unicode text I/O.
 >
 > >  - Full Windows codepage support
 >
 > Is ghc-7.2.1's problem just it? Or does ghc-7.2.1 have other prolems,
 too?

 On POSIX, from a quick glance it looks like we have everything necessary
 to switch over.  The tricky part will be making sure it still works on
 older versions (i.e., by choosing between the old or new code using CPP).

 On Windows, it's harder because you need to use the Win32 API to see
 console user events such as arrow keys.  That, plus the codepage issue,
 means I probably won't touch it for now.

 I'll update this ticket as I make progress on the issue.  (You can add
 yourself to the CC field to get emails when that happens)

 The full codepage support is a problem, but

-- 
Ticket URL: <http://trac.haskell.org/haskeline/ticket/94#comment:4>
haskeline <http://example.org/>
My example project