cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Patrick Reuter <patrick.reu...@gmx.de>
Subject Re: FW: [ANNOUNCEMENT] FOP 0.20.3 Release Candidate available
Date Wed, 23 Jan 2002 13:51:12 GMT
hi john,

of course this could be useful :-)

BTW, renderx (a comercial xslfo render) have a similiar ;-) xslt 
stylesheet on their website with additional, renderx-spezific funtionality.

And it would be good to have a FAQ-Entry for this 'problem' on the FOP-Page.

regards,
patrick


Morrison, John wrote:

> Thanks, I used the xslt to fix the originals :)  Much faster than
> trying to find out what had actually changed.
> 
> The xslt ought to be part of the fop download for at least the
> (close) future don't you think?
> 
> J.
> 
> 
>>-----Original Message-----
>>From: Patrick Reuter [mailto:patrick.reuter@gmx.de]
>>Sent: Tuesday, 22 January 2002 1:52 pm
>>To: cocoon-dev@xml.apache.org
>>Subject: Re: FW: [ANNOUNCEMENT] FOP 0.20.3 Release Candidate available
>>
>>
>>
>>Hi,
>>
>>as an attachment I sent you an XSLT stylesheet that converts 
>>documents 
>>from the xslfo candidate recommendation to the proposed 
>>recommendation.
>>
>>You can use it as a second transformer in the pipeline.
>>
>>Patrick
>>
>>
>>
>>Morrison, John wrote:
>>
>>
>>>>From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de]
>>>>Sent: Tuesday, 22 January 2002 1:22 pm
>>>>To: cocoon-dev@xml.apache.org
>>>>Subject: RE: FW: [ANNOUNCEMENT] FOP 0.20.3 Release 
>>>>
>>Candidate available
>>
>>>>
>>>>
>>>>>Morrison, John wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>As I feared, it seems that the new fop has changed (I think 
>>>>>>this happens
>>>>>>with each fop release...).
>>>>>>I get the following exception with our two examples:
>>>>>>
>>>>>>java.lang.RuntimeException: org.apache.fop.apps.FOPException:
>>>>>>'master-reference'
>>>>>>for 'fo:page-sequence'matches no 'simple-page-master' or
>>>>>>'page-sequence-master'
>>>>>>
>>>>>>So, if someone is able to fix this, this would be great and 
>>>>>>we can update.
>>>>>>But if not, we shouldn't upgrade as this would break our 
>>>>>>
>>>>>>
>>>>fop examples.
>>>>
>>>>
>>>>>Ah, yes - that rings bells.  They caught up with the specification.
>>>>>We prob ought to upgrade and fix the examples.
>>>>>
>>>>>I'll see what I can do, unfortunately I'm in a meeting 
>>>>>
>>from 2 (GMT).
>>
>>>>>I *may* have time tomorrow...
>>>>>
>>>>>
>>>>>
>>>>That would be great!
>>>>
>>>>Don't hurry - unfortunately there are more than the fop 
>>>>examples which 
>>>>are currently not working...
>>>>
>>>>
>>>:( true - but the fo ones I can prob fix ;)
>>>
>>>I had a look at the svg ones but gave up in disgust...
>>>
>>>J.
>>>
>>>
>>>
>>>
>>==============================================================
>>=========
>>
>>>Information in this email and any attachments are 
>>>
>>confidential, and may
>>
>>>not be copied or used by anyone other than the addressee, 
>>>
>>nor disclosed
>>
>>>to any third party without our permission.  There is no intention to
>>>create any legally binding contract or other commitment 
>>>
>>through the use
>>
>>>of this email.
>>>
>>>Experian Limited (registration number 653331).  
>>>Registered office: Talbot House, Talbot Street, Nottingham NG1 5HF
>>>
>>>
>>>
>>---------------------------------------------------------------------
>>
>>>To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
>>>For additional commands, email: cocoon-dev-help@xml.apache.org
>>>
>>>
>>>
>>>
>>
>>
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
> 
> 
> 




---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message