Re: Unbound Error
You are correct. Thanks, Luke - Original Message - From: Chris Bowditch [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, January 10, 2005 5:44 AM Subject: Re: Unbound Error Luke Shannon wrote: Hello Andreas; This is the nature of my problem. The block lies outside of the root. It is in a template. I start in root, write some generic stuff and than depending on the params jump of the one of several templates to write out the content. Each template needs to contains its own formatting schema. I was hoping to do this by embedding the content in a fo block. If this is allowed, do I have any other options? I would like to avoid complicating the root template with 13 different output options. I think you just need to define the fo namespace at the top of your xsl:stylesheet, e.g. xsl:stylesheet xmlns:fo=http://www.w3.org/1999/XSL/Format; xsl:template match=/ fo:root ... /fo:root /xsl:template ... /xsl:stylesheet snip/ Chris - 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]
Unbound Error
Hello; I am getting the error: org.xml.sax.SAXParseException: The prefix fo for element fo:block is not bound. I have been clicking around the form archives trying to find a solution to this without much luck. Can someone give me a hint? Thanks, Luke - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Unbound Error
-Original Message- From: Luke Shannon [mailto:[EMAIL PROTECTED] Hi, I am getting the error: org.xml.sax.SAXParseException: The prefix fo for element fo:block is not bound. Without seeing your FO source, difficult to say for sure, but it points to an error in there. Could be caused by something as simple as: ?xml version=1.0 standalone=yes? fo:block / fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; ... /fo:root Having a block outside of the root is, of course, a major error, but even if it weren't the 'fo:' prefix is not yet bound to a namespace for the first fo:block. This error would be encountered before the FO is validated --'validation' being somewhat of an overstatement considering FOP 0.20.5, but you get the idea ;-) HTH! Greetz, Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Unbound Error
Hello Andreas; This is the nature of my problem. The block lies outside of the root. It is in a template. I start in root, write some generic stuff and than depending on the params jump of the one of several templates to write out the content. Each template needs to contains its own formatting schema. I was hoping to do this by embedding the content in a fo block. If this is allowed, do I have any other options? I would like to avoid complicating the root template with 13 different output options. Thanks, Luke - Original Message - From: Andreas L. Delmelle [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, January 07, 2005 1:36 PM Subject: RE: Unbound Error -Original Message- From: Luke Shannon [mailto:[EMAIL PROTECTED] Hi, I am getting the error: org.xml.sax.SAXParseException: The prefix fo for element fo:block is not bound. Without seeing your FO source, difficult to say for sure, but it points to an error in there. Could be caused by something as simple as: ?xml version=1.0 standalone=yes? fo:block / fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; ... /fo:root Having a block outside of the root is, of course, a major error, but even if it weren't the 'fo:' prefix is not yet bound to a namespace for the first fo:block. This error would be encountered before the FO is validated --'validation' being somewhat of an overstatement considering FOP 0.20.5, but you get the idea ;-) HTH! Greetz, Andreas - 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]
