Marking Table Headers
Hi , I would like to mark the Heading of Tables as follows Heading1Heading2Heading3Heading4Heading5 specifically I don't want the left and right vertical lines to be printed. How can i do it..?? Thanks in advace bala --- Balajee Chandrasekaran Software Engineer Majesco Software Inc. Phone: 91-22-5695 Extn No 7911 Belief The most fearful unbelief is unbelief in your self. Thomas Carlyle, 1795-1881, Scottish Philosopher, Author. --- MASTEK Investing in relationships In the US, we're called MAJESCO ~~ Opinions expressed in this e-mail are those of the individual and not that of Mastek Limited, unless specifically indicated to that effect. Mastek Limited does not accept any responsibility or liability for it. This e-mail and attachments (if any) transmitted with it are confidential and/or privileged and solely for the use of the intended person or entity to which it is addressed. Any review, re-transmission, dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. This e-mail and its attachments have been scanned for the presence of computer viruses. It is the responsibility of the recipient to run the virus check on e-mails and attachments before opening them. If you have received this e-mail in error, kindly delete this e-mail from all computers. ~~ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: several simple-page-master-objects on one page?
Could you please try to reformulate your question? I don't understand what you intend to do. In XSL-FO a particular page can only have one page-master. I think you're mixing terms. On 07.04.2003 14:56:18 Todtenhaupt, Susann wrote: Is it possible to put more than one page-master-objects on one page (xsl:fo into pdf, ps)? Like ps-printer can do it... Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Marking Table Headers
See the attachement for an example. On 08.04.2003 07:06:42 balajeec wrote: I would like to mark the Heading of Tables as follows Heading1Heading2Heading3Heading4Heading5 specifically I don't want the left and right vertical lines to be printed. How can i do it..?? Jeremias Maerki Balajee-table-header.fo Description: Binary data - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
attribute border-style doesn't work
Hello! There're several values for the attribute border-style when designing a table-cell with xsl:fo. For example dotted, dashed etc. but it doesn't work. There's no aftereffect if this is setted... fo:table-cell border-width=0.5mm border-style=dotted fo:block font-size=14pt font-weight=boldName/fo:block /fo:table-cell What's the fault? suse - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: attribute border-style doesn't work
Todtenhaupt, Susann wrote: Hello! There're several values for the attribute border-style when designing a table-cell with xsl:fo. For example dotted, dashed etc. but it doesn't work. There's no aftereffect if this is setted... fo:table-cell border-width=0.5mm border-style=dotted fo:block font-size=14pt font-weight=boldName/fo:block /fo:table-cell What's the fault? Unimplemented feature (only solid works) Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
feature overview
Hello! Where can I find an overview of features that are supported by fop and things that don't work? greetz suse - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: feature overview
Todtenhaupt, Susann wrote: Where can I find an overview of features that are supported by fop and things that don't work? http://xml.apache.org/fop/compliance.html -- Oleg Tkachenko http://www.tkachenko.com/blog Multiconn Technologies, Israel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: feature overview
There is a nice table on the FOP-Site: http://xml.apache.org/fop/compliance.html Greetings Carsten -Ursprüngliche Nachricht- Von: Todtenhaupt, Susann [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 8. April 2003 11:41 An: '[EMAIL PROTECTED]' Betreff: feature overview Hello! Where can I find an overview of features that are supported by fop and things that don't work? greetz suse - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: feature overview
This side I already found... but what I search is an overview where also the supported values for the attributes are listed. For example: for border-style the value solid only works. -Ursprüngliche Nachricht- Von: Oleg Tkachenko [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 8. April 2003 12:47 An: [EMAIL PROTECTED] Betreff: Re: feature overview Todtenhaupt, Susann wrote: Where can I find an overview of features that are supported by fop and things that don't work? http://xml.apache.org/fop/compliance.html -- Oleg Tkachenko http://www.tkachenko.com/blog Multiconn Technologies, Israel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
About Adobe - Press Room - For Immediate Release
http://www.adobe.com/aboutadobe/pressroom/pressreleases/200304/040703XMLPDF.html Title: About Adobe - Press Room - For Immediate Release Adobe Brings Together XML with the Power and Ubiquity of PDF New XML Architecture Enables Intelligent Documents to Extend the Value of Enterprise SystemsSAN JOSE, Calif. April 7, 2003 (NASDAQ: ADBE) Adobe Systems Incorporated, the leader in network publishing, today announced a comprehensive XML architecture for document creation, collaboration and process management across the enterprise (see separate announcement, "Adobe Delivers Document Integration Solutions for the Extended Enterprise"). The new XML architecture provides an open framework for extending the value of business processes inside and outside the firewall. Now, businesses can bring people and processes together via XML, while retaining the inherent presentation, security and interactivity of documents in the Portable Document Format (PDF). Adobe's XML architecture supports end-to-end document processes. Key components include intelligent forms, process automation, data integration, security and publishing for archiving and printing. The architecture will be supported across Adobe's client and server solutions and will integrate Adobe PDF. It will take full advantage of XML for integration and bring continuity to business processes by presenting XML data in PDF for reliably sharing, viewing and interacting through Acrobat(r) 6.0 software or Adobe Reader. "PDF is a recognized standard for universal access to digital information, and XML provides a powerful mechanism for interchanging data between systems," said Shantanu Narayen, executive vice president, Worldwide Products, Adobe. "By combining these standards, Adobe can provide a set of document integration solutions that promise to redefine how people in large enterprises, government agencies, and financial institutions work with data and documents." Now, companies can create intelligent and interactive documents that include embedded calculations and business logic to help ensure accurate data collection both on and offline. Once the data has been captured, the process can be managed with the Adobe Workflow Server or other core systems. The architecture also enables dynamic rendering of PDF documents from XML for publishing or archiving with XMP meta data for search and retrieval. XML has become a critical standard within the enterprise and government agencies because of its ability to provide data utilization for Web services, reporting and interoperability with enterprise systems. With more than half-a-billion copies of the Adobe Reader distributed to date, PDF is already a universal standard for document-based communications. Now, companies that take advantage of Adobe's XML architecture can easily enable people to participate in business processes. XML combined with the open, cross-platform nature of PDF, means documents can be easily accessed across systems and core business applications for rapid, enterprise-wide deployment. Reliability and policy management features available in Adobe PDF lets businesses control access and integrity of business critical documents across the extended enterprise. All standard XML tools work directly with Adobe's XML architecture and it builds upon W3C XML standards including Namespaces, XSLT, XPath, XML Schema and XML Digital Signatures for full compatibility with existing applications and XML data streams. Over the coming months, Adobe will deliver a new tool for designing XML and PDF templates and forms; make the XML architecture specification publicly available and deliver an XML toolkit for developers to provide easy access to PDF file content from common scripting languages and Java. About Adobe Systems Incorporated Founded in 1982, Adobe Systems Incorporated (www.adobe.com), the leader in network publishing, offers a comprehensive line of software for enterprise and creative professional customers. Its products enable customers to create, manage and deliver visually rich, compelling and reliable content. Based in San Jose, Calif., Adobe is one of the world's largest software companies. ### © 2003 Adobe Systems Incorporated. All rights reserved. Adobe, the Adobe logo, Acrobat and Reader are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries. All other trademarks are the property of their respective owners. Press/Analyst Contacts Rebecca MichalsAdobe Systems Incorporated408-536-4201[EMAIL PROTECTED] Lisa AuslenAR Partners650-762-2805[EMAIL PROTECTED] Copyright 2003 Adobe Systems Incorporated. All rights reserved. Terms of Use Online
Antigen found =*.html file
Antigen for Exchange found 040703XMLPDF.html matching =*.html file filter. The file is currently Removed. The message, About Adobe - Press Room - For Immediate Release, was sent from [EMAIL PROTECTED] and was discovered in SMTP Messages\Inbound located at Questerra/First Administrative Group/QTCAEX01. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: feature overview
You know, that's an awful lot of work to document each and every attribute of the XSL-FO standard. We're working on completing that page. We've had a lot less before Victor put so much work into the compliance page. An hour ago I've added comments on the border-style and font-family attributes in CVS. It'll take a while but that information will make it on the website soon. All users of FOP are invited to participate in making the compliance page better. On 08.04.2003 13:06:23 Todtenhaupt, Susann wrote: This side I already found... but what I search is an overview where also the supported values for the attributes are listed. For example: for border-style the value solid only works. -Ursprüngliche Nachricht- Von: Oleg Tkachenko [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 8. April 2003 12:47 An: [EMAIL PROTECTED] Betreff: Re: feature overview Todtenhaupt, Susann wrote: Where can I find an overview of features that are supported by fop and things that don't work? http://xml.apache.org/fop/compliance.html Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: About Adobe - Press Room - For Immediate Release
Interesting. Not a word about XSL-FO: All standard XML tools work directly with Adobe's XML architecture and it builds upon W3C XML standards including Namespaces, XSLT, XPath, XML Schema and XML Digital Signatures for full compatibility with existing applications and XML data streams. Thanks for the link! On 08.04.2003 13:25:13 toufic.nehme wrote: http://www.adobe.com/aboutadobe/pressroom/pressreleases/200304/040703XMLPDF.html Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: AW: feature overview
Hello jeremias! I know that's a huge effort... I've joined that group not long ago and I've not so much experience with fop. And so I thought somebody can help me in this case. Where did you add this comment on cvs? Thanx! suse -Ursprüngliche Nachricht- Von: Jeremias Maerki [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 8. April 2003 13:32 An: [EMAIL PROTECTED] Betreff: Re: AW: feature overview You know, that's an awful lot of work to document each and every attribute of the XSL-FO standard. We're working on completing that page. We've had a lot less before Victor put so much work into the compliance page. An hour ago I've added comments on the border-style and font-family attributes in CVS. It'll take a while but that information will make it on the website soon. All users of FOP are invited to participate in making the compliance page better. On 08.04.2003 13:06:23 Todtenhaupt, Susann wrote: This side I already found... but what I search is an overview where also the supported values for the attributes are listed. For example: for border-style the value solid only works. -Ursprüngliche Nachricht- Von: Oleg Tkachenko [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 8. April 2003 12:47 An: [EMAIL PROTECTED] Betreff: Re: feature overview Todtenhaupt, Susann wrote: Where can I find an overview of features that are supported by fop and things that don't work? http://xml.apache.org/fop/compliance.html Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Error in PDF file
I am trying to create a simple PDF document. It consists of three pages or simple 2D graphics. I am using the PDFRenderer to create the pages. I create an SVG document from the SVGGraphics2D object. Then create a SVGArea with the SVGDocument. Thie area is then added to the Page's BodyAreaContainer's mainReferenceArea. Thie creates a PDF file that looks like it is large enough with all the pictures. When I open the file in Acrobat reader, I get an error saying Illegal operation 'q' inside a text object And the pages are blank. Why ?? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: attribute border-style doesn't work
Forgive my eavesdropping, but in my experience with FOP, I've seen that when outputting to -pdf, other border-styles work. In particular, I've got dashed working, and I believe dotted works as well. However, I noticed when outputting to -awt/-print it turns into a solid line. This is fine for me. If one of my clients wants it to look pretty, they'll make a PDF first, and then print that. Christian Geisert wrote: Todtenhaupt, Susann wrote: Hello! There're several values for the attribute border-style when designing a table-cell with xsl:fo. For example dotted, dashed etc. but it doesn't work. There's no aftereffect if this is setted... fo:table-cell border-width=0.5mm border-style=dotted fo:block font-size=14pt font-weight=boldName/fo:block /fo:table-cell What's the fault? Unimplemented feature (only solid works) Christian -- 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, e-mail: [EMAIL PROTECTED]
Re: feature overview
Woohoo! There's a party in compliance.html, and everyone's invited! BYOB-S (Bring Your Own Border-Style! ;-p) Seriously, though, perhaps someone (like me? ;-p) could start generating a few test cases like those that are sitting up on renderx.com. Anyone have a set of test cases lying around? Also, where would one submit these? Web Maestro Clay Jeremias Maerki wrote: You know, that's an awful lot of work to document each and every attribute of the XSL-FO standard. We're working on completing that page. We've had a lot less before Victor put so much work into the compliance page. An hour ago I've added comments on the border-style and font-family attributes in CVS. It'll take a while but that information will make it on the website soon. All users of FOP are invited to participate in making the compliance page better. On 08.04.2003 13:06:23 Todtenhaupt, Susann wrote: This side I already found... but what I search is an overview where also the supported values for the attributes are listed. For example: for border-style the value solid only works. -Ursprüngliche Nachricht- Von: Oleg Tkachenko [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 8. April 2003 12:47 An: [EMAIL PROTECTED] Betreff: Re: feature overview Todtenhaupt, Susann wrote: Where can I find an overview of features that are supported by fop and things that don't work? http://xml.apache.org/fop/compliance.html Jeremias Maerki -- 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, e-mail: [EMAIL PROTECTED]
Page number
Hai, I am tryinf to print page # in the format 1 0f 12. I included the following tags it does not work. fo:block id=last-page/ and the tag fo:page-nuber-citation ref-id=last-page/ @ the end of follow. Could anyone pls help, in getting page number in the above mentioned format. Thanks Vikram - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Page number
Exactly what happens when you try that? Do you get a compiler error or a transformer error? Also, please post your stylesheet so we can look at it. Thanks. Mike -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 08, 2003 10:42 AM To: [EMAIL PROTECTED] Subject: Page number Hai, I am tryinf to print page # in the format 1 0f 12. I included the following tags it does not work. fo:block id=last-page/ and the tag fo:page-nuber-citation ref-id=last-page/ @ the end of follow. Could anyone pls help, in getting page number in the above mentioned format. Thanks Vikram - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
fo:block coordinates
Hi, is it possible to take coordinates of fo:blocks in the pdf file when i am rendering pdf with my java application using fop? Thanks for help - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
PDFRenderer.
I am having trouble building pages in PDF. I create a StreamRenderer with a PDFRenderer and a FileOutputStream. I then create an AreaTree with the StreamRenderer. I start the rendering process on the StreamRenderer. I then loop three times to create three pages with a SVG on each page. In the Loop, I get a SVGDocument. Create an SVGArea and set the SVGDocument. I then create a PageMaster and make a Page passing the AreaTree. I then call Page.getBody().getMainReferenceArea().addChild(SVGArea); I then add the Page to the AreaTree. After the Loop I call stoprender() on the StreamRenderer. This all works fine and creates a PDF file. When I try to view the file I get errors like Illegal operation 'q' inside a text object What is this ? How do you create multiple PDF pages ? ?? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Error in PDF file
Ethan, I suspect there's a problem in your XSL-FO file. I had similar things happen to me with fo:list-item, and one of the components turned out to be empty. This caused an error in the renderer. I processed my XML XSL-FO using XALAN.BAT (included with 0.20.5rc), but set my output to -fo. the command line would be (assume c:\java\fop-0.20.5rc is command prompt): c:\java\fop-0.20.5rcxalan.bat -in c:\path\to\your\xmlfile.xml -xsl c:\path\to\your\xslfile.xsl -out c:\path\to\your\outputfofile.fo Hope this helps! Web Maestro Clay (note to FOP-DEV: it'd be nice to add a -fo output option to FOP, for debugging--although xalan.bat does this, it'd be nice not have to learn one more thing ;-p) Leet, Ethan C wrote: I am trying to create a simple PDF document. It consists of three pages or simple 2D graphics. I am using the PDFRenderer to create the pages. I create an SVG document from the SVGGraphics2D object. Then create a SVGArea with the SVGDocument. Thie area is then added to the Page's BodyAreaContainer's mainReferenceArea. Thie creates a PDF file that looks like it is large enough with all the pictures. When I open the file in Acrobat reader, I get an error saying Illegal operation 'q' inside a text object And the pages are blank. Why ?? -- 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, e-mail: [EMAIL PROTECTED]
RE: Error in PDF file
Clay Leeds wrote: (note to FOP-DEV: it'd be nice to add a -fo output option to FOP, for debugging--although xalan.bat does this, it'd be nice not have to learn one more thing ;-p) I suspect the reason why we didn't go that route is that -fo is already used as an /input/ option. The only way you could make this work is to treat -fo differently depending on whether -xml is present. That seems confusing and risky, since a user might accidentally overwrite a valuable fo file this way. I think it is better to keep the two processes separate. Victor Mote - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Error in PDF file
Allow me to clarify what I said. Sorry for the re-post... My problem was in fo:list-block: fo:list-block space-before=6pt space-after=6pt font-family=Times fo:list-item fo:list-item-label end-indent=label-end() fo:block font-family=ZapfDingbats?/fo:block /fo:list-item-label fo:list-item-body start-indent=body-start() fo:block This is the first entry in a plain unordered list. A check symbol is displayed in the bullet. /fo:block /fo:list-item-body /fo:list-item fo:list-item fo:list-item-label end-indent=label-end() fo:block font-family=ZapfDingbats?/fo:block /fo:list-item-label fo:list-item-body start-indent=body-start() fo:block/fo:block /fo:list-item-body /fo:list-item /fo:list-block I was missing content in 2nd fo:list-item-bodyfo:block. The PDF file rendered normally (I think FOP returned a warning), but an error was given when the file was opened in Adobe Acrobat Reader. Unbeknownst to me, my XML file did not include data where it was expected. What did I do? I wrote this list and they recommended I output the FO file using XALAN.BAT, and look for the problem. I found the problem by searching all of the fo:list-block items... Clay Leeds wrote: Ethan, I suspect there's a problem in your XSL-FO file. I had similar things happen to me with fo:list-item, and one of the components turned out to be empty. This caused an error in the renderer. I processed my XML XSL-FO using XALAN.BAT (included with 0.20.5rc), but set my output to -fo. the command line would be (assume c:\java\fop-0.20.5rc is command prompt): c:\java\fop-0.20.5rcxalan.bat -in c:\path\to\your\xmlfile.xml -xsl c:\path\to\your\xslfile.xsl -out c:\path\to\your\outputfofile.fo Hope this helps! Web Maestro Clay (note to FOP-DEV: it'd be nice to add a -fo output option to FOP, for debugging--although xalan.bat does this, it'd be nice not have to learn one more thing ;-p) -- 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, e-mail: [EMAIL PROTECTED]
RE: Page number
Here is the error org.apache.fop.apps.FOPException: The id last-page already exists in this document at org.apache.fop.datatypes.IDReferences.createID(IDReferences.java:77) at org.apache.fop.fo.flow.Block.layout(Block.java:148) at org.apache.fop.fo.flow.StaticContent.layout(StaticContent.java:73) at org.apache.fop.fo.pagination.PageSequence.layoutStaticContent(PageSequence.java:428) at org.apache.fop.fo.pagination.PageSequence.formatStaticContent(PageSequence.java:392) at org.apache.fop.fo.pagination.PageSequence.makePage(PageSequence.java:358) at org.apache.fop.fo.pagination.PageSequence.format(PageSequence.java:290) at org.apache.fop.apps.StreamRenderer.render(StreamRenderer.java:218) at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:177) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.fop.apps.Driver.render(Driver.java:457) Here is the style sheet ?xml version=1.0 encoding=UTF-8? xsl:stylesheet version=1.1 xmlns:xsl =http://www.w3.org/1999/XSL/Transform; xmlns:fo =http://www.w3.org/1999/XSL/Format; exclude-result-prefixes=fo xsl:output method=xml version=1.0 omit-xml-declaration=no indent =yes/ !-- = -- !-- root element: projectteam -- !-- = -- xsl:template match=Report fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set fo:simple-page-master master-name=simpleA4 page-height=21cm page-width=29.7cm margin-top=2cm margin-bottom=2cm margin-left=1cm margin-right=1cm writing-mode=tb-rl fo:region-before extent=4cm/ fo:region-after extent=1cm/ fo:region-body margin-top=2cm margin-bottom=2cm/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence initial-page-number=1 language=en country=us master-reference=simpleA4 fo:static-content flow-name=xsl-region-before fo:block font-size=16pt space-after=2mmxsl:value-of select =projectname/ /fo:block fo:block font-size=10pt color=red font-style=italic space-after =5mmxsl:value-of select=reportInfo/ /fo:block /fo:static-content fo:static-content flow-name=xsl-region-after fo:block text-align=centerpage fo:page-number/fo:page-nuber-citation ref-id=last-page/ of/fo:block fo:block id=last-page/ /fo:static-content fo:flow flow-name=xsl-region-body fo:block font-size=8pt space-after=2mm fo:table table-layout=auto text-align=center xsl:variable name=reportNamexsl:value-of select =reportname//xsl:variable xsl:choose xsl:when test=$reportName='RPT_USER_ACCESS'xsl:call-template name =RPT_USER_ACCESS//xsl:when xsl:when test=$reportName='RPT_TECH_ACCESS'xsl:call-template name =RPT_TECH_ACCESS//xsl:when xsl:when test=$reportName='RPT_NB_BY_DISPCDE'xsl:call-template name =RPT_NB_BY_DISPCDE//xsl:when xsl:when test=$reportName='RPT_NB_BY_NR'xsl:call-template name =RPT_NB_BY_NR//xsl:when xsl:when test=$reportName='RPT_FOR_TOTAL'xsl:call-template name =RPT_FOR_TOTAL//xsl:when /xsl:choose fo:table-header reference-orientation=90 fo:table-row text-align=center background-color=#A1A1A1 xsl:for-each select=ColumnHeader fo:table-cell border-style=solid border-width=0.2mm padding =1.5mm fo:blockxsl:value-of select=text()//fo:block /fo:table-cell /xsl:for-each /fo:table-row /fo:table-header fo:table-body reference-orientation=90 xsl:apply-templates select=Row/ /fo:table-body /fo:table /fo:block /fo:flow /fo:page-sequence /fo:root /xsl:template !-- = -- !-- child element: member -- !-- = -- xsl:template match=Row fo:table-row xsl:for-each select=Column fo:table-cell border-style=solid border-width=0.2mm padding =1.5mm fo:block xsl:value-of select=text()/ /fo:block /fo:table-cell /xsl:for-each /fo:table-row /xsl:template xsl:include href=/includes.xsl/ /xsl:stylesheet Partridge, Michael [EMAIL PROTECTED] on 04/08/2003 12:03:36 PM Please respond to [EMAIL PROTECTED] To:[EMAIL PROTECTED] cc: Subject:RE: Page number Exactly what happens when you try that? Do you get a compiler error or a transformer error? Also, please post your stylesheet so we can look at it. Thanks. Mike -Original Message-
RE: Page number
Remove child fo:block id=last-page/ from the fo:static-content parent. Add fo:block id=last-page to parent fo:flow as the one and only child (encompasses every other child that is currently in fo:flow). Add the end tag for the fo:block just before the /fo:flow. BTW, this is an FAQ. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 08, 2003 1:29 PM To: [EMAIL PROTECTED] Subject: RE: Page number Here is the error org.apache.fop.apps.FOPException: The id last-page already exists in this document at org.apache.fop.datatypes.IDReferences.createID(IDReferences.java:77) at org.apache.fop.fo.flow.Block.layout(Block.java:148) at org.apache.fop.fo.flow.StaticContent.layout(StaticContent.java:73) at org.apache.fop.fo.pagination.PageSequence.layoutStaticContent(PageSequence.j ava:428) at org.apache.fop.fo.pagination.PageSequence.formatStaticContent(PageSequence.j ava:392) at org.apache.fop.fo.pagination.PageSequence.makePage(PageSequence.java:358) at org.apache.fop.fo.pagination.PageSequence.format(PageSequence.java:290) at org.apache.fop.apps.StreamRenderer.render(StreamRenderer.java:218) at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:177) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatc her.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.fop.apps.Driver.render(Driver.java:457) Here is the style sheet ?xml version=1.0 encoding=UTF-8? xsl:stylesheet version=1.1 xmlns:xsl =http://www.w3.org/1999/XSL/Transform; xmlns:fo =http://www.w3.org/1999/XSL/Format; exclude-result-prefixes=fo xsl:output method=xml version=1.0 omit-xml-declaration=no indent =yes/ !-- = -- !-- root element: projectteam -- !-- = -- xsl:template match=Report fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set fo:simple-page-master master-name=simpleA4 page-height=21cm page-width=29.7cm margin-top=2cm margin-bottom=2cm margin-left=1cm margin-right=1cm writing-mode=tb-rl fo:region-before extent=4cm/ fo:region-after extent=1cm/ fo:region-body margin-top=2cm margin-bottom=2cm/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence initial-page-number=1 language=en country=us master-reference=simpleA4 fo:static-content flow-name=xsl-region-before fo:block font-size=16pt space-after=2mmxsl:value-of select =projectname/ /fo:block fo:block font-size=10pt color=red font-style=italic space-after =5mmxsl:value-of select=reportInfo/ /fo:block /fo:static-content fo:static-content flow-name=xsl-region-after fo:block text-align=centerpage fo:page-number/fo:page-nuber-citation ref-id=last-page/ of/fo:block fo:block id=last-page/ /fo:static-content fo:flow flow-name=xsl-region-body fo:block font-size=8pt space-after=2mm fo:table table-layout=auto text-align=center xsl:variable name=reportNamexsl:value-of select =reportname//xsl:variable xsl:choose xsl:when test=$reportName='RPT_USER_ACCESS'xsl:call-template name =RPT_USER_ACCESS//xsl:when xsl:when test=$reportName='RPT_TECH_ACCESS'xsl:call-template name =RPT_TECH_ACCESS//xsl:when xsl:when test=$reportName='RPT_NB_BY_DISPCDE'xsl:call-template name =RPT_NB_BY_DISPCDE//xsl:when xsl:when test=$reportName='RPT_NB_BY_NR'xsl:call-template name =RPT_NB_BY_NR//xsl:when xsl:when test=$reportName='RPT_FOR_TOTAL'xsl:call-template name =RPT_FOR_TOTAL//xsl:when /xsl:choose fo:table-header reference-orientation=90 fo:table-row text-align=center background-color=#A1A1A1 xsl:for-each select=ColumnHeader fo:table-cell border-style=solid border-width=0.2mm padding =1.5mm fo:blockxsl:value-of select=text()//fo:block /fo:table-cell /xsl:for-each /fo:table-row /fo:table-header fo:table-body reference-orientation=90 xsl:apply-templates select=Row/ /fo:table-body /fo:table /fo:block /fo:flow /fo:page-sequence /fo:root /xsl:template !-- = -- !-- child element: member -- !-- = -- xsl:template match=Row fo:table-row xsl:for-each select=Column fo:table-cell border-style=solid border-width=0.2mm padding =1.5mm fo:block xsl:value-of select=text()/ /fo:block /fo:table-cell
Re: Page number
Vikram, I've modified your xsl-fo with two main fixes. I don't have time to test it, but here're the changes: 1. If I recall, since xsl:include documents are treated almost as equals with the parent xsl:document, the xsl:include must be the first child of xsl:stylesheet. 2. The fo:block id=last-page/ must be the last thing in the fo:flow section. That way, when you call it with: fo:static-content flow-name=xsl-region-after fo:block text-align=center Page fo:page-number/ of fo:page-number-citation ref-id=last-page/ /fo:block /fo:static-content It'll be able to calculate the page-number-citation value. 3. You're receiving the error, because you've placed fo:block id=last-page/ in the region-after which is repeated on *every* page. Move it to the end of the fo:flow section, and you're set! Good luck! ?xml version=1.0 encoding=UTF-8? xsl:stylesheet version=1.1 xmlns:xsl=http://www.w3.org/1999/XSL/Transform; xmlns:fo=http://www.w3.org/1999/XSL/Format; exclude-result-prefixes=fo xsl:include href=/includes.xsl/ xsl:output method=xml version=1.0 omit-xml-declaration=no indent=yes/ !-- = -- !-- root element: projectteam -- !-- = -- xsl:template match=Report fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set fo:simple-page-master master-name=simpleA4 page-height=21cm page-width=29.7cm margin-top=2cm margin-bottom=2cm margin-left=1cm margin-right=1cm writing-mode=tb-rl fo:region-before extent=4cm/ fo:region-after extent=1cm/ fo:region-body margin-top=2cm margin-bottom=2cm/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence initial-page-number=1 language=en country=us master-reference=simpleA4 fo:static-content flow-name=xsl-region-before fo:block font-size=16pt space-after=2mmxsl:value-of select =projectname/ /fo:block fo:block font-size=10pt color=red font-style=italic space-after =5mmxsl:value-of select=reportInfo/ /fo:block /fo:static-content fo:static-content flow-name=xsl-region-after fo:block text-align=centerpage fo:page-number/ of fo:page-number-citation ref-id=last-page//fo:block /fo:static-content fo:flow flow-name=xsl-region-body fo:block font-size=8pt space-after=2mm fo:table table-layout=auto text-align=center xsl:variable name=reportNamexsl:value-of select =reportname//xsl:variable xsl:choose xsl:when test=$reportName='RPT_USER_ACCESS'xsl:call-template name =RPT_USER_ACCESS//xsl:when xsl:when test=$reportName='RPT_TECH_ACCESS'xsl:call-template name =RPT_TECH_ACCESS//xsl:when xsl:when test=$reportName='RPT_NB_BY_DISPCDE'xsl:call-template name =RPT_NB_BY_DISPCDE//xsl:when xsl:when test=$reportName='RPT_NB_BY_NR'xsl:call-template name =RPT_NB_BY_NR//xsl:when xsl:when test=$reportName='RPT_FOR_TOTAL'xsl:call-template name =RPT_FOR_TOTAL//xsl:when /xsl:choose fo:table-header reference-orientation=90 fo:table-row text-align=center background-color=#A1A1A1 xsl:for-each select=ColumnHeader fo:table-cell border-style=solid border-width=0.2mm padding =1.5mm fo:blockxsl:value-of select=text()//fo:block /fo:table-cell /xsl:for-each /fo:table-row /fo:table-header fo:table-body reference-orientation=90 xsl:apply-templates select=Row/ /fo:table-body /fo:table /fo:block fo:block id=last-page/ /fo:flow /fo:page-sequence /fo:root /xsl:template !-- = -- !-- child element: member -- !-- = -- xsl:template match=Row fo:table-row xsl:for-each select=Column fo:table-cell border-style=solid border-width=0.2mm padding =1.5mm fo:block xsl:value-of select=text()/ /fo:block /fo:table-cell /xsl:for-each /fo:table-row /xsl:template /xsl:stylesheet -- 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, e-mail: [EMAIL PROTECTED]
RE: Error in PDF file
I am trying to convert your explaination into code instead of
XSL-FO.
I see the missing second fo:list-item-body, but I am unsure how to
match it to this code sample.
public void printPageable(Pageable rcPageable, AttributeSet
rcAttrSet)
throws PrintException
{
// Check the number of pages.
int lnNumOfPages = rcPageable.getNumberOfPages();
if(lnNumOfPages == rcPageable.UNKNOWN_NUMBER_OF_PAGES)
{
lcLog.LogDebug(lnNumOfPages
+ Unknown Number of Pages
+ rcPageable);
throw new PrintException(Can't Handle Unknown Number of Pages.);
}
try
{
// Create a temp file to store the PDF.
FileOutputStream lcFileOut = initStream();
// Initialize the default pageformat.
PageFormat lcFormat = initPageFormat(rcAttrSet);
// Create PDF.
FontInfo lcFontInfo = new FontInfo();
PDFRenderer lcPdfRenderer = new PDFRenderer();
lcPdfRenderer.setupFontInfo(lcFontInfo);
lcPdfRenderer.setProducer(Cleetus-FOP);
// Create an AreaTree for Rendering onto the PDFPage.
StreamRenderer lcStrRenderer = new StreamRenderer(lcFileOut,
lcPdfRenderer);
lcStrRenderer.setLogger(new
ConsoleLogger(ConsoleLogger.LEVEL_INFO));
AreaTree lcAreaTree = new AreaTree(lcStrRenderer);
lcAreaTree.setFontInfo(lcFontInfo);
FontState lcFState = new FontState(lcFontInfo, Helvetica,
normal,
normal, 12, 0);
// Start Rendering
lcStrRenderer.startRenderer();
// Loop over the pages.
int lnPageExists = Printable.PAGE_EXISTS;
for(int lnIndex = 0;
lnIndex lnNumOfPages
lnPageExists != Printable.NO_SUCH_PAGE;
//
//lnIndex 1;
lnIndex++)
{
// Get the PageFormat
PageFormat lcPgFormat = rcPageable.getPageFormat(lnIndex);
if(lcPgFormat == null)
lcPgFormat = lcFormat;
// Initialize the default width and height and X an Y position.
Paper lcPaper = lcFormat.getPaper();
int lnWidth = (int)lcPaper.getWidth() * 1000;
int lnHeight = (int)lcPaper.getHeight() * 1000;
int lnPositionX = (int)lcPaper.getImageableX() * 1000;
int lnPositionY = (int)lcPaper.getImageableY() * 1000;
// Create the SVGDocument
Document lcSvgDoc = SVGUtilities.createSVGDocument(lnWidth/1000,
lnHeight/1000);
// Create the SVGGraphics2D to draw into the SVG Document.
SVGGraphics2D lcSVGGraphics = new SVGGraphics2D(lcSvgDoc);
// Get the Printable and pass the graphics for drawing.
Printable lcPrintable = rcPageable.getPrintable(lnIndex);
lnPageExists = lcPrintable.print(lcSVGGraphics,
lcPgFormat,
lnIndex);
// Get the Root SVg Node from the graphics
// and append it to the SVG Document.
lcSvgDoc.getFirstChild().appendChild(lcSVGGraphics.getRoot());
javax.xml.transform.TransformerFactory factory =
javax.xml.transform.TransformerFactory.newInstance();
javax.xml.transform.Transformer transformer =
factory.newTransformer();
javax.xml.transform.dom.DOMSource source =
new javax.xml.transform.dom.DOMSource(lcSvgDoc);
javax.xml.transform.stream.StreamResult result =
new
javax.xml.transform.stream.StreamResult(test+lnIndex+.svg);
transformer.transform(source, result);
// Create an SVGArea for rendering onto the PDF Page.
SVGArea lcSvgArea = new SVGArea(lcFState, lnWidth/1000,
lnHeight/1000);
lcSvgArea.setSVGDocument(lcSvgDoc);
// Create a Body Area Container
BodyRegionArea lcBodyRegion = new BodyRegionArea(lnPositionX,
lnPositionY,
lnWidth,
lnHeight);
// Create PageMaster who creates PDF Pages.
PageMaster lcPageMaster = new PageMaster(lnWidth, lnHeight);
lcPageMaster.addBody(lcBodyRegion);
// Create a Page with the PageMaster
Page lcCurPage = lcPageMaster.makePage(lcAreaTree);
//lcCurPage.getBody().addChild(lcSvgArea); // does nothing
lcCurPage.getBody().getMainReferenceArea().addChild(lcSvgArea);// adds
invalid q
//lcCurPage.getBody().addChild(lcSvgArea); // does nothing
Re: Error in PDF file
Ethan, I snipped a bit, but found this in your code. Notice the three lines of code which adds invalid q. I don't suppose removing these three lines of code will fix your problem? Otherwise, I can't help. I'm a doctor, not a... er... never mind... Good luck! Leet, Ethan C wrote: // Create a Page with the PageMaster Page lcCurPage = lcPageMaster.makePage(lcAreaTree); //lcCurPage.getBody().addChild(lcSvgArea); // does nothing lcCurPage.getBody().getMainReferenceArea().addChild(lcSvgArea);// adds invalid q //lcCurPage.getBody().addChild(lcSvgArea); // does nothing //lcBody.getMainReferenceArea().addChildAtStart(lcSvgArea); // adds invalid q //lcBody.getMainReferenceArea().addChild(lcSvgArea); // adds invalid q //lcBody.addChild(lcSvgArea); // does nothing lcAreaTree.addPage(lcCurPage); } This will create an invlaid PDF file that will popup an error saying Illegal 'q' in text object -- 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, e-mail: [EMAIL PROTECTED]
RE: Error in PDF file
lcCurPage.getBody().getMainReferenceArea().addChild(lcSvgArea); This line is the line that causes the problem. the // adds invalid q is a note to myself for which lines I have tried, and their result. If I remove the line, I can open the document with no errors, but also no data :-( Thank you. I hopefully will crack this soon :-) -Original Message- From: Clay Leeds [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 08, 2003 2:18 PM To: [EMAIL PROTECTED] Subject: Re: Error in PDF file Ethan, I snipped a bit, but found this in your code. Notice the three lines of code which adds invalid q. I don't suppose removing these three lines of code will fix your problem? Otherwise, I can't help. I'm a doctor, not a... er... never mind... Good luck! Leet, Ethan C wrote: // Create a Page with the PageMaster Page lcCurPage = lcPageMaster.makePage(lcAreaTree); //lcCurPage.getBody().addChild(lcSvgArea); // does nothing lcCurPage.getBody().getMainReferenceArea().addChild(lcSvgArea);// adds invalid q //lcCurPage.getBody().addChild(lcSvgArea); // does nothing //lcBody.getMainReferenceArea().addChildAtStart(lcSvgArea); // adds invalid q //lcBody.getMainReferenceArea().addChild(lcSvgArea); // adds invalid q //lcBody.addChild(lcSvgArea); // does nothing lcAreaTree.addPage(lcCurPage); } This will create an invlaid PDF file that will popup an error saying Illegal 'q' in text object -- 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, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Page number--Correction
Correction: Add fo:block id=last-page/ as the LAST child of fo:flow, don't wrap everything. My apologies. -Original Message- From: Koes, Derrick Sent: Tuesday, April 08, 2003 1:43 PM To: '[EMAIL PROTECTED]' Subject: RE: Page number Remove child fo:block id=last-page/ from the fo:static-content parent. Add fo:block id=last-page to parent fo:flow as the one and only child (encompasses every other child that is currently in fo:flow). Add the end tag for the fo:block just before the /fo:flow. BTW, this is an FAQ. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 08, 2003 1:29 PM To: [EMAIL PROTECTED] Subject: RE: Page number Here is the error org.apache.fop.apps.FOPException: The id last-page already exists in this document at org.apache.fop.datatypes.IDReferences.createID(IDReferences.java:77) at org.apache.fop.fo.flow.Block.layout(Block.java:148) at org.apache.fop.fo.flow.StaticContent.layout(StaticContent.java:73) at org.apache.fop.fo.pagination.PageSequence.layoutStaticContent(PageSequence.j ava:428) at org.apache.fop.fo.pagination.PageSequence.formatStaticContent(PageSequence.j ava:392) at org.apache.fop.fo.pagination.PageSequence.makePage(PageSequence.java:358) at org.apache.fop.fo.pagination.PageSequence.format(PageSequence.java:290) at org.apache.fop.apps.StreamRenderer.render(StreamRenderer.java:218) at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:177) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatc her.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.fop.apps.Driver.render(Driver.java:457) Here is the style sheet ?xml version=1.0 encoding=UTF-8? xsl:stylesheet version=1.1 xmlns:xsl =http://www.w3.org/1999/XSL/Transform; xmlns:fo =http://www.w3.org/1999/XSL/Format; exclude-result-prefixes=fo xsl:output method=xml version=1.0 omit-xml-declaration=no indent =yes/ !-- = -- !-- root element: projectteam -- !-- = -- xsl:template match=Report fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set fo:simple-page-master master-name=simpleA4 page-height=21cm page-width=29.7cm margin-top=2cm margin-bottom=2cm margin-left=1cm margin-right=1cm writing-mode=tb-rl fo:region-before extent=4cm/ fo:region-after extent=1cm/ fo:region-body margin-top=2cm margin-bottom=2cm/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence initial-page-number=1 language=en country=us master-reference=simpleA4 fo:static-content flow-name=xsl-region-before fo:block font-size=16pt space-after=2mmxsl:value-of select =projectname/ /fo:block fo:block font-size=10pt color=red font-style=italic space-after =5mmxsl:value-of select=reportInfo/ /fo:block /fo:static-content fo:static-content flow-name=xsl-region-after fo:block text-align=centerpage fo:page-number/fo:page-nuber-citation ref-id=last-page/ of/fo:block fo:block id=last-page/ /fo:static-content fo:flow flow-name=xsl-region-body fo:block font-size=8pt space-after=2mm fo:table table-layout=auto text-align=center xsl:variable name=reportNamexsl:value-of select =reportname//xsl:variable xsl:choose xsl:when test=$reportName='RPT_USER_ACCESS'xsl:call-template name =RPT_USER_ACCESS//xsl:when xsl:when test=$reportName='RPT_TECH_ACCESS'xsl:call-template name =RPT_TECH_ACCESS//xsl:when xsl:when test=$reportName='RPT_NB_BY_DISPCDE'xsl:call-template name =RPT_NB_BY_DISPCDE//xsl:when xsl:when test=$reportName='RPT_NB_BY_NR'xsl:call-template name =RPT_NB_BY_NR//xsl:when xsl:when test=$reportName='RPT_FOR_TOTAL'xsl:call-template name =RPT_FOR_TOTAL//xsl:when /xsl:choose fo:table-header reference-orientation=90 fo:table-row text-align=center background-color=#A1A1A1 xsl:for-each select=ColumnHeader fo:table-cell border-style=solid border-width=0.2mm padding =1.5mm fo:blockxsl:value-of select=text()//fo:block /fo:table-cell /xsl:for-each /fo:table-row /fo:table-header fo:table-body reference-orientation=90 xsl:apply-templates select=Row/ /fo:table-body /fo:table /fo:block /fo:flow /fo:page-sequence /fo:root /xsl:template !-- = -- !-- child element: member -- !-- =
