On 27 September 2011 12:27, Daniel Fischer
wrote:
> So the only opportunity for iconv to have a part in this would be during
> git cloning, wouldn't it? Does git use iconv when cloning?
Sorry I should have said libiconv. GHC's base library links against
libiconv to implement encoding/decoding for
On Tuesday 27 September 2011, 08:35:26, Max Bolingbroke wrote:
> On 26 September 2011 23:30, Daniel Fischer
>
> wrote:
> > In hex, the error sequences are
> > common: EF BF BD
> > expected: C8
> > actual: ED B3 88
>
> It looks like your iconv has erroneously UTF-8 encoded the lone
> surrogate co
On 26 September 2011 23:30, Daniel Fischer
wrote:
> In hex, the error sequences are
> common: EF BF BD
> expected: C8
> actual: ED B3 88
It looks like your iconv has erroneously UTF-8 encoded the lone
surrogate codepoint 0xDCC8 to UTF-8. This is in violation of the
recommendations of the UTF stan
On 27 September 2011 02:50, Ian Lynagh wrote:
> It's passing here too now.
Thanks. I made this change to get it to compile on Windows, because
GHC only recognises the UTF-8 encoding, not UTF8. It still worked on
OS X since the code fell through to iconv, which did understand UTF-8.
Thus, the pro
On Mon, Sep 26, 2011 at 05:59:39PM +0200, Daniel Fischer wrote:
> On Monday 26 September 2011, 15:35:26, Max Bolingbroke wrote:
> > On 24 September 2011 14:30, Daniel Fischer
> >
> > wrote:
> > > The test fails for me, too. My locale is de_DE.UTF-8.
> > > I get the same hex as Ian posted, I haven
On Monday 26 September 2011, 15:35:26, Max Bolingbroke wrote:
> On 24 September 2011 14:30, Daniel Fischer
>
> wrote:
> > The test fails for me, too. My locale is de_DE.UTF-8.
> > I get the same hex as Ian posted, I haven't yet built with the Attempt
> > to fix patch.
>
> Have you tried with thi
On Monday 26 September 2011, 15:35:26, Max Bolingbroke wrote:
> On 24 September 2011 14:30, Daniel Fischer
>
> wrote:
> > The test fails for me, too. My locale is de_DE.UTF-8.
> > I get the same hex as Ian posted, I haven't yet built with the Attempt
> > to fix patch.
>
> Have you tried with thi
On 24 September 2011 14:30, Daniel Fischer
wrote:
> The test fails for me, too. My locale is de_DE.UTF-8.
> I get the same hex as Ian posted, I haven't yet built with the Attempt to
> fix patch.
Have you tried with this patch yet?
I can't reproduce this problem either on my other Mac OS X machin
On Saturday 24 September 2011, 15:04:40, Ian Lynagh wrote:
> Hi Max,
>
> On Sat, Sep 24, 2011 at 09:56:00PM +0900, Max Bolingbroke wrote:
> > It almost certainly was caused by that patch, but the test works OK
> > for me!
>
> Hmm, interesting.
>
> > I think I can see what causes this: the output
Hi Max,
On Sat, Sep 24, 2011 at 09:56:00PM +0900, Max Bolingbroke wrote:
>
> It almost certainly was caused by that patch, but the test works OK for me!
Hmm, interesting.
> I think I can see what causes this: the output of this new test
> depends on the locale of the machine. My locale is en_G
Hi Ian,
It almost certainly was caused by that patch, but the test works OK for me!
I think I can see what causes this: the output of this new test
depends on the locale of the machine. My locale is en_GB.UTF-8 and and
trying to write a surrogate byte to stdout in this encoding fails with
an exce
Hi Max,
I'm seeing a test failure when validating:
Actual stdout output differs from expected:
--- ./lib/IO/decodingerror002.stdout2011-09-24 12:36:55.0 +0100
+++ ./lib/IO/decodingerror002.run.stdout2011-09-24 13:43:09.0
+0100
@@ -1,4 +1,4 @@
Left decodingerror002.i
12 matches
Mail list logo
