forrest-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Williams <william...@gmail.com>
Subject Re: relative links in site.xml
Date Thu, 01 Jul 2010 10:50:12 GMT
On Wed, Jun 30, 2010 at 8:36 AM, Wipf Markus <markus.wipf@axa-tech.com> wrote:
> Hi,
>
>
>
> Can anybody help me please to fix this problem.
>
> I'm trying to make the things more flexible by using relative links to
> external sites in site.xml:
>
>                 <external-refs>
>
>                                <eplatformIntra href="../">
>
>                                               
<workshop>
>
>                                                               
<as
> href="services/training/workshops/as/as_knowhow.pdf"/>
>
>                                               
</workshop>
>
>                                </eplatformIntra>
>
> The reference to it looks like:
>
> <a href="ext:as">as_knowhow.pdf</a>
>
>
>
> Running the site ant-task I get the following error:
>
>      [java] * [40/9]    [3/31]    0.728s 37.8Kb  kt/training.html
>
>      [java] * [41/8]    [0/0]     1.64s  52.3Kb  kt/training.pdf
>
>      [java] X [0]
> ../services/training/workshops/as/as_knowhow.pdf BROKEN: No flow in
> page-sequence
>
>
>
> The linkmap.xmap file defines for the 'linkmap' pipeline:  A linkmap is a
> map from abstract ('site:index') to
>
> physical ('../index.html') links for the current page.
>
>
>
> The compilation to html works fine, because the pipeline assumes another
> ../, which points exactly to the right place. But the pdf pipeline doesn't
> behave the same way. I don't understand this behavior.
>
> Is there any solution? Best regards. Markus

Hi Markus,
Is it really an *external* reference?  I haven't looked at this in a
while, but I can't recall seeing an example like yours where it's a
local (e.g. "../") and not building up on some full base url.
Hopefully someone else comes along soon, what version of forrest are
you using?  I'm not familiar with that particular fop error either
unfortunately.

--tim

Mime
View raw message