All:
After speaking with Dan in #parrot last night, I
either had originally misunderstood his position or he
has changed it (paraphrased):
We will ship Parrot with unicode support, but:.
A. The unicode support does not necessarily need to
be limited to a single library or ICU specifically.
B. Just because CVS will have unicode support, does
not mean the user will be forced to use it.
C. Configure should detect a system unicode library
and do the right thing in choosing which one it uses.
So, we really need to decide what we want to do about
unicode support. We are stuck with ICU unless someone
steps up to the plate to implement an alternative. If
we implement an alternative, I don't necessarily feel
we should drop ICU support. It just means that the
unicode support in CVS would not be ICU. Configure
would notice supported system unicode libraries and do
the right thing.
Providing an alternative to ICU may:
1. Eliminate the need for C++
2. Reduce the size of CVS
3. Make building on most platforms easier
WRT improving the ease of use of ICU. My suggestion
is that a representative from each platform that
Parrot is currently being built on download the latest
stable version of ICU source, build it, and note
anything "special" they needed to do to get it
working. Those things should make putting a newer
version into CVS a realistic possibility. I am
volunteering for Cygwin (yeah I know - big surprise
there).
Cheers
Joshua Gatcomb
a.k.a. Limbic~Region
__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail
