Re: ICU4D

On 25-Awi-2004, at 3:50 PM, [email protected] wrote:
>  See the readme (with the source) and userguide for some items on 
> organization and porting issues.
>  Yes, but those notes in the readme refer to porting the existing 
> project to a new platform. That's not what I'm talking about, so you 
> may have misunderstood. D is not a platform, it is a programming 
> language. I'm talking about creating a version of ICU with relevant 
> parts written in D, just as the Java version has relevant parts 
> written in Java. I'm talking about a language-port, not a 
> platform-port.

  I understand that, however a language-port has also to deal with the 
external dependencies of ICU (io, time zones, etc.) which is why I 
thought they might be helpful notes.

> hope this helps,  
>
> It doesn't help really, although I thank you for replying. You seem to 
> have answered as though I had asked "how do I write the code?" That 
> isn't quite what I meant - I can write code. I know how to make 
> wrappers, when they might be needed, and when they are inappropriate. 
> What I was trying to ask, is: How do I start a fork of ICU called 
> ICU4D, with the same status on the ICU web site as ICU4C or ICU4J? How 
> do we make this an "official" project? To whom do we have to talk? 
> etc.

Sorry, I think I misunderstood your "how do I go about 'this'?" as 
asking how best to add internationalization to D.   As far as the 
project goes, the ICU project leads can probably respond better here.

-s