forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ross Gardler <>
Subject Re: How to avoid hard-coding site-visible message strings in skin files
Date Thu, 02 Jun 2005 17:09:34 GMT
Thorsten Scherler wrote:
> On Thu, 2005-06-02 at 10:34 +0100, Ross Gardler wrote:
>>Pedro I. Sanchez wrote:
>>>A few days ago I added issue FOR-506 on this topic. This is my original
>>>  "Text strings like "Copyright", "Published", and "Search" are
>>>   hardcoded into skin files like site2xhtml.xsl. When creating web
>>>   sites in languages other than English the web developer is forced
>>>   to create local versions of these skin files with the appropriated
>>>   translations.
>>>   Instead, the DTD for the skinconf.xml should be improved to allow
>>>   these translations to be specified in this file. This would make
>>>   Forrest much easier to use."


> Actually I did not do it like you or Pedro suggested but the "cocoon"
> way with a simple i18n transformer in the contracts. That means we have
> a 
> <map:transformer name="xinclude"
>         src="org.apache.cocoon.transformation.XIncludeTransformer"/>
>       <map:transformer name="i18n"
> src="org.apache.cocoon.transformation.I18nTransformer">
> 	      <catalogues default="contracts">
> 	        <catalogue id="other" name="OtherMessages"
> location="messages"/>
> 	        <catalogue id="contracts" name="ContractsMessages"
> location="messages"/>
> 	      </catalogues>
> 	      <cache-at-startup>true</cache-at-startup>
> 	    </map:transformer>
> in the output.xmap of the viewHelper.xhmtl and nothing in the
> skinconf.xml.
> IMO that would be as well the way to implement it for the "old fashion"
> skins but I do not know how this affect the cli.

+1 especially if this is the official Cocoon way of doing things, there 
are some docs at

Pedro, if you need pointers as to where in the sitemap this stuff would 
go for skins we can help out.


View raw message