forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ross Gardler <>
Subject Re: question about changes in forrest.xmap
Date Mon, 26 Mar 2007 21:42:00 GMT
Ferdinand Soethe wrote:
> I just noticed that there are quite a few changes in forrest.xmap that
> require changes to
> "How to customize processing of html source"
> Is it correct to say that (forrest.xmap line 216)
>> <map:match type="wildcard" pattern="**.xml">
>>        <map:select type="exists">
>>          <map:when test="{lm:plugin.xmap.input}">
>>              <map:mount uri-prefix=""
>>                         src="{lm:plugin.xmap.input}"
>>                         check-reload="yes"
>>                         pass-through="true"/>
>>          </map:when>
>>        </map:select>
> will kick in when content is provided through a plugin and the next matcher

Yes. The input plugin sitemaps are processed first, if nothing matches 
in those then it falls through to the pipelines after the one quoted above.

>> <map:match type="i18n" pattern="{properties:content.xdocs}{1}.*.xml">


> is the new file resolver that combines i18N capabilities with a cascade
> through the different supported formats?


> Side issue. What is the effect of i18n being used here in the matcher?

All is explained in [1]



View raw message