Re: org.apache.fop.fo.ValidationException: fo:list-block is missing child elements
On 12/07/2011 12:11, Glenn Adams wrote: this is not a bug, as pointed out by Pascal By debug I meant debug the XSLT/XSL-FO rather than the Java code. On Tue, Jul 12, 2011 at 5:08 AM, Chris Bowditch bowditch_ch...@hotmail.com mailto:bowditch_ch...@hotmail.com wrote: On 12/07/2011 09:52, tecshine wrote: Hi, Thanks for the reply Pascal I have tried using fopFactory.setStrictValidation(false); but it doesnt solve the problem. Our entire application was based on FOP 0.20.5 and rewriting all XSLTs would mean a lot of work. Is there any other way we can resolve the issue. Can you generate the XSL-FO and post it to the list (if its not too big) Since you are submitting XSLT+XML to fop you will need to use -foout option when running FOP from the command line to generate the intermediate XSL-FO. We can debug the issue by looking at the XSL-FO. Thanks, Chris Pascal Sancho wrote: Hi Swetha, FOP 1.0 is more strict than FOP 0.2x regarding the XSL-FO REC 1.1. Probably you will experiment further ValidationExceptions against FO elements or attributes (missing %block% in fo:table-cell is the most popular). The best way is to rewrite your XSL-T to produce strict XSL-FO. But FOP team offered a configuration tip to help in FOP 0.2x to Latest migration: see [strict-validation] element at [1]. [1] http://xmlgraphics.apache.org/fop/1.0/configuration.html#general-available Le 12/07/2011 08:14, tecshine a écrit : I have migrated from fop 0.20.5 to FOP 1.0. I get the following exception javax.xml.transform.TransformerException: org.apache.fop.fo http://org.apache.fop.fo.ValidationException: fo:list-block is missing child elements. Required content model: marker* (list-item)+ (See position 369:112) I am aware that this kind of errors occur when the parent is empty or doesnt have child elements, so check the xsl file .All fo:list-block elements in the xsl file contain at least one fo:list-item child element. Even then I stumble upon this exception. Can someone help me get out of this please. Thanks in advance Swetha -- Pascal - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org mailto:fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org mailto:fop-users-h...@xmlgraphics.apache.org - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org mailto:fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org mailto:fop-users-h...@xmlgraphics.apache.org - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: org.apache.fop.fo.ValidationException: fo:list-block is missing child elements
I get this error intermittently while generating PDF report using FOP 1.0. null:5511:928: {http://www.w3.org/1999/XSL/Format}block; is not a valid child of fo:table-row! (See position 5511:928). In most cases this issue is resolved on resubmitting the report. Can any one pin point what is the actual cause of this issue and why it is happening occasionally for the same input? org.apache.fop.fo.ValidationException: { http://www.w3.org/1999/XSL/Format}block; is not a valid child of fo:table-row! (See position 1143:945) On Fri, Jul 15, 2011 at 9:42 AM, Chris Bowditch bowditch_ch...@hotmail.comwrote: On 12/07/2011 12:11, Glenn Adams wrote: this is not a bug, as pointed out by Pascal By debug I meant debug the XSLT/XSL-FO rather than the Java code. On Tue, Jul 12, 2011 at 5:08 AM, Chris Bowditch bowditch_ch...@hotmail.com mailto:bowditch_chris@**hotmail.combowditch_ch...@hotmail.com wrote: On 12/07/2011 09:52, tecshine wrote: Hi, Thanks for the reply Pascal I have tried using fopFactory.**setStrictValidation(false); but it doesnt solve the problem. Our entire application was based on FOP 0.20.5 and rewriting all XSLTs would mean a lot of work. Is there any other way we can resolve the issue. Can you generate the XSL-FO and post it to the list (if its not too big) Since you are submitting XSLT+XML to fop you will need to use -foout option when running FOP from the command line to generate the intermediate XSL-FO. We can debug the issue by looking at the XSL-FO. Thanks, Chris Pascal Sancho wrote: Hi Swetha, FOP 1.0 is more strict than FOP 0.2x regarding the XSL-FO REC 1.1. Probably you will experiment further ValidationExceptions against FO elements or attributes (missing %block% in fo:table-cell is the most popular). The best way is to rewrite your XSL-T to produce strict XSL-FO. But FOP team offered a configuration tip to help in FOP 0.2x to Latest migration: see [strict-validation] element at [1]. [1] http://xmlgraphics.apache.org/**fop/1.0/configuration.html#** general-availablehttp://xmlgraphics.apache.org/fop/1.0/configuration.html#general-available Le 12/07/2011 08:14, tecshine a écrit : I have migrated from fop 0.20.5 to FOP 1.0. I get the following exception javax.xml.transform.**TransformerException: org.apache.fop.fo http://org.apache.fop.fo.**ValidationException: fo:list-block is missing child elements. Required content model: marker* (list-item)+ (See position 369:112) I am aware that this kind of errors occur when the parent is empty or doesnt have child elements, so check the xsl file .All fo:list-block elements in the xsl file contain at least one fo:list-item child element. Even then I stumble upon this exception. Can someone help me get out of this please. Thanks in advance Swetha -- Pascal --**-- **- To unsubscribe, e-mail: fop-users-unsubscribe@**xmlgraphics.apache.orgfop-users-unsubscr...@xmlgraphics.apache.org mailto:fop-users-unsubscribe@**xmlgraphics.apache.orgfop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-help@xmlgraphics.**apache.orgfop-users-h...@xmlgraphics.apache.org mailto:fop-users-help@**xmlgraphics.apache.orgfop-users-h...@xmlgraphics.apache.org --**--** - To unsubscribe, e-mail: fop-users-unsubscribe@**xmlgraphics.apache.orgfop-users-unsubscr...@xmlgraphics.apache.org mailto:fop-users-unsubscribe@**xmlgraphics.apache.orgfop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-help@xmlgraphics.**apache.orgfop-users-h...@xmlgraphics.apache.org mailto:fop-users-help@**xmlgraphics.apache.orgfop-users-h...@xmlgraphics.apache.org --**--**- To unsubscribe, e-mail: fop-users-unsubscribe@**xmlgraphics.apache.orgfop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-help@xmlgraphics.**apache.orgfop-users-h...@xmlgraphics.apache.org -- Thanks, Hamed Mohammed, Email: mohdhamedms...@gmail.com.
Re: org.apache.fop.fo.ValidationException: fo:list-block is missing child elements
On 15 Jul 2011, at 17:54, Hamed Mohammed wrote: Hi Just to get it out of the way: please refrain from hijacking existing threads in the future, unless it really is the same issue. The OP was about fo:list-blocks, your issue concerns fo:table-rows. The OP was about missing child elements, your issue is about a wrong child element. Apart from the fact that a ValidationException is thrown, the cases have nothing in common... I get this error intermittently while generating PDF report using FOP 1.0. null:5511:928: {http://www.w3.org/1999/XSL/Format}block; is not a valid child of fo:table-row! (See position 5511:928). snip / In most cases this issue is resolved on resubmitting the report. Can any one pin point what is the actual cause of this issue and why it is happening occasionally for the same input? This means that, at line 5511, column 928 in the FO source, there is a fo:block that ends up as a direct child of a fo:table-row, and that is not allowed by XSL-FO (see: http://www.w3.org/TR/xsl/#fo_table-row - only fo:table-cells are allowed as child nodes) I would suspect it is actually NOT the same input. Have you verified that the FO is really identical in both cases? If so, can you post a sample? Regards, Andreas --- - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: org.apache.fop.fo.ValidationException: fo:list-block is missing child elements
See [1]. Valid children of table-row are table-cell+. [1] http://www.w3.org/TR/2006/REC-xsl11-20061205/#fo_table-row On Fri, Jul 15, 2011 at 11:54 AM, Hamed Mohammed mohdhamedms...@gmail.comwrote: I get this error intermittently while generating PDF report using FOP 1.0. null:5511:928: {http://www.w3.org/1999/XSL/Format}block; is not a valid child of fo:table-row! (See position 5511:928). In most cases this issue is resolved on resubmitting the report. Can any one pin point what is the actual cause of this issue and why it is happening occasionally for the same input? org.apache.fop.fo.ValidationException: { http://www.w3.org/1999/XSL/Format}block; is not a valid child of fo:table-row! (See position 1143:945) On Fri, Jul 15, 2011 at 9:42 AM, Chris Bowditch bowditch_ch...@hotmail.com wrote: On 12/07/2011 12:11, Glenn Adams wrote: this is not a bug, as pointed out by Pascal By debug I meant debug the XSLT/XSL-FO rather than the Java code. On Tue, Jul 12, 2011 at 5:08 AM, Chris Bowditch bowditch_ch...@hotmail.com mailto:bowditch_chris@**hotmail.combowditch_ch...@hotmail.com wrote: On 12/07/2011 09:52, tecshine wrote: Hi, Thanks for the reply Pascal I have tried using fopFactory.**setStrictValidation(false); but it doesnt solve the problem. Our entire application was based on FOP 0.20.5 and rewriting all XSLTs would mean a lot of work. Is there any other way we can resolve the issue. Can you generate the XSL-FO and post it to the list (if its not too big) Since you are submitting XSLT+XML to fop you will need to use -foout option when running FOP from the command line to generate the intermediate XSL-FO. We can debug the issue by looking at the XSL-FO. Thanks, Chris Pascal Sancho wrote: Hi Swetha, FOP 1.0 is more strict than FOP 0.2x regarding the XSL-FO REC 1.1. Probably you will experiment further ValidationExceptions against FO elements or attributes (missing %block% in fo:table-cell is the most popular). The best way is to rewrite your XSL-T to produce strict XSL-FO. But FOP team offered a configuration tip to help in FOP 0.2x to Latest migration: see [strict-validation] element at [1]. [1] http://xmlgraphics.apache.org/**fop/1.0/configuration.html#** general-availablehttp://xmlgraphics.apache.org/fop/1.0/configuration.html#general-available Le 12/07/2011 08:14, tecshine a écrit : I have migrated from fop 0.20.5 to FOP 1.0. I get the following exception javax.xml.transform.**TransformerException: org.apache.fop.fo http://org.apache.fop.fo.**ValidationException: fo:list-block is missing child elements. Required content model: marker* (list-item)+ (See position 369:112) I am aware that this kind of errors occur when the parent is empty or doesnt have child elements, so check the xsl file .All fo:list-block elements in the xsl file contain at least one fo:list-item child element. Even then I stumble upon this exception. Can someone help me get out of this please. Thanks in advance Swetha -- Pascal --** --**- To unsubscribe, e-mail: fop-users-unsubscribe@**xmlgraphics.apache.orgfop-users-unsubscr...@xmlgraphics.apache.org mailto:fop-users-unsubscribe@**xmlgraphics.apache.orgfop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-help@xmlgraphics.**apache.orgfop-users-h...@xmlgraphics.apache.org mailto:fop-users-help@**xmlgraphics.apache.orgfop-users-h...@xmlgraphics.apache.org --**--** - To unsubscribe, e-mail: fop-users-unsubscribe@**xmlgraphics.apache.orgfop-users-unsubscr...@xmlgraphics.apache.org mailto:fop-users-unsubscribe@**xmlgraphics.apache.orgfop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-help@xmlgraphics.**apache.orgfop-users-h...@xmlgraphics.apache.org mailto:fop-users-help@**xmlgraphics.apache.orgfop-users-h...@xmlgraphics.apache.org --**--**- To unsubscribe, e-mail: fop-users-unsubscribe@**xmlgraphics.apache.orgfop-users-unsubscr...@xmlgraphics.apache.org For
org.apache.fop.fo.ValidationException: fo:list-block is missing child elements
I have migrated from fop 0.20.5 to FOP 1.0. I get the following exception javax.xml.transform.TransformerException: org.apache.fop.fo.ValidationException: fo:list-block is missing child elements. Required content model: marker* (list-item)+ (See position 369:112) I am aware that this kind of errors occur when the parent is empty or doesnt have child elements, so check the xsl file .All fo:list-block elements in the xsl file contain at least one fo:list-item child element. Even then I stumble upon this exception. Can someone help me get out of this please. Thanks in advance Swetha -- View this message in context: http://old.nabble.com/org.apache.fop.fo.ValidationException%3A-%22fo%3Alist-block%22-is-missing-child-elements-tp32043465p32043465.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
Re: org.apache.fop.fo.ValidationException: fo:list-block is missing child elements
Hi Swetha, FOP 1.0 is more strict than FOP 0.2x regarding the XSL-FO REC 1.1. Probably you will experiment further ValidationExceptions against FO elements or attributes (missing %block% in fo:table-cell is the most popular). The best way is to rewrite your XSL-T to produce strict XSL-FO. But FOP team offered a configuration tip to help in FOP 0.2x to Latest migration: see [strict-validation] element at [1]. [1] http://xmlgraphics.apache.org/fop/1.0/configuration.html#general-available Le 12/07/2011 08:14, tecshine a écrit : I have migrated from fop 0.20.5 to FOP 1.0. I get the following exception javax.xml.transform.TransformerException: org.apache.fop.fo.ValidationException: fo:list-block is missing child elements. Required content model: marker* (list-item)+ (See position 369:112) I am aware that this kind of errors occur when the parent is empty or doesnt have child elements, so check the xsl file .All fo:list-block elements in the xsl file contain at least one fo:list-item child element. Even then I stumble upon this exception. Can someone help me get out of this please. Thanks in advance Swetha -- Pascal - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: org.apache.fop.fo.ValidationException: fo:list-block is missing child elements
Thanks for the reply Pascal I have tried using fopFactory.setStrictValidation(false); but it doesnt solve the problem. Our entire application was based on FOP 0.20.5 and rewriting all XSLTs would mean a lot of work. Is there any other way we can resolve the issue. Pascal Sancho wrote: Hi Swetha, FOP 1.0 is more strict than FOP 0.2x regarding the XSL-FO REC 1.1. Probably you will experiment further ValidationExceptions against FO elements or attributes (missing %block% in fo:table-cell is the most popular). The best way is to rewrite your XSL-T to produce strict XSL-FO. But FOP team offered a configuration tip to help in FOP 0.2x to Latest migration: see [strict-validation] element at [1]. [1] http://xmlgraphics.apache.org/fop/1.0/configuration.html#general-available Le 12/07/2011 08:14, tecshine a écrit : I have migrated from fop 0.20.5 to FOP 1.0. I get the following exception javax.xml.transform.TransformerException: org.apache.fop.fo.ValidationException: fo:list-block is missing child elements. Required content model: marker* (list-item)+ (See position 369:112) I am aware that this kind of errors occur when the parent is empty or doesnt have child elements, so check the xsl file .All fo:list-block elements in the xsl file contain at least one fo:list-item child element. Even then I stumble upon this exception. Can someone help me get out of this please. Thanks in advance Swetha -- Pascal - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org -- View this message in context: http://old.nabble.com/org.apache.fop.fo.ValidationException%3A-%22fo%3Alist-block%22-is-missing-child-elements-tp32043465p32044249.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
Re: org.apache.fop.fo.ValidationException: fo:list-block is missing child elements
On 12/07/2011 09:52, tecshine wrote: Hi, Thanks for the reply Pascal I have tried using fopFactory.setStrictValidation(false); but it doesnt solve the problem. Our entire application was based on FOP 0.20.5 and rewriting all XSLTs would mean a lot of work. Is there any other way we can resolve the issue. Can you generate the XSL-FO and post it to the list (if its not too big) Since you are submitting XSLT+XML to fop you will need to use -foout option when running FOP from the command line to generate the intermediate XSL-FO. We can debug the issue by looking at the XSL-FO. Thanks, Chris Pascal Sancho wrote: Hi Swetha, FOP 1.0 is more strict than FOP 0.2x regarding the XSL-FO REC 1.1. Probably you will experiment further ValidationExceptions against FO elements or attributes (missing %block% in fo:table-cell is the most popular). The best way is to rewrite your XSL-T to produce strict XSL-FO. But FOP team offered a configuration tip to help in FOP 0.2x to Latest migration: see [strict-validation] element at [1]. [1] http://xmlgraphics.apache.org/fop/1.0/configuration.html#general-available Le 12/07/2011 08:14, tecshine a écrit : I have migrated from fop 0.20.5 to FOP 1.0. I get the following exception javax.xml.transform.TransformerException: org.apache.fop.fo.ValidationException: fo:list-block is missing child elements. Required content model: marker* (list-item)+ (See position 369:112) I am aware that this kind of errors occur when the parent is empty or doesnt have child elements, so check the xsl file .All fo:list-block elements in the xsl file contain at least one fo:list-item child element. Even then I stumble upon this exception. Can someone help me get out of this please. Thanks in advance Swetha -- Pascal - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: org.apache.fop.fo.ValidationException: fo:list-block is missing child elements
this is not a bug, as pointed out by Pascal On Tue, Jul 12, 2011 at 5:08 AM, Chris Bowditch bowditch_ch...@hotmail.comwrote: On 12/07/2011 09:52, tecshine wrote: Hi, Thanks for the reply Pascal I have tried using fopFactory.**setStrictValidation(false); but it doesnt solve the problem. Our entire application was based on FOP 0.20.5 and rewriting all XSLTs would mean a lot of work. Is there any other way we can resolve the issue. Can you generate the XSL-FO and post it to the list (if its not too big) Since you are submitting XSLT+XML to fop you will need to use -foout option when running FOP from the command line to generate the intermediate XSL-FO. We can debug the issue by looking at the XSL-FO. Thanks, Chris Pascal Sancho wrote: Hi Swetha, FOP 1.0 is more strict than FOP 0.2x regarding the XSL-FO REC 1.1. Probably you will experiment further ValidationExceptions against FO elements or attributes (missing %block% in fo:table-cell is the most popular). The best way is to rewrite your XSL-T to produce strict XSL-FO. But FOP team offered a configuration tip to help in FOP 0.2x to Latest migration: see [strict-validation] element at [1]. [1] http://xmlgraphics.apache.org/**fop/1.0/configuration.html#** general-availablehttp://xmlgraphics.apache.org/fop/1.0/configuration.html#general-available Le 12/07/2011 08:14, tecshine a écrit : I have migrated from fop 0.20.5 to FOP 1.0. I get the following exception javax.xml.transform.**TransformerException: org.apache.fop.fo.**ValidationException: fo:list-block is missing child elements. Required content model: marker* (list-item)+ (See position 369:112) I am aware that this kind of errors occur when the parent is empty or doesnt have child elements, so check the xsl file .All fo:list-block elements in the xsl file contain at least one fo:list-item child element. Even then I stumble upon this exception. Can someone help me get out of this please. Thanks in advance Swetha -- Pascal --**--** - To unsubscribe, e-mail: fop-users-unsubscribe@**xmlgraphics.apache.orgfop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-help@xmlgraphics.**apache.orgfop-users-h...@xmlgraphics.apache.org --**--**- To unsubscribe, e-mail: fop-users-unsubscribe@**xmlgraphics.apache.orgfop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-help@xmlgraphics.**apache.orgfop-users-h...@xmlgraphics.apache.org
Re: org.apache.fop.fo.ValidationException: fo:list-block is missing child elements
Dear I generated the XSL-FO for my XML+XSL and the result is too big to post here.I have attached it http://old.nabble.com/file/p32045268/test.out test.out But here is an extract from it which I guess is the cause of the error: fo:list-block line-height=1.5 provisional-label-separation=1cm provisional-distance-between-starts=6cm fo:list-item fo:list-item-label end-indent=label-end() fo:block font-weight=bold text-align=start/ /fo:list-item-label fo:list-item-body start-indent=body-start() fo:list-block space-after=1cm provisional-label-separation=1cm provisional-distance-between-starts=3cm/ /fo:list-item-body /fo:list-item /fo:list-block and the corresponding XSL part for the above is : fo:list-block provisional-distance-between-starts=6cm provisional-label-separation=1cm line-height=1.5 fo:list-item fo:list-item-label end-indent=label-end() fo:block text-align=start font-weight=bold/ /fo:list-item-label fo:list-item-body start-indent=body-start() fo:list-block provisional-distance-between-starts=3cm provisional-label-separation=1cm space-after=1cm xsl:for-each select=SITE/OPENHOURS/DAY fo:list-item fo:list-item-label end-indent=label-end() So is it the usage of fo:list-block inside a fo:list-item-label that caused the problem?? Glenn Adams-2 wrote: this is not a bug, as pointed out by Pascal On Tue, Jul 12, 2011 at 5:08 AM, Chris Bowditch bowditch_ch...@hotmail.comwrote: On 12/07/2011 09:52, tecshine wrote: Hi, Thanks for the reply Pascal I have tried using fopFactory.**setStrictValidation(false); but it doesnt solve the problem. Our entire application was based on FOP 0.20.5 and rewriting all XSLTs would mean a lot of work. Is there any other way we can resolve the issue. Can you generate the XSL-FO and post it to the list (if its not too big) Since you are submitting XSLT+XML to fop you will need to use -foout option when running FOP from the command line to generate the intermediate XSL-FO. We can debug the issue by looking at the XSL-FO. Thanks, Chris Pascal Sancho wrote: Hi Swetha, FOP 1.0 is more strict than FOP 0.2x regarding the XSL-FO REC 1.1. Probably you will experiment further ValidationExceptions against FO elements or attributes (missing %block% in fo:table-cell is the most popular). The best way is to rewrite your XSL-T to produce strict XSL-FO. But FOP team offered a configuration tip to help in FOP 0.2x to Latest migration: see [strict-validation] element at [1]. [1] http://xmlgraphics.apache.org/**fop/1.0/configuration.html#** general-availablehttp://xmlgraphics.apache.org/fop/1.0/configuration.html#general-available Le 12/07/2011 08:14, tecshine a écrit : I have migrated from fop 0.20.5 to FOP 1.0. I get the following exception javax.xml.transform.**TransformerException: org.apache.fop.fo.**ValidationException: fo:list-block is missing child elements. Required content model: marker* (list-item)+ (See position 369:112) I am aware that this kind of errors occur when the parent is empty or doesnt have child elements, so check the xsl file .All fo:list-block elements in the xsl file contain at least one fo:list-item child element. Even then I stumble upon this exception. Can someone help me get out of this please. Thanks in advance Swetha -- Pascal --**--** - To unsubscribe, e-mail: fop-users-unsubscribe@**xmlgraphics.apache.orgfop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-help@xmlgraphics.**apache.orgfop-users-h...@xmlgraphics.apache.org --**--**- To unsubscribe, e-mail: fop-users-unsubscribe@**xmlgraphics.apache.orgfop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-help@xmlgraphics.**apache.orgfop-users-h...@xmlgraphics.apache.org -- View this message in context: http://old.nabble.com/org.apache.fop.fo.ValidationException%3A-%22fo%3Alist-block%22-is-missing-child-elements-tp32043465p32045268.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
RE: org.apache.fop.fo.ValidationException: fo:list-block is missing child elements
Our entire application was based on FOP 0.20.5 and rewriting all XSLTs would mean a lot of work. Is there any other way we can resolve the issue. At risk of being obvious, how about : Don't try to move from 0.20 to 1.0 unless you've got time available to spend sorting out any issues that arise. Unhelpfully, Richard. - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
RE: org.apache.fop.fo.ValidationException: fo:list-block is missing child elements
I have this to come, as I have just upgraded from a customised 0.23 to 1.0 and the first problem I saw was that originally we would define the document as Xsl-region-before Xsl-region-after Xsl-region-body Now we have to have body before everything else.. Plus we had custom cmyk(12%,1%,0%,20%) And now we need cmky(0.12,0.01,0,0.2) its gonna take a while. and o/ Hiya Richard, hows your current project going, been a while since we worked at Bournemouth Kindest regards Theresa Forster Senior Software Developer -Original Message- From: Kerry, Richard [mailto:richard.ke...@atos.net] Sent: 12 July 2011 12:28 To: fop-users@xmlgraphics.apache.org Subject: RE: org.apache.fop.fo.ValidationException: fo:list-block is missing child elements Our entire application was based on FOP 0.20.5 and rewriting all XSLTs would mean a lot of work. Is there any other way we can resolve the issue. At risk of being obvious, how about : Don't try to move from 0.20 to 1.0 unless you've got time available to spend sorting out any issues that arise. Unhelpfully, Richard. - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org - No virus found in this message. Checked by AVG - www.avg.com Version: 10.0.1390 / Virus Database: 1516/3759 - Release Date: 07/11/11 - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
Re: org.apache.fop.fo.ValidationException: fo:list-block is missing child elements
On 07/12/2011 08:08 AM, tecshine wrote: fo:list-block line-height=1.5 provisional-label-separation=1cm provisional-distance-between-starts=6cm fo:list-item fo:list-item-label end-indent=label-end() fo:block font-weight=bold text-align=start/ /fo:list-item-label fo:list-item-body start-indent=body-start() fo:list-block space-after=1cm provisional-label-separation=1cm provisional-distance-between-starts=3cm/ This list-block is empty. That is illegal. /fo:list-item-body /fo:list-item /fo:list-block ~Chris -- Chris Maden, text nerd URL: http://crism.maden.org/ “Mankind are more disposed to suffer, while evils are sufferable than to right themselves by abolishing the forms to which they are accustomed.” — Thomas Jefferson - To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org