Re: How to create version 2.0 PS files
Hi Chris, cbowditch wrote: OFFENDING COMMAND: setpagedevice ERRORINFO: Key = /PageSize Value = arraytpe STACK: dicttype That error seems to indicate that the Printer doesn't like the Page Size specified. Make sure the dimensions assigned to your simple page master match the paper size supported by the Printer, i.e. if the Printer has a Letter sized paper source but you specified A4 dimensions 297mmx210mm in the simple-page-master then this cause could this type of error. yes that seems to be the reason. If I change paper tray to Letter in the printer configuration everything works well - except normal printings from my users. Strange thing is that the printers accept the PS version 2.0 Letter with A4 printer settings but not the PS version 3.0 Letter with A4 printer settings. But I guess we have to live with that behavior. Thanks, Frank -- View this message in context: http://www.nabble.com/How-to-create-version-2.0-PS-files-tp22804932p22904482.html Sent from the FOP - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Problems with DOMSource
Hi, I'm using fop .94. I'm reading in a .fo file, which is then manipulated by adding more fo that is generated to the flow xsl-region-body. When I try to transform the DOMSource, I get two errors: that the root node is not a valid root node and that it must be fo:root, and that fo:block is not a valid child of block. However, if I turn the DOMSource into a string, everything works fine and I get no errors. I really need to use as DOMSource rather than a string, though. Has anybody had a similar problem? Sam Fuqua ΣΝ ΘΗ 454
Re: Problems with DOMSource
On 06 Apr 2009, at 13:36, Sam Fuqua wrote: Hi I'm using fop .94. I'm reading in a .fo file, which is then manipulated by adding more fo that is generated to the flow xsl- region-body. When I try to transform the DOMSource, I get two errors: that the root node is not a valid root node and that it must be fo:root, and that fo:block is not a valid child of block. However, if I turn the DOMSource into a string, everything works fine and I get no errors. I really need to use as DOMSource rather than a string, though. Has anybody had a similar problem? Yes, in another (non-FO) context. Most likely this is related to namespaces. Are you adding the elements in the correct namespace, or do you just add the 'fo:' prefix and expect that this will magically take care of putting the node in the correct namespace? In the latter case, tough luck, I'm afraid. You have to take care that the additional nodes are added with the correct namespace /URI/ (the prefix should be irrelevant). HTH! Andreas - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: Problems with DOMSource
Andreas, Yes, I believe you're right, which would explain it not working from the DOM, while it would work from the String. I currently have: Node contentNode = printFeed.createElement(fo:block); where I attach generated FO to contentNode. How would you recommend doing the proper namespacing? Just for more information, printFeed is a Document created from reading an FO file that has all of the proper namespacing in it. It is from a namespace-aware DocumentFactory. Sam On Mon, Apr 6, 2009 at 12:13 PM, Andreas Delmelle andreas.delme...@telenet.be wrote: On 06 Apr 2009, at 13:36, Sam Fuqua wrote: Hi I'm using fop .94. I'm reading in a .fo file, which is then manipulated by adding more fo that is generated to the flow xsl-region-body. When I try to transform the DOMSource, I get two errors: that the root node is not a valid root node and that it must be fo:root, and that fo:block is not a valid child of block. However, if I turn the DOMSource into a string, everything works fine and I get no errors. I really need to use as DOMSource rather than a string, though. Has anybody had a similar problem? Yes, in another (non-FO) context. Most likely this is related to namespaces. Are you adding the elements in the correct namespace, or do you just add the 'fo:' prefix and expect that this will magically take care of putting the node in the correct namespace? In the latter case, tough luck, I'm afraid. You have to take care that the additional nodes are added with the correct namespace /URI/ (the prefix should be irrelevant). HTH! Andreas - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org -- Sam Fuqua ΣΝ ΘΗ 454
Re: Problems with DOMSource
On 06 Apr 2009, at 18:23, Sam Fuqua wrote: Hi Sam Yes, I believe you're right, which would explain it not working from the DOM, while it would work from the String. I currently have: Node contentNode = printFeed.createElement(fo:block); IIRC, then you would need: Node contentNode = printFeed.createElementNS(http://www.w3.org/1999/XSL/Format , fo:block); Just checked in the DOM APIdocs, and there it is explicitly mentioned that setting the prefix alone does not influence the namespaceURI. HTH! Andreas - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: Problems with DOMSource
Thank you. That worked perfectly. On Mon, Apr 6, 2009 at 12:34 PM, Andreas Delmelle andreas.delme...@telenet.be wrote: On 06 Apr 2009, at 18:23, Sam Fuqua wrote: Hi Sam Yes, I believe you're right, which would explain it not working from the DOM, while it would work from the String. I currently have: Node contentNode = printFeed.createElement(fo:block); IIRC, then you would need: Node contentNode = printFeed.createElementNS( http://www.w3.org/1999/XSL/Format;, fo:block); Just checked in the DOM APIdocs, and there it is explicitly mentioned that setting the prefix alone does not influence the namespaceURI. HTH! Andreas - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org -- Sam Fuqua ΣΝ ΘΗ 454
RE: Japanese Char Issues
Not sure what happened to the attachment, but here it is: _ Rediscover Hotmail®: Get e-mail storage that grows with you. http://windowslive.com/RediscoverHotmail?ocid=TXT_TAGLM_WL_HM_Rediscover_Storage1_042009 test.pdf Description: Adobe PDF document - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
