cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Francesco Chicchiriccò (JIRA) <>
Subject [jira] [Commented] (COCOON3-64) i18n support
Date Thu, 11 Aug 2011 15:27:27 GMT


Francesco Chicchiriccò commented on COCOON3-64:

I've just committed all the modifications involved with issue COCOON3-64: I've ported the
i18NTransformer in cocoon-sax (since no additional dependencies are involved), added some
unit tests and some sitemap samples in cocoon-sitemap.

Some remarks:

1. With respects to comments into COCOON3-64, I've NOT ported all the classes from the trunk,
but only the transformer: in particular, I thought - at least from the moment - not to consider
XML catalogs but to use instead standard JDK ResourceBundle, much like other frameworks -
namely Wicket - are doing.

2. This porting is for C3 only, even though I think it could be quit easily adaptable to C2.2
as well.

3. I've taken as reference for writing unit tests the old but still well written [1]: I think
we should enclose something similar in C3 documentation.

4. In C2.1 there used to be a "type" attribute, already deprecated in some situations like

<i18n:param type="date" pattern="dd-MMM-yy" />

C3 I18NTransformer does not consider such situations at all; the sample above becomes - like
it also used to be in C2.1

<i18n:param><i18n:date pattern="dd-MMM-yy" /></i18n:param>

5. I needed to port ParamSAXBuffer extending SAXBuffer (from cocoon-xml): for the moment I
put its source in cocoon-sax, but of course the right place would be in cocoon-xml, so how
could we handle this? Can I move that class to cocoon-xml's? In which SVN place? And how can
we release a SNAPSHOT version of this subproject?



> i18n support
> ------------
>                 Key: COCOON3-64
>                 URL:
>             Project: Cocoon 3
>          Issue Type: New Feature
>          Components: cocoon-pipeline, cocoon-sax, cocoon-servlet, cocoon-sitemap
>    Affects Versions: 3.0.0-alpha-3
>            Reporter: Francesco Chicchiriccò
>            Assignee: Francesco Chicchiriccò
> Cocoon 3 would take benefit from having a complete i18n support, possibly porting the
2.1 I18NTransformer.
> We would also need some sitemap, pipeline and servlet integration and, of course, an
overlook should also be considered towards the cocoon-wicket integration.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message