Thank you for your help. I am sure that you are right as to the cause of the
problem. However, I do not know what I should do to solve it. The Haskell
program is generated by LaTeX macros. It is useless to import System.IO.UTF8.
I did it. The system keeps producing the same error. What I need
On 2009-10-24 19:03 -0700 (Sat), Philippos Apolinarius wrote:
> However, I do not know what I should do to solve it.
I am not clear on exactly what your requirements are as far as character
encodings. But you need to understand character encodings if you're
going to be using non-ASCII ones. One s
Philippos Apolinarius writes:
> Thank you for your help. I am sure that you are right as to the cause
> of the problem. However, I do not know what I should do to solve
> it. The Haskell program is generated by LaTeX macros. It is useless
> to import System.IO.UTF8. I did it.
Are you sure? It
On Oct 25, 2009, at 5:01 PM, Curt Sampson wrote:
Actually, you would be having the exact same issues with Java; in
UTF-8
mode it would also choke on Latin-1.
Yes, but from the 'javac' man-page:
-encoding encoding
Setsthesourcefileencodingname,
su
On Oct 26, 2009, at 20:12 , Richard O'Keefe wrote:
On Oct 25, 2009, at 5:01 PM, Curt Sampson wrote:
The corresponding part of the GHC documentation says
GHC assumes that source files are ASCII or UTF-8 only,
other encodings are not recognised. However,
invalid UTF-8 sequ
> "Brandon" == Brandon S Allbery KF8NH writes:
Brandon> That would be the Haskell98 Report: Haskell uses the
Brandon> Unicode [11] character set. However, source programs are
Brandon> currently biased toward the ASCII character set used in
Brandon> earlier versions of Haskell
Colin Paul Adams writes:
> Brandon> So yes, it's reasonable to "blame" the language (spec).
On the other hand, the sooner users can get moving to utf-8, the sooner
we can get eliminate these kinds of problems.
> Note also that it mentions the Unicode character set, not a particular
> Unicod
Hello Ketil!
Tue, Oct 27, 2009 at 09:06:50AM +0100 you wrote:
> > At which point you probably want to make use of iconv, so you might as
> > well support all iconv-supported encodings.
>
> Interestingly, Wikipedia [0] says that "Unicode-aware programs are
> required to display, print and manipul
