forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Upayavira ...@upaya.co.uk>
Subject Re: i18n errors, bad downgrading
Date Mon, 15 Mar 2004 09:26:01 GMT
Juan Jose Pablos wrote:
...

>>
>> What I don't get is that if this scenario is so common (which I also 
>> believe), why isn't it already in place - I mean, Cocoon has it 
>> (_still_ needs to be tested, but they're at version 2.1.x, so any 
>> major problem here should have been discovered and rectified a long 
>> time ago), and as soon as you have that machinery in place, it should 
>> be a piece of cake after that. Or is there something fundamental in 
>> the relationship between Forrest and Cocoon that I don't get?
>
>
> You can check the code by yourself:
>
>       <map:match pattern="**.xml">
>         <map:select type="config">
>           <map:parameter name="value" value="{defaults:i18n}"/>
>           <map:when test="true">
>           <map:act type="locale">
>             <map:call resource="file-resolver">
>               <map:parameter name="uri" value="{../1}_{lang}"/>
>             </map:call>
>           </map:act>
>           </map:when>
>           <map:otherwise>
>             <map:call resource="file-resolver">
>               <map:parameter name="uri" value="{1}"/>
>             </map:call>
>           </map:otherwise>
>         </map:select>
>       </map:match>
>
> There is not a i18nfile generator, so it needs to be added on the 
> sitemap.

Hmmm. Seems like we could do with something here. If I've got a load of 
content files, how do I do a graceful downgrading? We could use a 
generator, although, with a suitable syntax, an input module may do it.

I'll ask on Cocoon-dev.

Upayavira




Mime
View raw message