#3307: System.IO and System.Directory functions not Unicode-aware under Unix
----------------------------------+-----------------------------------------
Reporter: YitzGale | Owner:
Type: bug | Status: new
Priority: normal | Milestone: 7.2.1
Component: libraries/base | Version: 6.11
Keywords: directory unicode | Testcase:
Blockedby: | Difficulty: Unknown
Os: Unknown/Multiple | Blocking:
Architecture: Unknown/Multiple | Failure: None/Unknown
----------------------------------+-----------------------------------------
Comment(by batterseapower):
Hmm, this is tricker than I thought. Python 3 still provides a way for the
dedicated programmer to support filenames that are not decodable in the
current locale by using "surrogate escapes" to tunnel undecodable bytes
through strings -- see PEP 383 (http://www.python.org/dev/peps/pep-0383/)
The implications of PEP 383 are far reaching and I'm not sure that I want
to implement it, but its existence has I think weakened the case for
decoding-by-default. This is a real shame because we so clearly *do* want
to decode any *text* entered on the command line by using the current
locale.
Anyway, my patch for #3309 to implement locale-decoding behaviour for the
CString FFI functions is still useful, even if we don't actually want to
use the *CString family for filename decoding. I'm validating it now.
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/3307#comment:13>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
_______________________________________________
Glasgow-haskell-bugs mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
