forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thorsten Scherler <>
Subject Re: Using dispatcher contracts with a not html output
Date Fri, 19 Sep 2008 23:34:26 GMT
On Fri, 2008-09-19 at 13:58 +0100, Pablo Barrera wrote:
> On 17/09/2008, at 15:11:56, Pablo Barrera wrote:
> > Hello
> >
> > I have developed an small contract to collect and show all links of  
> > a document.

the input is our internal xml format?

>  My idea is to create a new section on my documents  
> > called "References", so all links could be found in the same place.  
> > After some problems (thanks for the help) I have the system working  
> > smoothly for HTML output using the pelt-html.content.panel.xml  
> > structurer.

Good to hear. :)

> > However, I would like to obtain a TEI document with the same  
> > section. How could I use my contract with the tei output?

You want the link contract that you described above to be included in a
tei document? Is the above link html specific, or could you directly
reuse it?

> > I think I'm a little confuse with TEI being an output plugging and  
> > the way structurers for non-html output work.

Each format that supports the dispatcher needs to declare it. As I see 
there is *.html and *.fo but no *.tei. 

In org.apache.forrest.plugin.output.tei/output.xmap it is not declared
either. So you need to declare the dispatcher there as well.

> As I am having problems with this particular use of dispatcher

See above the dispatcher is not enabled there, but it is easy to do so.

>  I am  
> going to try to modify document-2-tei xsl to add the links at the end  
> of the document when using a tei output instead of a html output.

Please (if possible) implement the functionality in a seperate xsl that
you then include in the doc-2-tei. This way it will be easy to use it as
well in a tei contract if you decide to enable the dispatcher in tei.


> Regards,
> Pablo
> --
> Pablo Barrera
Thorsten Scherler                       
Open Source Java                      consulting, training and solutions

View raw message