cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Rosenstrauch <dar...@dti.net>
Subject Re: AW: AW: Cocoon: Few steps in sitemap?
Date Fri, 16 Nov 2001 02:29:22 GMT
Actually, very sorry - I think I gave you the wrong advice here.  From the docs: "A serializer
is the end point of an xml pipeline. It transform SAX events in binary or char streams for
final client consumption."

So I think what I told you to do is wrong.  Having a stylesheet that outputs TEX doesn't help
you, since the serializer that runs after it to generate PDF is expecting XML input (SAX events).

Very sorry for the bad info.

So sounds like your options are:

1)
* Modify your XSL to write pseudo-TEX (i.e., TEX commands formatted as XML SAX events)
* Write a serializer that takes pseudo-TEX, and feeds it into the pdflatex utility (if this
is even possible) or generates PDF in some other way

2) Take TEX out of the picture and do the whole thing using XSL:FO

I'd still vote for option 2, if possible.

Particularly because I'm still not sure why TEX needs to be a part of the picture at all,
if your eventual goal is a PDF file.  Cocoon works with XML data flowing through the pipeline,
so putting TEX in the middle is really mucking things up.


DR


At 02:18 PM 11/15/01 +0100, you wrote:
>Hello, David!
>
>1) xsp and xsl that make tex file are already written.
>3)The problem is that I need a "self-written" serializer that makes from
>tex a pdf file.
>I have unfortunately no experience in writing serializers.
>Is that difficult? Are there any examples or source code of already
>existing serializers anywhere?
>
>We use tex as we generate tables, not text, and tex seems to be easier
>as fo in formatting, as tables concerns.
>
>What do you think about it?
>Thanks!
>Regards,
>Viktor
>
>
>
>-----Ursprüngliche Nachricht-----
>Von: David Rosenstrauch [mailto:darose@dti.net]
>Gesendet: Donnerstag, 15. November 2001 13:17
>An: cocoon-users@xml.apache.org
>Betreff: Re: AW: Cocoon: Few steps in sitemap?
>
>
>Not sure I understand the problem.  Why can't you do this?
>
>1) write an xsp that outputs in xml the info you need to build the tex
>doc
>2) write an xsl that outputs tex
>3) write a new serializer that generates pdf by calling pdflatex
>4) put the above 3 items in a pipeline and run them
>
>
>But why use tex?  Why not do this?
>
>1) write an xsp that outputs in xml the info you need to build the doc
>2) write an xsl that outputs xsl:fo
>3) call the existing serializer that generates pdf from xsl:fo
>4) put the above 3 items in a pipeline and run them
>
>
>DR
>
>
>
>At 10:44 AM 11/15/01 +0100, you wrote:
> >Luca,
> >
> >Sorry for disturbing you once again, but it isn't clear to me yet.
> >Could you please take a look at the steps I need to make?
> >
> >The GOAL: it must be shown (on mouseclick on the link "PDF") a PDF file
> >that should be generated as following: 
> >
> >1. I make a TEX(LATEX) document from XSP page that get all the data
>from
> >Oracle DB and a stylesheet that makes from these XSP a TEX document.
> >                         
> >2. To get a PDF file, these .TEX file must be now compiled with the
> >programm "pdflatex".
> >
> >PROBLEM: How can I tell Cocoon to execute these steps?
> >Is this generally possible?
> >
> >Thank you in advance for your help!
> >
> >Regards,
> >Viktor
> >
> >-----Ursprüngliche Nachricht-----
> >Von: Luca Morandini [mailto:l.moran@tin.it]
> >Gesendet: Donnerstag, 15. November 2001 09:56
> >An: Cocoon-users
> >Betreff: RE: Cocoon: Few steps in sitemap?
> >
> >
> >  Viktor,
> >
> >         the example reads a row from the dbms
> >  (select-resource-db.xml) and presents it as a read-only (say,
> >  display-resource.html) or editable (edit-resource.html) HTML.
> >         Of course, only the second <map:match> is invoked from the
> >  browser, the first one being an "internal" pipeline.
> >
> >         Apart from this, my idea was just to show you that
> >  pipelines may be chained, hence avoiding the need for storing
> >  intemediate files.
> >
> >  Best regards,
> >
> >  ---------------------------------------------
> >                 Luca Morandini
> >                 GIS Consultant
> >                lmorandini@ieee.org
> >  http://utenti.tripod.it/lmorandini/index.html
> >  ---------------------------------------------
> >
> > >
> > > > -----Original Message-----
> > > > From: Skladov, Victor [mailto:Skladov@his.de]
> > > > Sent: Thursday, November 15, 2001 9:42 AM
> > > > To: cocoon-users@xml.apache.org; lmorandini@ieee.org
> > > > Subject: AW: Cocoon: Few steps in sitemap?
> > > >
> > > >
> > > > Hello Luca!
> > > >
> > > > Thank you for your reply!
> > > > Could you please describe in few words what this example does?
> > > >
> > > > Regards,
> > > > Viktor
> > > >
> > > > -----Ursprüngliche Nachricht-----
> > > > Von: Luca Morandini [mailto:l.moran@tin.it]
> > > > Gesendet: Donnerstag, 15. November 2001 09:26
> > > > An: cocoon-users@xml.apache.org
> > > > Betreff: RE: Cocoon: Few steps in sitemap?
> > > >
> > > >
> > > > Viktor,
> > > >
> > > >     I think this example may fit the first of your questions:
> > > >
> > > > <map:pipeline>
> > > >     <map:match name="wildcard" pattern="select-resource-db.xml">
> > > >             <map:generate type="file"
> > > > src="docs/all-parameters.xml"/>
> > > >             <map:transform src="stylesheets/select-resource.xsl"/>
> > > >                     <map:transform type="sql">
> > > >                     <map:parameter name="use-connection"
> > > > value="noria-dev"/>
> > > >                     </map:transform>
> > > >                     <map:serialize type="xml"/>
> > > >     </map:match>
> > > >
> > > >     <map:match name="wildcard" pattern="*-resource.html">
> > > >             <map:aggregate element="page">
> > > >             <map:part src="docs/all-parameters.xml"/>
> > > >                     <map:part src="docs/form-resource.xml"/>
> > > >                     <map:part
>src="cocoon:/select-resource-db.xml"/>
> > > >             </map:aggregate>
> > > >                     <map:transform
> > > src="stylesheets/resource-{1}-html.xsl"/>
> > > >                     <map:serialize type="html"/>
> > > >     </map:match>
> > > > </map:pipeline>
> > > >
> > > >     As you may notice the second <map:match> (the one actually
>being
> > > > invoked
> > > > from the browser), calls the first one using <map:part
> > > > src="cocoon:/select-resource-db.xml"/> .
> > > >
> > > >     The first <map:match> may be called from another <map:match>
> > > > used to
> > > > deliver PDF instead of HTML, hence avoiding the need for the
>storage
> >of
> > > > intermediate files.
> > > >
> > > >     I use this for more complicated pipelines than the usual
> > > > XML->XSL->HTML
> > > > stuff.
> > > >
> > > >     I hope this helps,
> > > >
> > > > ---------------------------------------------
> > > >                Luca Morandini
> > > >                GIS Consultant
> > > >               lmorandini@ieee.org
> > > > http://utenti.tripod.it/lmorandini/index.html
> > > > ---------------------------------------------
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: Skladov, Victor [mailto:Skladov@his.de]
> > > > > Sent: Thursday, November 15, 2001 9:08 AM
> > > > > To: cocoon-users@xml.apache.org
> > > > > Subject: Cocoon: Few steps in sitemap?
> > > > >
> > > > >
> > > > > Hello!
> > > > >
> > > > > I am writing  to you all once more, because I can't find a
> >solution up
> > > > > to now.
> > > > > Does anybody know how can I tell Cocoon2 to execute not one step
> > > > > (XSP+XSL->and output in a format that Cocoon accept, for example
> > > > HTML),
> > > > > but a few steps:
> > > > > 1)generate from XSP with XSL a further file, say, TEX (it
>doesn't
> > > > > matter!)
> > > > > 2) generate from that file (TEX in our case) a further format,
>for
> > > > > example PDF?
> > > > >
> > > > > OR:
> > > > > Can Cocoon2 save output file? Can I force Cocoon execute my
>LINUX
> > > > script
> > > > > that lies on the server?
> > > > >
> > > > > I would be very grateful for any ideas!
> > > > >
> > > > > Regards,
> > > > > Viktor
> > > > >
> > > > >
> >---------------------------------------------------------------------
> > > > > Please check that your question has not already been answered in
> >the
> > > > > FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
> > > > >
> > > > > To unsubscribe, e-mail:
><cocoon-users-unsubscribe@xml.apache.org>
> > > > > For additional commands, e-mail:
> ><cocoon-users-help@xml.apache.org>
> > > > >
> > > >
> > > >
> > > >
> >---------------------------------------------------------------------
> > > > Please check that your question has not already been answered in
>the
> > > > FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
> > > >
> > > > To unsubscribe, e-mail: <cocoon-users-unsubscribe@xml.apache.org>
> > > > For additional commands, e-mail:
><cocoon-users-help@xml.apache.org>
> >
> >
> >---------------------------------------------------------------------
> >Please check that your question has not already been answered in the
> >FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
> >
> >To unsubscribe, e-mail: <cocoon-users-unsubscribe@xml.apache.org>
> >For additional commands, e-mail: <cocoon-users-help@xml.apache.org>
> >
> >---------------------------------------------------------------------
> >Please check that your question has not already been answered in the
> >FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
> >
> >To unsubscribe, e-mail: <cocoon-users-unsubscribe@xml.apache.org>
> >For additional commands, e-mail: <cocoon-users-help@xml.apache.org> 
>
>
>---------------------------------------------------------------------
>Please check that your question has not already been answered in the
>FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
>
>To unsubscribe, e-mail: <cocoon-users-unsubscribe@xml.apache.org>
>For additional commands, e-mail: <cocoon-users-help@xml.apache.org>
>
>---------------------------------------------------------------------
>Please check that your question has not already been answered in the
>FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
>
>To unsubscribe, e-mail: <cocoon-users-unsubscribe@xml.apache.org>
>For additional commands, e-mail: <cocoon-users-help@xml.apache.org> 


---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

To unsubscribe, e-mail: <cocoon-users-unsubscribe@xml.apache.org>
For additional commands, e-mail: <cocoon-users-help@xml.apache.org>


Mime
View raw message