ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Magesh Umasankar" <umag...@apache.org>
Subject Re: Ant 1.5 Beta1 Sneak Preview ready
Date Thu, 02 May 2002 10:10:23 GMT
----- Original Message -----
From: "GOMEZ Henri" <hgomez@slib.fr>


> 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 <javac>).
  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...

> <a href="/welcome__LANG.html">
> <img src="/images/welcome__LANG.gif" align="left" border="0"
alt="__TRANS(welcome)
> __/></a></td>

Using T1, this would be like:

<a href="/welcome__#LANG#.html">
<img src="/images/welcome__#LANG#.gif" align="left" border="0"
alt="#welcome#/></a></td>

> will be translated in french (bienvenue chez nous) and could also
> adjust needed links (img, href...) :
>
> <a href="/welcome__fr.html">
> <img src="/images/welcome__fr.gif" align="left" border="0" alt="bienvenue
chez
> nous"/></a></td>

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:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>


Mime
View raw message