Ok, ant 1.6 ;) - Henri Gomez ___[_]____ EMAIL : [EMAIL PROTECTED] (. .) PGP KEY : 697ECEDD ...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6
>-----Original Message----- >From: Erik Hatcher [mailto:[EMAIL PROTECTED] >Sent: Thursday, May 02, 2002 1:32 PM >To: Ant Developers List >Subject: Re: Ant 1.5 Beta1 Sneak Preview ready > > >You mean Ant 1.6 alpha! > >No new features in 1.5. > > Erik > > >----- Original Message ----- >From: "GOMEZ Henri" <[EMAIL PROTECTED]> >To: "Ant Developers List" <[EMAIL PROTECTED]> >Sent: Thursday, May 02, 2002 7:09 AM >Subject: RE: Ant 1.5 Beta1 Sneak Preview ready > > >I'll start to work on it for ant 1.5 beta 2 ;) > >BTW, I may ask you more about encoding, I'm just >a plain Latin boy ;) > >- >Henri Gomez ___[_]____ >EMAIL : [EMAIL PROTECTED] (. .) >PGP KEY : 697ECEDD ...oOOo..(_)..oOOo... >PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 > > > >>-----Original Message----- >>From: Magesh Umasankar [mailto:[EMAIL PROTECTED] >>Sent: Thursday, May 02, 2002 1:06 PM >>To: Ant Developers List >>Subject: Re: Ant 1.5 Beta1 Sneak Preview ready >> >> >>----- Original Message ----- >>From: "GOMEZ Henri" <[EMAIL PROTECTED]> >> >> >>> >* T1 fully supports encoding; T2 doesn't seem to be >>> > supporting encoding in its curent form. >>> >>> Hum, need to learn more, may be after reading your own >>> source. >> >>Especially Japanese (Shift-JIS) stuff... >> >>> >* T1 supports configurable start and end tokens (though, >>> > IIRC, it can be just one character each). T2's >>> > token parsing, AFAICS, is not configurable. >>> >>> ok, I'll add this two tokens quickly ;) >> >>As I said, I was merely trying to find the similarities >>and differences - not trying to prod you into work on >>it right away ;-) >> >>> >* T1 uses multiple hierarchial Resource Bundles; T2 uses >>> > a single xml file - I can see merits in both approach. >>> >>> T2 could use a set of xml files, not just one. >>> There is a not so hidden concept of domain, with a >>> root domain. >>> Each xml file concern a domain of translation and >>> you could search in this domain by tagging like >>> this __TRANS([EMAIL PROTECTED])__. >>> >>> Fallback will be in root domain (should add more configure >>> option here) >> >>Cool. >> >>> T2 have the same feature, since it extend MatchingTask >>> and use restric : >> >>Aah! I missed that, didn't I... >> >>> That's why one my idea, having Translate just an interface. >>> XMLTranslate could be an implementation, ditto for ResourceBundles, >>> and why not a JDBC implementation ? >> >>+1 to all 4. Willing to take it on? ;-) >> >>> >xtranslate does look good - but, IMHO, if you can >>> >integrate both these tasks into one, if feasible, >>> >that would be the best step forward. Let me know >>> >what you think. >>> >>> Let's go. I'll try to get translate and translator a >>> uniq task, with your benediction ;) >> >>I say, go for it! I can see the value addition you >>are trying to provide to this task. >> >>Cheers, >>Magesh >> >>**************************************************** >>* Doctor: A person who kills your ills by pills, * >>* and then kills you with his bills. * >>**************************************************** >> >> >> >> >>-- >>To unsubscribe, e-mail: ><mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
