Well I did originally have this in mind, but the more I looked into it the more I thought it needed someone with unicode experience.
It seems to me that the unicode world is full of "ah but in North Icelandic Yiddish aleph is considered to be an infinitely composite character" and other such arcane exceptions that make the inexperienced the natural victims of their own rational assumptions.
Yeah, understandable. I'm not looking for someone to understand Unicode, though, just ICU, at least well enough to make it build. I'm willing to trust that IBM knows more about Unicode (or at least knows fewer wrong things :) than we do and keep with their code.
Also, given the icu-not-building problem (http://www.mail-archive.com/[EMAIL PROTECTED]/msg17477.html) maybe what we need is an icu person per platform. This might have the benefit of making the task seem less onerous.
I did manage to get it building on OS X (still does, I just checked). I wonder on what systems is it actually failing?
It's failing on Linux, though it built fine on my OS X system. Odd, definitely odd.
I think I'll add it to the tinderboxen I wrangle to see what happens and whether it's a local problem or not.
On 15 Jan 2004, at 21:09, Dan Sugalski wrote:
Now, assuming there's still anyone left reading this message...
We've been threatening to build ICU into parrot, and it's time for that to start happening. Unfortunately there's a problem--it doesn't work right now. So, what we need is some brave soul to track ICU development and keep us reasonably up to date. What I'd really like is:
1) ICU building and working 2) ICU not needing any C++
I'd also like a pony, too, so I can live if we don't get #2, at least for a bit (as it means that we now require a C++ compiler to build parrot).
Anyone care to volunteer?
-- Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
