[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Monotone-devel] Re: Why is utf8 type _NOVERIFY, and other vocab stu
From: |
Nathaniel Smith |
Subject: |
Re: [Monotone-devel] Re: Why is utf8 type _NOVERIFY, and other vocab stuff. |
Date: |
Thu, 15 Feb 2007 11:25:40 -0800 |
User-agent: |
Mutt/1.5.13 (2006-08-11) |
On Thu, Feb 15, 2007 at 02:54:45PM +0100, Lapo Luchini wrote:
> Nathaniel Smith wrote:
> > (Also,
> > there were reports that the _best_effort code didn't actually work
> > with lots of broken iconv's found in the wild...)
>
> On Derek's super-laptop "UTF8 to ASCII//IGNORE//TRANSLIT" actually
> failed just like it was plain "UTF8 to ASCII". AFAIR it was a Gentoo.
>
> I'm willing to debug it further, if someone gives me access to a system
> in which I can verify the failure... or, even easier, I could create a
> smallish program that only has a fixes UTF8 string inside itself and ask
> on the command line for a charset and simply call the iconv function
> with those 2 parameters...
There must be a solution to this, I would think, it can't be that
every program everywhere just crashes all the time whenever funny
charset stuff happens... maybe this is overoptimistic of me :-).
But I can imagine it turning out we have to include our own non-borked
iconv for broken systems.
-- Nathaniel
--
"If you can explain how you do something, then you're very very bad at it."
-- John Hopfield
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: [Monotone-devel] Re: Why is utf8 type _NOVERIFY, and other vocab stuff.,
Nathaniel Smith <=