Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 21344 invoked from network); 2 May 2002 10:10:23 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 2 May 2002 10:10:23 -0000 Received: (qmail 24995 invoked by uid 97); 2 May 2002 10:10:35 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@nagoya.betaversion.org Received: (qmail 24908 invoked by alias); 2 May 2002 10:10:35 -0000 Delivered-To: jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 24893 invoked by uid 97); 2 May 2002 10:10:34 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 24872 invoked by uid 98); 2 May 2002 10:10:34 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Message-ID: <00aa01c1f1c1$953f99c0$7fc8a8c0@manu.com> From: "Magesh Umasankar" To: "Ant Developers List" References: Subject: Re: Ant 1.5 Beta1 Sneak Preview ready Date: Thu, 2 May 2002 06:10:23 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Spam-Rating: localhost.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N ----- Original Message ----- From: "GOMEZ Henri" > Did someone take a look at my Translator Task. Sorry, but I haven't had a chance yet to take a detailed look. > It's similar to the translate task from Magesh, but > I candidly think it's a little better to translate > webapps, since it could translate TOKEN searching > in the xml dicts files and also add current lang Here is what I have observed from my short glance - correct me if I am wrong: (T1->my task; T2->your task) * The configuration file of T2 is XML based, while T1 is ResourceBundle (property file) based. * T1 fully supports encoding; T2 doesn't seem to be supporting encoding in its curent form. * T1 supports configurable start and end tokens (though, IIRC, it can be just one character each). T2's token parsing, AFAICS, is not configurable. * T1 uses multiple hierarchial Resource Bundles; T2 uses a single xml file - I can see merits in both approach. * T1 supports translation of just those files that need to be updated (based on timestamps, like ). In its current state, T2 doesn't seem to. There may be other minor differences as well - I don't yet know. But let me ask this: Since the only significant difference really seems to be the way the translation text is submitted, would it be possible for you to refactor both these tasks so that we end up with one single task that can be configured using XML files or Resource Bundles, retaining the values provided by both these tasks? If it doesn't seem feasible, then, perhaps we can provide your task too, as an alternative... > >

__TRANS(welcome)
> __/></a></td>

Using T1, this would be like:

<a href=

#welcome#/></a></td>

> will be translated in french (bienvenue chez nous) and could also
> adjust needed links (img, href...) :
>
> <a href=

T1's result will be the same, of course. > if translator name seems incorrect, we could rename it to xtranslate > (xml based translate) .... 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. > Henri Gomez Cheers, Magesh **************************************************** * Doctor: A person who kills your ills by pills, * * and then kills you with his bills. * **************************************************** -- To unsubscribe, e-mail: For additional commands, e-mail: