On 1/20/07, Gav.... <[EMAIL PROTECTED]> wrote:
Ok, so 11 days without a reply, I realise people are doing What interests them, but if anyone understands this please Let me in on it so I can continue and try and resolve The lack of images in pdfs issue.I will narrow my questions down a bit :- In resources.xmap we have <map:match pattern="images/**.*"> <map:select type="exists"> <map:when test="{lm:skin.images.{1}.{2}}"> <map:read src="{lm:skin.images.{1}.{2}}" mime-type="image/{2}" /> </map:when> <map:when test="{lm:project.images.{1}.svg}"> <map:call resource="pipe-aggregate-svg2png-resource"> <map:parameter name="path" value="{lm:project.images.{1}.svg}" /> </map:call> </map:when> <map:otherwise test="{lm:project.images.{1}.{2}}"> <map:read src="{lm:project.images.{1}.{2}}" mime-type="image/{2}" /> </map:otherwise> </map:select> </map:match> <map:match pattern="**images/**.*"> <map:select type="exists"> <map:when test="{lm:project.images.{1}.images/{2}.{3}}"> <map:read src="{lm:project.images.{1}.images/{2}.{3}}" mime-type="image/{3}" /> </map:when> <map:when test="{lm:project.images.{2}.{3}}"> <map:read src="{lm:project.images.{2}.{3}}" mime-type="image/{3}" /> </map:when> </map:select> </map:match> The first math pattern is simple enough. The second match pattern is a little more complicated. Questions. 1. - When a URL of /images/icon-a.png is called for as an example, it will Fall into this match. So where and how does forrest determine where /images/ Location actually is. We have possibility of a> in xdocs/images b> in resources/images/ c> in anotherLocation/images/ The when tests check in project.images which is defaulted to resources/images. If /images/icon-a.png is meant to be xdocs/images/icon-a.png where is this matched ??
take a look at the locationmap.xml file and look for the pattern "project.images.**.*" this is where they actually get resolved to a physical location. I don't know the rest of your questions without looking into it a bit to refresh myself and I haven't the time right now. --tim
