Re: master-reference '' for fo:page-sequence matches no simple-page-master or page-sequence-master
Quite happy to. Done. Glen --- Simon Pepping [EMAIL PROTECTED] wrote: Glen, On Wed, Mar 09, 2005 at 11:34:29AM -0800, Glen Mazza wrote: The property on fo:conditional-page-master-reference should be master-reference, not master-name [1]. I had this problem too the other day. Can you not throw some validation towards detecting a missing master-reference attribute? The idea that FOP goes searching for an empty master-reference name is not quite satisfactory. Regards, Simon -- Simon Pepping home page: http://www.leverkruid.nl
DO NOT REPLY [Bug 31224] New: - Need embedded page sequence functionality
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=31224. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=31224 Need embedded page sequence functionality Summary: Need embedded page sequence functionality Product: Fop Version: 0.20.4 Platform: PC OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: page-master/layout AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Is there a way to generate page subsequences for the purpose of pagination in XSL-FO. For example, generate an XSL-FO output with embedded sections that contain their own page number sequences. In other words, we like to generate local (in contrast to global, container or parent) page numbers using an embedded page sequence (assuming that there is such a thing). Example -- Main Doc (Page 1 of 1000) Section 1 (Page 1 of 3) Section 1 (Page 2 of 3) Main Doc (Page 2 of 1000) Section 1 (Page 3 of 3) Section 2 (Page 1 of 2) Main Doc (Page 3 of 1000) Section 2 (Page 2 of 2) Thanks, Peter
DO NOT REPLY [Bug 31225] New: - Need embedded page sequence functionality
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=31225. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=31225 Need embedded page sequence functionality Summary: Need embedded page sequence functionality Product: Fop Version: 0.20.4 Platform: PC OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: page-master/layout AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Is there a way to generate page subsequences for the purpose of pagination in XSL-FO. For example, generate an XSL-FO output with embedded sections that contain their own page number sequences. In other words, we like to generate local (in contrast to global, container or parent) page numbers using an embedded page sequence (assuming that there is such a thing). Example -- Main Doc (Page 1 of 1000) Section 1 (Page 1 of 3) Section 1 (Page 2 of 3) Main Doc (Page 2 of 1000) Section 1 (Page 3 of 3) Section 2 (Page 1 of 2) Main Doc (Page 3 of 1000) Section 2 (Page 2 of 2) Thanks, Peter
DO NOT REPLY [Bug 31225] - Need embedded page sequence functionality
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=31225. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=31225 Need embedded page sequence functionality --- Additional Comments From [EMAIL PROTECTED] 2004-09-14 18:24 --- oops!...example is slightly off. Should be: Example -- Main Doc (Page 1 of 1000) Section 1 (Page 1 of 3) Section 1 (Page 2 of 3) Main Doc (Page 3 of 1000) Section 1 (Page 3 of 3) Section 2 (Page 1 of 2) Main Doc (Page 4 of 1000) Section 2 (Page 2 of 2)
DO NOT REPLY [Bug 28556] New: - fox:outline generates PDF bookmark sets for each page-sequence
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=28556. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=28556 fox:outline generates PDF bookmark sets for each page-sequence Summary: fox:outline generates PDF bookmark sets for each page- sequence Product: Fop Version: 1.0dev Platform: PC OS/Version: Windows XP Status: NEW Severity: Normal Priority: Other Component: pdf renderer AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] If I use the outline extension to generate PDF bookmarks it generates a complete set of bookmarks for each page-sequence I have. In other words, if I have this input: ?xml version=1.0 encoding=UTF-8 ? fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set fo:simple-page-master master-name=simple page- height=29.7cm page-width=21cm margin-top=1cm margin-bottom=2cm margin-left=2.5cm margin-right=2.5cm fo:region-body margin-top=3cm / fo:region-before extent=3cm / fo:region-after extent=1.5cm / /fo:simple-page-master /fo:layout-master-set fox:bookmarks xmlns:fox=http://xml.apache.org/fop/extensions; fox:outline internal-destination=sec1 fox:labelSection 1/fox:label /fox:outline fox:outline internal-destination=sec2 fox:labelSection 2/fox:label /fox:outline /fox:bookmarks fo:page-sequence master-reference=simple fo:flow flow-name=xsl-region-body font-size=10pt font- family=Helvetica fo:block id=sec1Section 1/fo:block /fo:flow /fo:page-sequence fo:page-sequence master-reference=simple fo:flow flow-name=xsl-region-body font-size=10pt font- family=Helvetica fo:block id=sec2Section 2/fo:block /fo:flow /fo:page-sequence /fo:root I expect to get one set of bookmarks with items of Section 1 and Section 2 linking to the first page and second page respectively. Instead I get two complete sets, i.e., items Section 1, Section 2, Section 1 and Section 2. The bookmarks link to the right places. This only seems to happen if there are outline references to more than one page-sequence.
Re: multi page-sequence don't work for (XML+XSL) to PDF on the fly
Hi,
Can't you use multiple page-sequences instead of just creating one sequence
'interrupted' by the 'ctrlPage' template?
but How?
this template is more difficult since it is used in with a more
complicated XML like groupproduct/.../group..., the way that I
sent is for brevety to discover because ctrlPage don't work, for groups
I need print a header, followed by products, etc..., in original XSL i
use xalan extensions to count how many lines I used PDF.
A few remarks to help you on your way:
1. I can't seem to find the reason why you are placing the whole
fo:static-content into a separate template, since it is ... well, static
and it doesn't rely on the elements in the XML (unless something is
missing).
because, I reduced the code for brevety, then the static-content is for
groups case. sorry
2. In the ctrlPage template, you are testing for a position(): you could
also use XPath to select these, like
xsl:apply-templates select=product[(position() mod 3) = 0]
Then inside the product template, use
xsl:for-each select=preceding::product[position() 3] /
to grab the two preceding product nodes.
but for-each select don't put Xalan in DOM process? consumes more
memory? however I can't use position because the original XML is more
complex. (I use xalan extensions to control this). like this xsl:if
test=counter:read('ctLine') mod 3/xsl:if
3. Check our http://xml.apache.org/fop/resources.html page, among the books
and articles, there's a link to Dave Pawson's XSLT FAQ. Over there, you'll
find a lot of useful stuff (amongst others on grouping which I think you'll
find particularly helpful), so I'll bet you can work out a redesign which
affects only the XSL itself and leaves the other files alone.
If you really can't get any further, try posting your problem on Mulberry's
XSLT list. Warning: it's a quite high-traffic list, but the upside is that
the tips are 'highly-usable' ;)
Hope this helps!
Cheers,
Andreas
Thanks for tips
Clovis
multi page-sequence don't work for (XML+XSL) to PDF on the fly
Hi FOP DevTeam, I developed a way to generate multiple page-sequence on XSL without to change my XML, but the XML-XSL-PDF don't work, to make this work, first I need to generate the .fo file, then transform this to PDF. if run: fop.sh -xml sample.xml -xsl multiplePageSequence.xsl -pdf sample.pdf I get follow output: [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [INFO] FOP 0.20.5 [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [INFO] building formatting object tree [INFO] setting up fonts [ERROR] org.apache.fop.apps.FOPException: flow must be child of page-sequence, not fo:flow but if I first generate the .fo file with: xalan.sh -IN sample.xml -XSL multiplePageSequence.xsl -OUT sample.fo then generate the .pdf file from .fo file with: fop.sh -fo sample.fo -pdf sample.pdf I get the follow output: [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [INFO] FOP 0.20.5 [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [INFO] building formatting object tree [INFO] setting up fonts [INFO] [1] [INFO] [2] [INFO] [3] [INFO] [4] [INFO] Parsing of document complete, stopping renderer The part of XSL that cause on the fly transformation to catch the ERROR is: xsl:template name=ctrlPage xsl:if test=(position() mod 3) = 0 xsl:text disable-output-escaping=yes![CDATA[/fo:flow/fo:page-sequencefo:page-sequence master-reference=A4 language=pt country=br]]/xsl:text xsl:call-template name=header/ xsl:text disable-output-escaping=yes![CDATA[fo:flow flow-name=xsl-region-body]]/xsl:text /xsl:if /xsl:template to close and open fo:flow and fo:page-sequence for xsl:template match=data fo:page-sequence master-reference=A4 language=pt country=br xsl:call-template name=header/ fo:flow flow-name=xsl-region-body xsl:apply-templates / /fo:flow /fo:page-sequence /xsl:template I can't understand because on the fly don't woks and from .fo file generated from xml+xsl transformation work, maybe a bug of FOP, or I can't generate XML elements using CDATA from this form. I post this in dev list because I think that this is a feature or a bug on FOP then I attached the XSL and XML files that the team can test this issue, and the code is better to read than my bad English ;) Thanks for any help or tip Clovis ?xml version=1.0 encoding=ISO-8859-1? xsl:stylesheet version=1.0 xmlns:fo=http://www.w3.org/1999/XSL/Format; xmlns:xsl=http://www.w3.org/1999/XSL/Transform; xsl:output method=xml/ xsl:template match=/ fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set fo:simple-page-master master-name=A4 page-width=297mm page-height=210mm margin-top=5mm margin-bottom=5mm margin-left=3mm margin-right=5mm fo:region-before extent=20.8mm/ fo:region-body margin-top=21.8mm margin-bottom=0in/ fo:region-after extent=0in/ fo:region-start extent=0in margin-top=0mm margin-bottom=0mm margin-left=0mm margin-right=0mm/ fo:region-end extent=0in margin-top=0mm margin-bottom=0mm margin-left=0mm margin-right=0mm/ /fo:simple-page-master /fo:layout-master-set xsl:apply-templates / /fo:root /xsl:template xsl:template match=info/xsl:template xsl:template match=data fo:page-sequence master-reference=A4 language=pt country=br xsl:call-template name=header/ fo:flow flow-name=xsl-region-body xsl:apply-templates / /fo:flow /fo:page-sequence /xsl:template xsl:template match=product xsl:call-template name=detail / /xsl:template !-- Header For Pages -- xsl:template name=header fo:static-content flow-name=xsl-region-before fo:table table-layout=fixed fo:table-column column-width=40mm/ fo:table-column column-width=40mm/ fo:table-column column-width=40mm/ fo:table-body fo:table-row fo:table-cell fo:blockHEADER CEL 1/fo:block /fo:table-cell fo:table-cell fo:blockHEADER CEL 2/fo:block /fo:table-cell fo:table-cell fo:blockHEADER CEL 3/fo:block /fo:table-cell /fo:table-row /fo:table-body /fo:table /fo:static-content /xsl:template !-- Control Page Sequence Creation -- xsl:template name=ctrlPage xsl:if test=(position() mod 3) = 0 xsl:text disable-output-escaping=yes![CDATA[/fo:flow/fo:page-sequencefo:page-sequence master-reference=A4
Re: multi page-sequence don't work for (XML+XSL) to PDF on the fly
On 09.01.2004 18:29:14 Clóvis Wichoski wrote: snip/ xsl:template name=ctrlPage xsl:if test=(position() mod 3) = 0 xsl:text disable-output-escaping=yes![CDATA[/fo:flow/fo:page-sequencefo:page-sequence master-reference=A4 language=pt country=br]]/xsl:text xsl:call-template name=header/ xsl:text disable-output-escaping=yes![CDATA[fo:flow flow-name=xsl-region-body]]/xsl:text /xsl:if /xsl:template The problem is that you put some XML code into a CDATA section. On-the-fly processing works with SAX. And in SAX your code will be delivered as text instead of as elements. snip/ I can't understand because on the fly don't woks and from .fo file generated from xml+xsl transformation work, maybe a bug of FOP, or I can't generate XML elements using CDATA from this form. The latter. I post this in dev list because I think that this is a feature or a bug on FOP then I attached the XSL and XML files that the team can test this issue, and the code is better to read than my bad English ;) Well, bad luck. Your issue would have been a better fit for fop-user. Jeremias Maerki
Re: multi page-sequence don't work for (XML+XSL) to PDF on the fly
Hi Jeremias, The CDATA is only to maintain the XSL well-formed, since I close fo:flow on another template, the tech is good, maybe dev team implement a SAX over the stream from XML+XSL transformation option, this is the feature that I mean. Note that this is to reduce memory consuption. Best regards Clovis Jeremias Maerki wrote: On 09.01.2004 18:29:14 Clvis Wichoski wrote: snip/ xsl:template name="ctrlPage" xsl:if test="(position() mod 3) = 0" xsl:text disable-output-escaping="yes"![CDATA[/fo:flow/fo:page-sequencefo:page-sequence master-reference="A4" language="pt" country="br"]]/xsl:text xsl:call-template name="header"/ xsl:text disable-output-escaping="yes"![CDATA[fo:flow flow-name="xsl-region-body"]]/xsl:text /xsl:if /xsl:template The problem is that you put some XML code into a CDATA section. On-the-fly processing works with SAX. And in SAX your code will be delivered as text instead of as elements. snip/ I can't understand because on the fly don't woks and from .fo file generated from xml+xsl transformation work, maybe a bug of FOP, or I can't generate XML elements using CDATA from this form. The latter. I post this in dev list because I think that this is a feature or a bug on FOP then I attached the XSL and XML files that the team can test this issue, and the code is better to read than my bad English ;) Well, bad luck. Your issue would have been a better fit for fop-user. Jeremias Maerki
Re: multi page-sequence don't work for (XML+XSL) to PDF on the fly
Clóvis Wichoski wrote: The CDATA is only to maintain the XSL well-formed, since I close fo:flow on another template, Opening and closing XML tags within different XSL templates is bad practice. You'll need to redesign your XSL stylesheet or run the XSL Transform as a separate process, serialize the resulting FO and then present the FO to FOP. the tech is good, maybe dev team implement a SAX over the stream from XML+XSL transformation option, this is the feature that I mean. This isnt very clear, but if you mean serializing the result of the XSL transform before processing the FO then I wouldnt see this as a desirable feature for FOP. Mainly because it will slow down processing. If users require this functionality then they can implement it themselves very easily as I suggested above. Note that this is to reduce memory consuption. Chris
Re: multi page-sequence don't work for (XML+XSL) to PDF on the fly
Chris Bowditch wrote: Opening and closing XML tags within different XSL templates is bad practice. You'll need to redesign your XSL stylesheet or run the XSL Transform as a separate process, serialize the resulting FO and then present the FO to FOP. But with multiple pages like 500 pages the redesign must be in XML source, that need redesign in all XSL too (HTML, PDF, TXT and many others), this cause a rework that I attempted to avoid, and only needed because FOP throubles with memory, this is only a relief. Thanks for all reply Clovis
Re: multi page-sequence don't work for (XML+XSL) to PDF on the fly
This is just a guess, but perhaps you could do a pre-pass using XSL to generate multiple output pages, and then use something like iText[1] to concatenate your output files together. FOP Resources: http://xml.apache.org/fop/resources.html I hope this helps! Web Maestro Clay On Jan 9, 2004, at 10:45 AM, Clóvis Wichoski wrote: Chris Bowditch wrote: Opening and closing XML tags within different XSL templates is bad practice. You'll need to redesign your XSL stylesheet or run the XSL Transform as a separate process, serialize the resulting FO and then present the FO to FOP. But with multiple pages like 500 pages the redesign must be in XML source, that need redesign in all XSL too (HTML, PDF, TXT and many others), this cause a rework that I attempted to avoid, and only needed because FOP throubles with memory, this is only a relief. Thanks for all reply Clovis
RE: multi page-sequence don't work for (XML+XSL) to PDF on the fly
-Original Message- From: Clovis Wichoski [mailto:[EMAIL PROTECTED] snip / But with multiple pages like 500 pages the redesign must be in XML source, that need redesign in all XSL too (HTML, PDF, TXT and many others), this cause a rework that I attempted to avoid, and only needed because FOP throubles with memory, this is only a relief. Hi, Can't you use multiple page-sequences instead of just creating one sequence 'interrupted' by the 'ctrlPage' template? A few remarks to help you on your way: 1. I can't seem to find the reason why you are placing the whole fo:static-content into a separate template, since it is ... well, static and it doesn't rely on the elements in the XML (unless something is missing). 2. In the ctrlPage template, you are testing for a position(): you could also use XPath to select these, like xsl:apply-templates select=product[(position() mod 3) = 0] Then inside the product template, use xsl:for-each select=preceding::product[position() 3] / to grab the two preceding product nodes. 3. Check our http://xml.apache.org/fop/resources.html page, among the books and articles, there's a link to Dave Pawson's XSLT FAQ. Over there, you'll find a lot of useful stuff (amongst others on grouping which I think you'll find particularly helpful), so I'll bet you can work out a redesign which affects only the XSL itself and leaves the other files alone. If you really can't get any further, try posting your problem on Mulberry's XSLT list. Warning: it's a quite high-traffic list, but the upside is that the tips are 'highly-usable' ;) Hope this helps! Cheers, Andreas
DO NOT REPLY [Bug 18624] New: - Problem with: multiple page-sequence(s)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18624. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18624 Problem with: multiple page-sequence(s) Summary: Problem with: multiple page-sequence(s) Product: Fop Version: 0.20.5 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Major Priority: Other Component: pdf renderer AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] When I try examples with multiple page sequences, I get an error: [ERROR] master-reference '' for fo:page-sequence matches no simple-page-master or page-sequence-master. This is demonstrated by running: giro.fo advanced example. I have tried other examples from books and get the same result. I haven't found any other documentation stating this is a known problem, or a work around. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: DO NOT REPLY [Bug 18624] New: - Problem with: multiple page-sequence(s)
This is a FAQ: http://xml.apache.org/fop/faq.html#no_page_master 2.1. I get the error: [ERROR]: 'master-reference' for 'fo:page-sequence'matches no 'simple-page-master' or 'page-sequence-master'^ FOP was changed to be in accordance with the latest standard (see XSL standard).The page master for a fo:page-sequence is now refereced by the master-reference attribute. Replace the master-name attributes of your fo:page-sequence elements by master-reference attributes. You have to do this also for fo:single-page-master-reference, fo:repeatable-page-master-reference and fo:conditional-page-master-reference elements in you page master definitions. [EMAIL PROTECTED] wrote: DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18624. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18624 Problem with: multiple page-sequence(s) Summary: Problem with: multiple page-sequence(s) Product: Fop Version: 0.20.5 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Major Priority: Other Component: pdf renderer AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] When I try examples with multiple page sequences, I get an error: [ERROR] master-reference '' for fo:page-sequence matches no simple-page-master or page-sequence-master. This is demonstrated by running: giro.fo advanced example. I have tried other examples from books and get the same result. I haven't found any other documentation stating this is a known problem, or a work around. -- Clay Leeds - [EMAIL PROTECTED] Web Developer - Medata, Inc. - http://www.medata.com PGP Public Key: https://mail.medata.com/pgp/cleeds.asc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
multiple page-sequence
Hi, I have an out of memory problem and I saw that a solution is to make multiple page-sequences. I need a simple and clear example of how to implement multiple page-sequences, it is better a page sequence for each page, because I have a very big xml. Thank you, Emilia - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: multiple page-sequence
hi there, Multiple Page-sequence examples are found in the docs section of the FOP distribution. (cfr docs/examples/pagination/franklin_2pageseqs.fo) good luck Jochen Maes ICT Development KBC Securities (kbcsecurities.com) Havenlaan 12 Avenue du Port SIF 8683 B-1080 Brussels Belgium Tel: +32 2 429 96 81 GSM: +32 496 57 90 99 E-mail : [EMAIL PROTECTED] This message and any attachments hereto are for the named person's use only. It may contain confidential, proprietary or legally privileged information. You may not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. If you have received this e-mail message without being the intended recipient, please notify KBC Securities promptly and delete this e-mail. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of KBC Securities. KBC Securities reserves the right to monitor all e-mail communications through its networks and any messages addressed to, received or sent by KBC Securities or its employees are deemed to be professional in nature. The sender or recipient of any messages to or of KBC Securities agrees that those may be read by other employees of KBC Securities than the stated recipient or sender in order to ensure the continuity of work-related activities and allow supervision thereof. KBC Securities does not accept liability for the correct and complete transmission of the information, nor for any delay or interruption of the transmission, nor for damages arising from the use of, or reliance on, the information. Graziani Emilia [EMAIL PROTECTED]To: [EMAIL PROTECTED] ormula.itcc: Subject: multiple page-sequence 10/03/2003 11:47 Please respond to fop-dev Hi, I have an out of memory problem and I saw that a solution is to make multiple page-sequences. I need a simple and clear example of how to implement multiple page-sequences, it is better a page sequence for each page, because I have a very big xml. Thank you, Emilia - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
R: multiple page-sequence
Hi, thank you Jochen, I have found it, but it is not enought for me. If I would to generate a page-sequence for each page or for each 10 page, have I to define explicitly each page-sequence? I don't know how many pages I could have for each document, it is variable. Emilia -Messaggio originale- Da: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Inviato: lunedì 10 marzo 2003 11.48 A: [EMAIL PROTECTED] Oggetto: Re: multiple page-sequence hi there, Multiple Page-sequence examples are found in the docs section of the FOP distribution. (cfr docs/examples/pagination/franklin_2pageseqs.fo) good luck Jochen Maes ICT Development KBC Securities (kbcsecurities.com) Havenlaan 12 Avenue du Port SIF 8683 B-1080 Brussels Belgium Tel: +32 2 429 96 81 GSM: +32 496 57 90 99 E-mail : [EMAIL PROTECTED] This message and any attachments hereto are for the named person's use only. It may contain confidential, proprietary or legally privileged information. You may not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. If you have received this e-mail message without being the intended recipient, please notify KBC Securities promptly and delete this e-mail. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of KBC Securities. KBC Securities reserves the right to monitor all e-mail communications through its networks and any messages addressed to, received or sent by KBC Securities or its employees are deemed to be professional in nature. The sender or recipient of any messages to or of KBC Securities agrees that those may be read by other employees of KBC Securities than the stated recipient or sender in order to ensure the continuity of work-related activities and allow supervision thereof. KBC Securities does not accept liability for the correct and complete transmission of the information, nor for any delay or interruption of the transmission, nor for damages arising from the use of, or reliance on, the information. Graziani Emilia [EMAIL PROTECTED]To: [EMAIL PROTECTED] ormula.itcc: Subject: multiple page-sequence 10/03/2003 11:47 Please respond to fop-dev Hi, I have an out of memory problem and I saw that a solution is to make multiple page-sequences. I need a simple and clear example of how to implement multiple page-sequences, it is better a page sequence for each page, because I have a very big xml. Thank you, Emilia - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: R: multiple page-sequence
Page Sequences need to be defined up front. If i'm not loosing my mind. If this won't work, then i might help you with configuring the java on how to rule out the out off memory exception. I can create about 4000 documents in a half an hour without using more then 50 k (for smaller pdf files). Do you do multiple documents in one run? Or is it one run for each document. Did you try to set up the memory use for java: java -mx256m blah blah? this can also help, and allows you a bigger minimum/maximum heapsize... good luck Jochen Maes ICT Development KBC Securities (kbcsecurities.com) Havenlaan 12 Avenue du Port SIF 8683 B-1080 Brussels Belgium Tel: +32 2 429 96 81 GSM: +32 496 57 90 99 E-mail : [EMAIL PROTECTED] This message and any attachments hereto are for the named person's use only. It may contain confidential, proprietary or legally privileged information. You may not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. If you have received this e-mail message without being the intended recipient, please notify KBC Securities promptly and delete this e-mail. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of KBC Securities. KBC Securities reserves the right to monitor all e-mail communications through its networks and any messages addressed to, received or sent by KBC Securities or its employees are deemed to be professional in nature. The sender or recipient of any messages to or of KBC Securities agrees that those may be read by other employees of KBC Securities than the stated recipient or sender in order to ensure the continuity of work-related activities and allow supervision thereof. KBC Securities does not accept liability for the correct and complete transmission of the information, nor for any delay or interruption of the transmission, nor for damages arising from the use of, or reliance on, the information. Graziani Emilia [EMAIL PROTECTED]To: [EMAIL PROTECTED] ormula.itcc: Subject: R: multiple page-sequence 10/03/2003 11:57 Please respond to fop-dev Hi, thank you Jochen, I have found it, but it is not enought for me. If I would to generate a page-sequence for each page or for each 10 page, have I to define explicitly each page-sequence? I don't know how many pages I could have for each document, it is variable. Emilia -Messaggio originale- Da: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Inviato: lunedì 10 marzo 2003 11.48 A: [EMAIL PROTECTED] Oggetto: Re: multiple page-sequence hi there, Multiple Page-sequence examples are found in the docs section of the FOP distribution. (cfr docs/examples/pagination/franklin_2pageseqs.fo) good luck Jochen Maes ICT Development KBC Securities (kbcsecurities.com) Havenlaan 12 Avenue du Port SIF 8683 B-1080 Brussels Belgium Tel: +32 2 429 96 81 GSM: +32 496 57 90 99 E-mail : [EMAIL PROTECTED] This message and any attachments hereto are for the named person's use only. It may contain confidential, proprietary or legally privileged information. You may not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. If you have received this e-mail message without being the intended recipient, please notify KBC Securities promptly and delete this e-mail. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of KBC Securities
Re: multiple page-sequence
I repost an example that help me, hope this helps PS: pay attention at the foreach and change row with your xml node ciao ===XML ?xml version=1.0 encoding=iso-8859-1? table rowRow 1/row rowRow 2/row rowRow 3/row rowRow 4/row rowRow 5/row rowRow 6/row rowRow 7/row rowRow 8/row rowRow 9/row rowRow 10/row rowRow 11/row rowRow 12/row rowRow 13/row rowRow 14/row rowRow 15/row rowRow 16/row rowRow 17/row rowRow 18/row rowRow 19/row rowRow 20/row rowRow 21/row rowRow 22/row rowRow 23/row rowRow 24/row rowRow 25/row rowRow 26/row rowRow 27/row /table XSL ?xml version=1.0 encoding=iso-8859-1? xsl:stylesheet xmlns:xsl=http://www.w3.org/1999/XSL/Transform; version=1.0 xsl:output indent=yes/ xsl:template match=table result xsl:for-each select=row[ position() mod 5 = 1 ] page-sequence table xsl:copy-of select=./ xsl:for-each select=following-sibling::row[ position() lt; 5 ] xsl:copy-of select=./ /xsl:for-each /table /page-sequence /xsl:for-each /result /xsl:template /xsl:stylesheet ===RESULT ?xml version=1.0 encoding=utf-8? result page-sequence table rowRow 1/row rowRow 2/row rowRow 3/row rowRow 4/row rowRow 5/row /table /page-sequence page-sequence table rowRow 6/row rowRow 7/row rowRow 8/row rowRow 9/row rowRow 10/row /table /page-sequence page-sequence table rowRow 11/row rowRow 12/row rowRow 13/row rowRow 14/row rowRow 15/row /table /page-sequence page-sequence table rowRow 16/row rowRow 17/row rowRow 18/row rowRow 19/row rowRow 20/row /table /page-sequence page-sequence table rowRow 21/row rowRow 22/row rowRow 23/row rowRow 24/row rowRow 25/row /table /page-sequence page-sequence table rowRow 26/row rowRow 27/row /table /page-sequence /result From: Graziani Emilia [EMAIL PROTECTED] Hi, thank you Jochen, I have found it, but it is not enought for me. If I would to generate a page-sequence for each page or for each 10 page, have I to define explicitly each page-sequence? I don't know how many pages I could have for each document, it is variable. Emilia - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 10846] - retrieve-boundary=page-sequence only works wnen referenced marker is still in the stream renderer's queue.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10846. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10846 retrieve-boundary=page-sequence only works wnen referenced marker is still in the stream renderer's queue. [EMAIL PROTECTED] changed: What|Removed |Added Summary|retrieve-boundary=page-|retrieve-boundary=page- |sequence gives error |sequence only works wnen ||referenced marker is still ||in the stream renderer's ||queue. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Page-sequence-master error
Hello, I'm having problems with a page-sequence-master page layout in my XSL. I want the first page of my PDF to be formatted differently to any subsequent pages, hence I have defined the following layout master: fo:layout-master-set fo:page-sequence-master master-name=seq-master fo:repeatable-page-master-alternatives fo:conditional-page-master-reference page-position=first master-name=first/ fo:conditional-page-master-reference page-position=rest master-name=rest/ /fo:repeatable-page-master-alternatives /fo:page-sequence-master fo:simple-page-master master-name=first page-height=29.7cm page-width=21cm margin-top=0cm margin-bottom=0.5cm margin-left=1.5cm margin-right=1.5cm fo:region-before extent=0.8cm/ fo:region-body margin-top=0.8cm/ fo:region-after extent=0.5cm/ /fo:simple-page-master fo:simple-page-master master-name=rest page-height=29.7cm page-width=21cm margin-top=0cm margin-bottom=0.5cm margin-left=1.5cm margin-right=1.5cm fo:region-body margin-top=0.8cm/ fo:region-before extent=2cm region-name=rest-before-region/ fo:region-after extent=0.5cm/ /fo:simple-page-master /fo:layout-master-set The rest of my XSL is then: fo:page-sequence master-reference=seq-master initial-page-number=1 fo:static-content flow-name=rest-before-region fo:block text-align=start font-weight=normalHEADING TEXT FOR PAGES AFTER PAGE 1/fo:block /fo:static-content fo:flow flow-name=xsl-region-body ... ... /fo:flow /fo:page-sequence The idea is that HEADING TEXT FOR PAGES AFTER PAGE 1 will appear at the top of pages 2 onwards, but not on page 1. However, when I run try to create a PDF using FOP from within my Java application, FOP throws exceptions (stack trace attached as a file - too long to paste directly into email). The first error is thrown by Xalan, and then FOP errors follow. When I use the simple-page-master first by itself (as defined above), without a page-sequence-master, I get no such problems. Can anyone help? I realise the problem is probably within my XSL but I thought it would be useful to post to this list as FOP experts may be able to recognize the cause of the problem from the stack trace of FOP errors. Thanks in advance for any help, Haitham. StackTrace.txt [INFO]: building formatting object tree [INFO]: Parsing of document complete, stopping renderer javax.xml.transform.TransformerException at org.apache.xalan.transformer.TransformerImpl.transformNode(Compiled Code) at org.apache.xalan.transformer.TransformerImpl.run(Compiled Code) at java.lang.Thread.run(Compiled Code) - java.lang.NullPointerException at org.apache.fop.fo.pagination.PageSequence.isFlowForMasterNameDone(Compiled Code) at org.apache.fop.fo.pagination.PageSequence.getNextPageMasterName(Compiled Code) at org.apache.fop.fo.pagination.PageSequence.getNextSimplePageMaster(Compiled Code) at org.apache.fop.fo.pagination.PageSequence.getNextPageMaster(Compiled Code) at org.apache.fop.fo.pagination.PageSequence.makePage(Compiled Code) at org.apache.fop.fo.pagination.PageSequence.format(Compiled Code) at org.apache.fop.apps.StreamRenderer.render(Compiled Code) at org.apache.fop.fo.FOTreeBuilder.endElement(Compiled Code) at org.apache.xalan.transformer.ResultTreeHandler.endElement(Compiled Code) at org.apache.xalan.templates.ElemLiteralResult.execute(Compiled Code) at org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(Compiled Code) at org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(Compiled Code) at org.apache.xalan.transformer.TransformerImpl.applyTemplateToNode(Compiled Code) at org.apache.xalan.transformer.TransformerImpl.transformNode(Compiled Code) at org.apache.xalan.transformer.TransformerImpl.run(Compiled Code) at java.lang.Thread.run(Compiled Code) org.apache.fop.apps.FOPException at org.apache.fop.apps.Driver.render(Compiled Code) at XMLtoPDF.XMLtoPDF.main(Compiled Code) - javax.xml.transform.TransformerException at org.apache.xalan.transformer.TrAXFilter.parse(Compiled Code) at org.apache.fop.apps.Driver.render(Compiled Code) at XMLtoPDF.XMLtoPDF.main(Compiled Code) - javax.xml.transform.TransformerException at org.apache.xalan.transformer.TransformerImpl.transformNode(Compiled Code
Re: Page-sequence-master error
Al-Dhahir, Haitham wrote: I'm having problems with a page-sequence-master page layout in my XSL. I want the first page of my PDF to be formatted differently to any subsequent pages, hence I have defined the following layout master: ... fo:conditional-page-master-reference page-position=first master-name=first/ Use master-reference instead of master-name here (check the spec). J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 10846] - retrieve-boundary=page-sequence gives error
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10846. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10846 retrieve-boundary=page-sequence gives error --- Additional Comments From [EMAIL PROTECTED] 2002-07-19 06:34 --- This works now in CVS maintenance branch, as long as the page with the referenced marker is still in the stream renderer's queue. This can be enforced by using a forward page number citation. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 10846] New: - retrieve-boundary=page-sequence gives error
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10846. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10846 retrieve-boundary=page-sequence gives error Summary: retrieve-boundary=page-sequence gives error Product: Fop Version: 0.20.4 Platform: PC OS/Version: Linux Status: NEW Severity: Normal Priority: Other Component: general AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] If the retrieve-boundary attribute is set to page-sequence rather than page, then org.apache.fop.apps.Fop quits with an [ERROR]: null message. Example fragment: fo:retrieve-marker retrieve-class-name=message retrieve-boundary=page-sequence retrieve-position=first-including-carryover/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 1231] - basic-link can't link to a page-sequence element
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1231. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1231 basic-link can't link to a page-sequence element [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Additional Comments From [EMAIL PROTECTED] 2002-05-03 16:02 --- *** This bug has been marked as a duplicate of 635 *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Page sequence
hello I am using fop 0.20.3. I have to generate 3 TOCs (table of contents, list of figures, list of tables) and a blank page at the end of global 3 TOCs if the 3 TOCs total page count is odd. The problem is that I have to change header depending on the TOC. I have defined 3 'fo:repeatable-page-master-alternatives' in a 'fo:page-sequence-master' but I don't know how to skip from a 'fo:repeatable-page-master-alternatives' to another in 'fo:flow'. The fo:block break-before=page instruction don't make changing the current 'fo:repeatable-page-master-alternatives' Can someone help ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Page sequence
Hi Gilles Just put a break-after=page in the last block intended to be inside each page sequence. Salut. Fred. --- Gilles Beaugeais [EMAIL PROTECTED] a écrit : hello I am using fop 0.20.3. I have to generate 3 TOCs (table of contents, list of figures, list of tables) and a blank page at the end of global 3 TOCs if the 3 TOCs total page count is odd. The problem is that I have to change header depending on the TOC. I have defined 3 'fo:repeatable-page-master-alternatives' in a 'fo:page-sequence-master' but I don't know how to skip from a 'fo:repeatable-page-master-alternatives' to another in 'fo:flow'. The fo:block break-before=page instruction don't make changing the current 'fo:repeatable-page-master-alternatives' Can someone help ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Change page sequence after generating a pdf-document
Hi! We want to change the sequence of pages AFTER the generation of the PDF-document with FOP. Our intention is to publish a document like a book, so we have to produce a sequence of pages like : 1, 4, 2, 3... ( not 1,2,3,4 ...). It is possible to alternate the sequence of the pages? In other words : It is possible to have some influence on the PDF-serialization process ? Thanks for any kind of help! regards Stefan Schmied - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Change page sequence after generating a pdf-document
At 2002-01-17 14:40 +0100, Stefan Schmied wrote: We want to change the sequence of pages AFTER the generation of the PDF-document with FOP. Our intention is to publish a document like a book, so we have to produce a sequence of pages like : 1, 4, 2, 3... ( not 1,2,3,4 ...). It is possible to alternate the sequence of the pages? In other words : It is possible to have some influence on the PDF-serialization process ? For years I've needed to do this with my PDF books in order to offer stacked double-sided copies of the publication. I have been *more* than satisfied (ecstatic?) with Quite Imposing: http://www.quite.com It's the best investment in my publishing process. I'm running Quite Imposing version 1.5b(EN), not even Quite Imposing Plus, and I can do all the rearrangements of pages that I need through simple and straightforward GUI interfaces that figure out all the wierd page numberings needed for different options. I highly recommend it and take the time to cite in the colophon of my books and instructor-led training material. . Ken -- Training Blitz: 3-days XSLT/XPath, 2-days XSLFO - Feb 18-22, 2002 - (Early-bird date for discounts is this Friday!) G. Ken Holmanmailto:[EMAIL PROTECTED] Crane Softwrights Ltd. http://www.CraneSoftwrights.com/f/ Box 266, Kars, Ontario CANADA K0A-2E0 +1(613)489-0999 (Fax:-0995) ISBN 0-13-065196-6Definitive XSLT XPath ISBN 1-894049-08-X Practical Transformation Using XSLT and XPath ISBN 1-894049-07-1 Practical Formatting Using XSLFO XSL/XML/DSSSL/SGML/OmniMark services, books(electronic, printed), articles, training(instructor-live,Internet-live,web/CD,licensed) Next public training:2002-01-18,02-11,12,13,15,18,21, - 03-04,05,06,08,11,04-08,09,10,12,05-14,15,06-04,07 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
[DO NOT REPLY: Bug 1231] basic-link can't link to a page-sequence element
PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1231 *** shadow/1231 Sun May 20 17:24:39 2001 --- shadow/1231.tmp.7007Tue Aug 28 06:00:17 2001 *** *** 1,19 ! Bug#: 1231 ! Product: Fop ! Version: all ! Platform: All ! OS/Version: All ! Status: NEW ! Resolution: ! Severity: Normal ! Priority: ! Component: general ! AssignedTo: [EMAIL PROTECTED] ! ReportedBy: [EMAIL PROTECTED] ! URL: ! Cc: ! Summary: basic-link can't link to a page-sequence element ! It seems that when a basic-link element has got an internal-destination attribute that points to a page-sequence element, FOP won't find the ID, and complains that an ID was referenced but not found. --- 1,18 ! ++ ! | basic-link can't link to a page-sequence element | ! ++ ! |Bug #: 1231Product: Fop | ! | Status: NEW Version: all | ! | Resolution:Platform: All | ! | Severity: Normal OS/Version: All | ! | Priority: High Component: general | ! ++ ! | Assigned To: [EMAIL PROTECTED] | ! | Reported By: [EMAIL PROTECTED] | ! ++ ! | URL: | ! ++ ! | DESCRIPTION | It seems that when a basic-link element has got an internal-destination attribute that points to a page-sequence element, FOP won't find the ID, and complains that an ID was referenced but not found. *** *** 38,41 (this can be reproduced with the DocBook DTD and associated style sheets : page number is not set in TOC for chapters and other top-level components) ! Sylvain --- 37,40 (this can be reproduced with the DocBook DTD and associated style sheets : page number is not set in TOC for chapters and other top-level components) ! Sylvain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Page sequence/Layer/region... argll..
Thu, Aug 16, 2001 at 07:38, Ian Larner a tapoté sur son clavier: Return-Path: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm Precedence: bulk list-help: mailto:[EMAIL PROTECTED] list-unsubscribe: mailto:[EMAIL PROTECTED] list-post: mailto:[EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] Delivered-To: mailing list [EMAIL PROTECTED] Subject: Re: Page sequence/Layer/region... argll.. To: Romain Bourgue [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 From: Ian Larner [EMAIL PROTECTED] Date: Thu, 16 Aug 2001 19:38:38 +0100 X-MIMETrack: Serialize by Router on d06ml006/06/M/IBM(Release 5.0.6 |December 14, 2000) at 16/08/2001 19:38:27 MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Sender: [EMAIL PROTECTED] Romain, I think that the following properties of fo:block should help prevent a block splitting at a page boundary, but I cannot seem to get them to do what they should (with FOP 0.18) keep-together=always keep-with-next=always keep-with-previous=always Ok, I'll check this out... Initially I wanted to use page-break-inside=avoid but it's not supported yet... (You should not need to use them all.) If anyone on fop-dev has successful experience of using these, perhaps they can advise. You can refine the properties with component qualifiers; for example: keep-together.within-page=always For more information, see the examples directory of the FOP installation. You can also force a page break before a block that spills over a page (effectively preventing the spillage) with: break-before=page Good luck! Ian P.S. I'm unplugged until 26th Sept, so I can't respond from now until then. How lucky you are...! I'm in a training period here. I finish on 21th Sept. Therefore, thanks for all your help, it's been realy kind from you to spend time and knowledge to help me... It's always a pleasure to meet people like you. Enjoy your holydays... Romain. Ian Larner User Technologies, IBM Hursley Lab, England Internal: 246440External: +44 1962 816440Fax: +44 9162 816151 Mailpoint 095 email: [EMAIL PROTECTED] The credit belongs to the man ...in the arena, (who) knowing there is no effort without ...shortcomings, actually strives to do the deeds... Theodore Roosevelt Romain Bourgue Romain.Bourgue@SecurityKe To: Ian Larner/UK/IBM@IBMGB epers.com cc: Subject: Re: Page sequence/Layer/region... argll.. 08/16/2001 04:46 PM Please respond to Romain Bourgue Sorry for replying that late... I just come back from the HAL... Thank you for your precious advice... Thanks to your code I managed to find a walk throught for my paging issues. Anyway, one issue remains : Is it possible to avoid a page break into a block ? I checked out the Web for a solution but it seems that many asked but few answered... Thanks for your help. Romain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Page sequence/Layer/region... argll..
Romain, I think that the following properties of fo:block should help prevent a block splitting at a page boundary, but I cannot seem to get them to do what they should (with FOP 0.18) keep-together=always keep-with-next=always keep-with-previous=always (You should not need to use them all.) If anyone on fop-dev has successful experience of using these, perhaps they can advise. You can refine the properties with component qualifiers; for example: keep-together.within-page=always For more information, see the examples directory of the FOP installation. You can also force a page break before a block that spills over a page (effectively preventing the spillage) with: break-before=page Good luck! Ian P.S. I'm unplugged until 26th Sept, so I can't respond from now until then. Ian Larner User Technologies, IBM Hursley Lab, England Internal: 246440External: +44 1962 816440Fax: +44 9162 816151 Mailpoint 095 email: [EMAIL PROTECTED] The credit belongs to the man ...in the arena, (who) knowing there is no effort without ...shortcomings, actually strives to do the deeds... Theodore Roosevelt Romain Bourgue Romain.Bourgue@SecurityKe To: Ian Larner/UK/IBM@IBMGB epers.com cc: Subject: Re: Page sequence/Layer/region... argll.. 08/16/2001 04:46 PM Please respond to Romain Bourgue Sorry for replying that late... I just come back from the HAL... Thank you for your precious advice... Thanks to your code I managed to find a walk throught for my paging issues. Anyway, one issue remains : Is it possible to avoid a page break into a block ? I checked out the Web for a solution but it seems that many asked but few answered... Thanks for your help. Romain - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: page-sequence is missing an sequence-specification Still inwont help
On 19 Jun 2001 23:04:21 -0600, peti ban wrote: I have used both the help of John and Weiqi, but it gives me the same error of page-sequence is missing an sequence-specification as I stated in my first mail. Peti, I saved the .fo file you posted at the beginning of this thread, and run it through Fop. And here's all the errors I encountered: ==Session==Session==Session== [weiqi@gao-2001 weiqi]$ fop -fo .fo -pdf .pdf FOP 0.19.0-CVS using SAX parser org.apache.xerces.parsers.SAXParser building formatting object tree WARNING: A 'flow-name' is required for fo:flow. This constraint will be enforced in future versions of FOP WARNING: Unknown formatting object ^apply-templates setting up fonts formatting FOs into areas [1WARNING: page-number outside block area ] rendering areas to PDF writing out PDF [weiqi@gao-2001 weiqi]$ vi .fo [weiqi@gao-2001 weiqi]$ fop -fo .fo -pdf .pdf FOP 0.19.0-CVS using SAX parser org.apache.xerces.parsers.SAXParser building formatting object tree WARNING: Unknown formatting object ^apply-templates setting up fonts formatting FOs into areas [1WARNING: page-number outside block area ] rendering areas to PDF writing out PDF [weiqi@gao-2001 weiqi]$ vi .fo [weiqi@gao-2001 weiqi]$ fop -fo .fo -pdf .pdf FOP 0.19.0-CVS using SAX parser org.apache.xerces.parsers.SAXParser building formatting object tree setting up fonts formatting FOs into areas [1WARNING: page-number outside block area ] rendering areas to PDF writing out PDF [weiqi@gao-2001 weiqi]$ vi .fo [weiqi@gao-2001 weiqi]$ fop -fo .fo -pdf .pdf FOP 0.19.0-CVS using SAX parser org.apache.xerces.parsers.SAXParser building formatting object tree setting up fonts formatting FOs into areas [1] rendering areas to PDF writing out PDF [weiqi@gao-2001 weiqi]$ xpdf .pdf ==Session==Session==Session== I suspect that the error stems from the book template of your xslt, which you did not post. Could you run just the XSLT transformation on the XML file and post the pure .fo file? You do this by adding $FOP_HOME/lib/xalan-2.0.0.jar into your CLASSPATH, and run java org.apache.xalan.xslt.Process -in foo.xml -xsl bar.xsl -out foo.fo. -- Weiqi Gao [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Problem in page-sequence is missing an sequence-specification
Hi fop users I am using Cocoon 1.8 and generating pdf. But gives an error of missing page-sequence. Like this: Error found handling the request. org.apache.fop.apps.FOPException: page-sequence is missing an sequence-specification at org.apache.fop.fo.pagination.PageSequence.makePage(PageSequence.java:161) at org.apache.fop.fo.pagination.PageSequence.format(PageSequence.java:189) at org.apache.fop.fo.pagination.Root.format(Root.java:104) at org.apache.fop.fo.FOTreeBuilder.format(FOTreeBuilder.java:252) at org.apache.fop.apps.Driver.format(Driver.java:345) at org.apache.cocoon.formatter.FO2PDFFormatter.format(FO2PDFFormatter.java:86) at org.apache.cocoon.Engine.handle(Engine.java:375) at org.apache.cocoon.Cocoon.service(Cocoon.java:167) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:404) at org.apache.tomcat.core.Handler.service(Handler.java:286) at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372) at org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:797) at org.apache.tomcat.core.ContextManager.service(ContextManager.java:743) at org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnection(Ajp12ConnectionHandler.java:166) at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416) at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:498) at java.lang.Thread.run(Thread.java:484) My xsl for the page-layout and page-sequence reads like this: fo:root fo:layout-master-set fo:simple-page-master fo:region-before extent=100pt/ fo:region-body margin-bottom=55pt margin-top=75pt/ fo:region-after extent=0pt/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence fo:static-content flow-name=xsl-region-before fo:page-number/ /fo:static-content fo:flow xsl:apply-templates select=book/ /fo:flow /fo:page-sequence /fo:root I belive some modifications have to be done in xsl so that it can be compatible with Cocoon 1.8. Please help me out of this problem, Thanks in advance. Peti Ban Get free email and a permanent address at http://www.netaddress.com/?N=1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Problem in page-sequence is missing an sequence-specification
fo:root fo:layout-master-set fo:simple-page-master master-name=all fo:region-before extent=100pt/ fo:region-body margin-bottom=55pt margin-top=75pt/ fo:region-after extent=0pt/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence master-name=all fo:static-content flow-name=xsl-region-before fo:page-number/ /fo:static-content fo:flow xsl:apply-templates select=book/ /fo:flow /fo:page-sequence /fo:root John H. Wyman 5160 Darry Lane Dublin, OH 43016 (614)-889-0698 [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Wyman Genealogy Site http://www.wyman.org Francis Wyman Assoc email List http://groups.yahoo.com/group/FrancisWymanAssoc Wyman Family Genealogy Forum http://genforum.genealogy.com/wyman/ The Wyman Surname Message Board http://www.familyhistory.com/messages/messages.asp?category=surnamefor um=Wyman -Original Message- From: peti ban [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 19, 2001 7:35 AM To: [EMAIL PROTECTED] Subject: Problem in page-sequence is missing an sequence-specification Hi fop users I am using Cocoon 1.8 and generating pdf. But gives an error of missing page-sequence. Like this: Error found handling the request. org.apache.fop.apps.FOPException: page-sequence is missing an sequence-specification at org.apache.fop.fo.pagination.PageSequence.makePage(PageSequence.java:161 ) at org.apache.fop.fo.pagination.PageSequence.format(PageSequence.java:189) at org.apache.fop.fo.pagination.Root.format(Root.java:104) at org.apache.fop.fo.FOTreeBuilder.format(FOTreeBuilder.java:252) at org.apache.fop.apps.Driver.format(Driver.java:345) at org.apache.cocoon.formatter.FO2PDFFormatter.format(FO2PDFFormatter.java: 86) at org.apache.cocoon.Engine.handle(Engine.java:375) at org.apache.cocoon.Cocoon.service(Cocoon.java:167) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:404) at org.apache.tomcat.core.Handler.service(Handler.java:286) at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372) at org.apache.tomcat.core.ContextManager.internalService(ContextManager.jav a:797) at org.apache.tomcat.core.ContextManager.service(ContextManager.java:743) at org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnec tion(Ajp12ConnectionHandler.java:166) at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416 ) at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:49 8) at java.lang.Thread.run(Thread.java:484) My xsl for the page-layout and page-sequence reads like this: fo:root fo:layout-master-set fo:simple-page-master fo:region-before extent=100pt/ fo:region-body margin-bottom=55pt margin-top=75pt/ fo:region-after extent=0pt/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence fo:static-content flow-name=xsl-region-before fo:page-number/ /fo:static-content fo:flow xsl:apply-templates select=book/ /fo:flow /fo:page-sequence /fo:root I belive some modifications have to be done in xsl so that it can be compatible with Cocoon 1.8. Please help me out of this problem, Thanks in advance. Peti Ban Get free email and a permanent address at http://www.netaddress.com/?N=1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: [RE: Problem in page-sequence is missing an sequence-specification]
Hi John thanx for your help but it wont help me either as I have tried your idea of giving master name to simple-page and page-sequence. bye Subhajyoti John Wyman [EMAIL PROTECTED] wrote: fo:root fo:layout-master-set fo:simple-page-master master-name=all fo:region-before extent=100pt/ fo:region-body margin-bottom=55pt margin-top=75pt/ fo:region-after extent=0pt/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence master-name=all fo:static-content flow-name=xsl-region-before fo:page-number/ /fo:static-content fo:flow xsl:apply-templates select=book/ /fo:flow /fo:page-sequence /fo:root John H. Wyman 5160 Darry Lane Dublin, OH 43016 (614)-889-0698 [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Wyman Genealogy Site http://www.wyman.org Francis Wyman Assoc email List http://groups.yahoo.com/group/FrancisWymanAssoc Wyman Family Genealogy Forum http://genforum.genealogy.com/wyman/ The Wyman Surname Message Board http://www.familyhistory.com/messages/messages.asp?category=surnamefor um=Wyman -Original Message- From: peti ban [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 19, 2001 7:35 AM To: [EMAIL PROTECTED] Subject: Problem in page-sequence is missing an sequence-specification Hi fop users I am using Cocoon 1.8 and generating pdf. But gives an error of missing page-sequence. Like this: Error found handling the request. org.apache.fop.apps.FOPException: page-sequence is missing an sequence-specification at org.apache.fop.fo.pagination.PageSequence.makePage(PageSequence.java:161 ) at org.apache.fop.fo.pagination.PageSequence.format(PageSequence.java:189) at org.apache.fop.fo.pagination.Root.format(Root.java:104) at org.apache.fop.fo.FOTreeBuilder.format(FOTreeBuilder.java:252) at org.apache.fop.apps.Driver.format(Driver.java:345) at org.apache.cocoon.formatter.FO2PDFFormatter.format(FO2PDFFormatter.java: 86) at org.apache.cocoon.Engine.handle(Engine.java:375) at org.apache.cocoon.Cocoon.service(Cocoon.java:167) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:404) at org.apache.tomcat.core.Handler.service(Handler.java:286) at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372) at org.apache.tomcat.core.ContextManager.internalService(ContextManager.jav a:797) at org.apache.tomcat.core.ContextManager.service(ContextManager.java:743) at org.apache.tomcat.service.connector.Ajp12ConnectionHandler.processConnec tion(Ajp12ConnectionHandler.java:166) at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416 ) at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:49 8) at java.lang.Thread.run(Thread.java:484) My xsl for the page-layout and page-sequence reads like this: fo:root fo:layout-master-set fo:simple-page-master fo:region-before extent=100pt/ fo:region-body margin-bottom=55pt margin-top=75pt/ fo:region-after extent=0pt/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence fo:static-content flow-name=xsl-region-before fo:page-number/ /fo:static-content fo:flow xsl:apply-templates select=book/ /fo:flow /fo:page-sequence /fo:root I belive some modifications have to be done in xsl so that it can be compatible with Cocoon 1.8. Please help me out of this problem, Thanks in advance. Peti Ban Get free email and a permanent address at http://www.netaddress.com/?N=1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] Get free email and a permanent address at http://www.netaddress.com/?N=1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
