On 20 Οκτ 2009, at 3:08 μ.μ., Simon Marlow wrote:
It's not to do with Haskeline. The real underlying problem is that
our filesystem APIs on Unix interpret FilePath as [Word8] without
doing any encoding/decoding; they just strip off all but the low 8
bits of each Char. This is a long-sta
On 18/10/2009 20:15, Chryssochoidis Christos wrote:
Thanks Don for your reply.
I may have overlooked something in the blog post you gave, but my
understanding is that it talks about the user's input/output to and from
GHCi and the file system. The user IO with non-Latin chars seems to work
fine i
Thanks Don for your reply.
I may have overlooked something in the blog post you gave, but my
understanding is that it talks about the user's input/output to and
from GHCi and the file system. The user IO with non-Latin chars seems
to work fine in GHC 6.12.1; e.g.:
*Main> putStrLn "πρόχει
christosc:
> I've noticed that when I load in GHCi a file that has a non-latin name,
> although it gets loaded, its name appears garbled in the message after
> the loading:
>
>> Prelude> :load πρόχειρον.hs
>> [1 of 1] Compiling Main ( ÏÏοÌÏειÏον.hs,
>> interpreted )
>> Ok,
I've noticed that when I load in GHCi a file that has a non-latin
name, although it gets loaded, its name appears garbled in the message
after the loading:
Prelude> :load πρόχειρον.hs
[1 of 1] Compiling Main ( ÏÏÎ
¿ÌÏειÏον.hs, interpreted )
Ok, modules loaded: Main.
*
