forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ross Gardler <>
Subject Re: i18n message catalogue in dispatcher and skins
Date Wed, 10 Sep 2008 12:12:17 GMT
Sjur Moshagen wrote:
> Hello all,
> I'm starting on the next step to make the pdf plugin fully i18n - 
> support for i18n text.
> To that extent I have a couple of questions:
> 1.
> In $FORREST_HOME/main/webapp/sitemap.xmap, the following lines are found:
>       <map:transformer name="i18n" 
> src="org.apache.cocoon.transformation.I18nTransformer">
>         <catalogues default="common">
>           <catalogue id="common" name="CommonMessages" 
> location="{properties:skins-dir}common/translations"/>
>         </catalogues>
>         <cache-at-startup>true</cache-at-startup>
>       </map:transformer>
> Why is the path to the message catalogue "soft-coded" to the project 
> instead of using a LM?

Quite possibly missed when I did the move to LM. I probably did a search 
for 'src="' which would have missed this.

I certainly didn't intentionally leave it out.

[I'll have to pass on questions 2 and 3]

> Basic point for all these questions:
> now we have copies of the same info all over the place, and most is not 
> used - I would like to remove all the unnecessary ones, and use LM in 
> all cases - and remove the messages from the seed. As part of that I 
> would like to update the user documentation for i18n as well, to make 
> sure it reflects the current state and how to set up proper i18n 
> support, as well as how to add new languages to the translation catalogue.

Yes please!


View raw message