cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Hunsberger" <peter.hunsber...@gmail.com>
Subject Re: [Proposal] i18n Transformer: Support Multiple Languages in One Document
Date Mon, 17 Apr 2006 16:34:58 GMT
On 4/17/06, Adrien Guillon <guila@dainty.ca> wrote:
> I know I can write an i18n Transformer in XSLT faster than I can modify the
> Java Code.  Is this how we want to go?
>
> I don't want to make something just for my applications, when I can contribute
> the solution to the community.  I feel we can make the change to an XSLT
> implementation of the transformer fairly transparent. Basically, just change
> the definition of the transformer in the sitemap... mark the existing Java
> Code as deprecated for the next release, and provide an alternative
> definition for the transformer in XSLT.  Alternatively we can take the
> existing Java class, and make it a wrapper for a new XSLT implementation as
> an upgrade pathway.
>
>   XSLT will be more extensible for site-specific configurations, and more
> maintainable than the existing Java code.
>

I don't see that you'd necessarily have to mark the existing
implementation deprecated.  Having the two different versions as
configurable options might make sense, in particular if there is much
of a performance difference.  Even if there is not, some people may
not feel that XSLT is "more maintainable" than the existing Java
code....

--
Peter Hunsberger

Mime
View raw message