[jira] [Commented] (FOP-2496) fop2.0 crashes if docbook is last inside a or a . No bug in fop1.1
[ https://issues.apache.org/jira/browse/FOP-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15146591#comment-15146591 ] Lennart Johansson commented on FOP-2496: Thank you! This has obviously been fixed in FOP 2.1 which works nicely. Best Regards /ljo > fop2.0 crashes if docbook is last inside a or a . No > bug in fop1.1 > -- > > Key: FOP-2496 > URL: https://issues.apache.org/jira/browse/FOP-2496 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 2.0 >Reporter: Lennart Johansson > Attachments: note-problem-fop2.0-listitem-crash.fo, > note-problem-fop2.0-listitem-workaround-patched.fo, > note-problem-fop2.0-step-crash.fo, > note-problem-fop2.0-step-workaround-patched.fo > > > fop2.0 crashes if docbook is last inside a or a . No > bug in fop1.1 > This works in fop1.1 and it is good docbook syntax and should not be a > problem. > A workaround, that also shows the problem, is to insert an empty > between and . > We are now forced to use this workaround in the building scripts - not nice! > Appended: > - note-problem-fop2.0-listitem-crash.fo = Small example .fo file with a note > last in a listitem > - note-problem-fop2.0-listitem-workaround-patched.fo = Workaround-patched > .fo file (listitem) > - note-problem-fop2.0-step-crash.fo = Small example .fo file with a note > last in a step > - note-problem-fop2.0-step-workaround-patched.fo = Workaround-patched .fo > file (step) > The fop CRASH log is below: > INFO: Rendered page #1. > INFO: Rendered page #2. > Jul 8, 2015 8:18:06 PM org.apache.fop.cli.Main startFOP > SEVERE: Exception > java.lang.NullPointerException > at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:288) > at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:115) > at org.apache.fop.cli.Main.startFOP(Main.java:186) > at org.apache.fop.cli.Main.main(Main.java:217) > Caused by: java.lang.NullPointerException > at > org.apache.fop.layoutmgr.list.ListItemLayoutManager.getCombinedKnuthElementsForListItem(ListItemLayoutManager.java:405) > at > org.apache.fop.layoutmgr.list.ListItemLayoutManager.getNextKnuthElements(ListItemLayoutManager.java:326) > at > org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:239) > at > org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextChildElements(BlockStackingLayoutManager.java:498) > at > org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289) > at > org.apache.fop.layoutmgr.list.ListBlockLayoutManager.getNextKnuthElements(ListBlockLayoutManager.java:103) > at > org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:239) > at > org.apache.fop.layoutmgr.FlowLayoutManager.getNextChildElements(FlowLayoutManager.java:223) > at > org.apache.fop.layoutmgr.FlowLayoutManager.addChildElements(FlowLayoutManager.java:147) > at > org.apache.fop.layoutmgr.FlowLayoutManager.getNextKnuthElements(FlowLayoutManager.java:116) > at > org.apache.fop.layoutmgr.FlowLayoutManager.getNextKnuthElements(FlowLayoutManager.java:69) > at > org.apache.fop.layoutmgr.PageBreaker.getNextKnuthElements(PageBreaker.java:252) > at > org.apache.fop.layoutmgr.AbstractBreaker.getNextBlockList(AbstractBreaker.java:643) > at > org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:178) > at > org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:158) > at > org.apache.fop.layoutmgr.AbstractBreaker.doLayout(AbstractBreaker.java:384) > at org.apache.fop.layoutmgr.PageBreaker.doLayout(PageBreaker.java:112) > at > org.apache.fop.layoutmgr.PageSequenceLayoutManager.activateLayout(PageSequenceLayoutManager.java:138) > at > org.apache.fop.area.AreaTreeHandler.endPageSequence(AreaTreeHandler.java:267) > at > org.apache.fop.fo.pagination.PageSequence.endOfNode(PageSequence.java:130) > at > org.apache.fop.fo.FOTreeBuilder$MainFOHandler.endElement(FOTreeBuilder.java:360) > at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:190) > at > org.apache.xalan.transformer.TransformerIdentityImpl.endElement(TransformerIdentityImpl.java:1101) > at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown > Source) > at org.apache.xerces.xinclude.XIncludeHandler.endElement(Unknown > Source) > at > org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) > at >
[jira] [Updated] (FOP-2496) fop2.0 crashes if docbook note is last inside a listitem or a step. No bug in fop1.1
[ https://issues.apache.org/jira/browse/FOP-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lennart Johansson updated FOP-2496: --- Attachment: (was: note-problem-fop2.0-step-crash.fo) fop2.0 crashes if docbook note is last inside a listitem or a step. No bug in fop1.1 -- Key: FOP-2496 URL: https://issues.apache.org/jira/browse/FOP-2496 Project: FOP Issue Type: Bug Components: renderer/pdf Affects Versions: 2.0 Reporter: Lennart Johansson Attachments: note-problem-fop2.0-listitem-crash.fo, note-problem-fop2.0-listitem-workaround-patched.fo fop2.0 crashes if docbook note is last inside a listitem or a step. No bug in fop1.1 This works in fop1.1 and it is good docbook syntax and should not be a problem. A workaround, that also shows the problem, is to insert an empty para between /note and /listitem), or directly in the .fo file, insert an extra fo:block/fo.block. We are now forced to use this workaround in the building scripts - not nice! Appended: - note-problem-fop2.0-listitem-crash.fo = Small example .fo file with a note last in a listitem - note-problem-fop2.0-listitem-workaround-patched.fo = Workaround-patched .fo file (listitem) - note-problem-fop2.0-step-crash.fo = Small example .fo file with a note last in a step - note-problem-fop2.0-step-workaround-patched.fo = Workaround-patched .fo file (step) The fop CRASH log is below: INFO: Rendered page #1. INFO: Rendered page #2. Jul 8, 2015 8:18:06 PM org.apache.fop.cli.Main startFOP SEVERE: Exception java.lang.NullPointerException at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:288) at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:115) at org.apache.fop.cli.Main.startFOP(Main.java:186) at org.apache.fop.cli.Main.main(Main.java:217) Caused by: java.lang.NullPointerException at org.apache.fop.layoutmgr.list.ListItemLayoutManager.getCombinedKnuthElementsForListItem(ListItemLayoutManager.java:405) at org.apache.fop.layoutmgr.list.ListItemLayoutManager.getNextKnuthElements(ListItemLayoutManager.java:326) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:239) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextChildElements(BlockStackingLayoutManager.java:498) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289) at org.apache.fop.layoutmgr.list.ListBlockLayoutManager.getNextKnuthElements(ListBlockLayoutManager.java:103) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:239) at org.apache.fop.layoutmgr.FlowLayoutManager.getNextChildElements(FlowLayoutManager.java:223) at org.apache.fop.layoutmgr.FlowLayoutManager.addChildElements(FlowLayoutManager.java:147) at org.apache.fop.layoutmgr.FlowLayoutManager.getNextKnuthElements(FlowLayoutManager.java:116) at org.apache.fop.layoutmgr.FlowLayoutManager.getNextKnuthElements(FlowLayoutManager.java:69) at org.apache.fop.layoutmgr.PageBreaker.getNextKnuthElements(PageBreaker.java:252) at org.apache.fop.layoutmgr.AbstractBreaker.getNextBlockList(AbstractBreaker.java:643) at org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:178) at org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:158) at org.apache.fop.layoutmgr.AbstractBreaker.doLayout(AbstractBreaker.java:384) at org.apache.fop.layoutmgr.PageBreaker.doLayout(PageBreaker.java:112) at org.apache.fop.layoutmgr.PageSequenceLayoutManager.activateLayout(PageSequenceLayoutManager.java:138) at org.apache.fop.area.AreaTreeHandler.endPageSequence(AreaTreeHandler.java:267) at org.apache.fop.fo.pagination.PageSequence.endOfNode(PageSequence.java:130) at org.apache.fop.fo.FOTreeBuilder$MainFOHandler.endElement(FOTreeBuilder.java:360) at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:190) at org.apache.xalan.transformer.TransformerIdentityImpl.endElement(TransformerIdentityImpl.java:1101) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.xinclude.XIncludeHandler.endElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at
[jira] [Updated] (FOP-2496) fop2.0 crashes if docbook note is last inside a listitem or a step. No bug in fop1.1
[ https://issues.apache.org/jira/browse/FOP-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lennart Johansson updated FOP-2496: --- Attachment: note-problem-fop2.0-step-workaround-patched.fo note-problem-fop2.0-step-crash.fo fop2.0 crashes if docbook note is last inside a listitem or a step. No bug in fop1.1 -- Key: FOP-2496 URL: https://issues.apache.org/jira/browse/FOP-2496 Project: FOP Issue Type: Bug Components: renderer/pdf Affects Versions: 2.0 Reporter: Lennart Johansson Attachments: note-problem-fop2.0-listitem-crash.fo, note-problem-fop2.0-listitem-workaround-patched.fo, note-problem-fop2.0-step-crash.fo, note-problem-fop2.0-step-workaround-patched.fo fop2.0 crashes if docbook note is last inside a listitem or a step. No bug in fop1.1 This works in fop1.1 and it is good docbook syntax and should not be a problem. A workaround, that also shows the problem, is to insert an empty para between /note and /listitem), or directly in the .fo file, insert an extra fo:block/fo.block. We are now forced to use this workaround in the building scripts - not nice! Appended: - note-problem-fop2.0-listitem-crash.fo = Small example .fo file with a note last in a listitem - note-problem-fop2.0-listitem-workaround-patched.fo = Workaround-patched .fo file (listitem) - note-problem-fop2.0-step-crash.fo = Small example .fo file with a note last in a step - note-problem-fop2.0-step-workaround-patched.fo = Workaround-patched .fo file (step) The fop CRASH log is below: INFO: Rendered page #1. INFO: Rendered page #2. Jul 8, 2015 8:18:06 PM org.apache.fop.cli.Main startFOP SEVERE: Exception java.lang.NullPointerException at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:288) at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:115) at org.apache.fop.cli.Main.startFOP(Main.java:186) at org.apache.fop.cli.Main.main(Main.java:217) Caused by: java.lang.NullPointerException at org.apache.fop.layoutmgr.list.ListItemLayoutManager.getCombinedKnuthElementsForListItem(ListItemLayoutManager.java:405) at org.apache.fop.layoutmgr.list.ListItemLayoutManager.getNextKnuthElements(ListItemLayoutManager.java:326) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:239) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextChildElements(BlockStackingLayoutManager.java:498) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289) at org.apache.fop.layoutmgr.list.ListBlockLayoutManager.getNextKnuthElements(ListBlockLayoutManager.java:103) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:239) at org.apache.fop.layoutmgr.FlowLayoutManager.getNextChildElements(FlowLayoutManager.java:223) at org.apache.fop.layoutmgr.FlowLayoutManager.addChildElements(FlowLayoutManager.java:147) at org.apache.fop.layoutmgr.FlowLayoutManager.getNextKnuthElements(FlowLayoutManager.java:116) at org.apache.fop.layoutmgr.FlowLayoutManager.getNextKnuthElements(FlowLayoutManager.java:69) at org.apache.fop.layoutmgr.PageBreaker.getNextKnuthElements(PageBreaker.java:252) at org.apache.fop.layoutmgr.AbstractBreaker.getNextBlockList(AbstractBreaker.java:643) at org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:178) at org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:158) at org.apache.fop.layoutmgr.AbstractBreaker.doLayout(AbstractBreaker.java:384) at org.apache.fop.layoutmgr.PageBreaker.doLayout(PageBreaker.java:112) at org.apache.fop.layoutmgr.PageSequenceLayoutManager.activateLayout(PageSequenceLayoutManager.java:138) at org.apache.fop.area.AreaTreeHandler.endPageSequence(AreaTreeHandler.java:267) at org.apache.fop.fo.pagination.PageSequence.endOfNode(PageSequence.java:130) at org.apache.fop.fo.FOTreeBuilder$MainFOHandler.endElement(FOTreeBuilder.java:360) at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:190) at org.apache.xalan.transformer.TransformerIdentityImpl.endElement(TransformerIdentityImpl.java:1101) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.xinclude.XIncludeHandler.endElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) at
[jira] [Updated] (FOP-2496) fop2.0 crashes if docbook note is last inside a listitem or a step. No bug in fop1.1
[ https://issues.apache.org/jira/browse/FOP-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lennart Johansson updated FOP-2496: --- Attachment: (was: note-problem-fop2.0-step-workaround-patched.fo) fop2.0 crashes if docbook note is last inside a listitem or a step. No bug in fop1.1 -- Key: FOP-2496 URL: https://issues.apache.org/jira/browse/FOP-2496 Project: FOP Issue Type: Bug Components: renderer/pdf Affects Versions: 2.0 Reporter: Lennart Johansson Attachments: note-problem-fop2.0-listitem-crash.fo, note-problem-fop2.0-listitem-workaround-patched.fo fop2.0 crashes if docbook note is last inside a listitem or a step. No bug in fop1.1 This works in fop1.1 and it is good docbook syntax and should not be a problem. A workaround, that also shows the problem, is to insert an empty para between /note and /listitem), or directly in the .fo file, insert an extra fo:block/fo.block. We are now forced to use this workaround in the building scripts - not nice! Appended: - note-problem-fop2.0-listitem-crash.fo = Small example .fo file with a note last in a listitem - note-problem-fop2.0-listitem-workaround-patched.fo = Workaround-patched .fo file (listitem) - note-problem-fop2.0-step-crash.fo = Small example .fo file with a note last in a step - note-problem-fop2.0-step-workaround-patched.fo = Workaround-patched .fo file (step) The fop CRASH log is below: INFO: Rendered page #1. INFO: Rendered page #2. Jul 8, 2015 8:18:06 PM org.apache.fop.cli.Main startFOP SEVERE: Exception java.lang.NullPointerException at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:288) at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:115) at org.apache.fop.cli.Main.startFOP(Main.java:186) at org.apache.fop.cli.Main.main(Main.java:217) Caused by: java.lang.NullPointerException at org.apache.fop.layoutmgr.list.ListItemLayoutManager.getCombinedKnuthElementsForListItem(ListItemLayoutManager.java:405) at org.apache.fop.layoutmgr.list.ListItemLayoutManager.getNextKnuthElements(ListItemLayoutManager.java:326) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:239) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextChildElements(BlockStackingLayoutManager.java:498) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289) at org.apache.fop.layoutmgr.list.ListBlockLayoutManager.getNextKnuthElements(ListBlockLayoutManager.java:103) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:239) at org.apache.fop.layoutmgr.FlowLayoutManager.getNextChildElements(FlowLayoutManager.java:223) at org.apache.fop.layoutmgr.FlowLayoutManager.addChildElements(FlowLayoutManager.java:147) at org.apache.fop.layoutmgr.FlowLayoutManager.getNextKnuthElements(FlowLayoutManager.java:116) at org.apache.fop.layoutmgr.FlowLayoutManager.getNextKnuthElements(FlowLayoutManager.java:69) at org.apache.fop.layoutmgr.PageBreaker.getNextKnuthElements(PageBreaker.java:252) at org.apache.fop.layoutmgr.AbstractBreaker.getNextBlockList(AbstractBreaker.java:643) at org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:178) at org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:158) at org.apache.fop.layoutmgr.AbstractBreaker.doLayout(AbstractBreaker.java:384) at org.apache.fop.layoutmgr.PageBreaker.doLayout(PageBreaker.java:112) at org.apache.fop.layoutmgr.PageSequenceLayoutManager.activateLayout(PageSequenceLayoutManager.java:138) at org.apache.fop.area.AreaTreeHandler.endPageSequence(AreaTreeHandler.java:267) at org.apache.fop.fo.pagination.PageSequence.endOfNode(PageSequence.java:130) at org.apache.fop.fo.FOTreeBuilder$MainFOHandler.endElement(FOTreeBuilder.java:360) at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:190) at org.apache.xalan.transformer.TransformerIdentityImpl.endElement(TransformerIdentityImpl.java:1101) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.xinclude.XIncludeHandler.endElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at
[jira] [Created] (FOP-2496) fop2.0 crashes if docbook note is last inside a listitem or a step. No bug in fop1.1
Lennart Johansson created FOP-2496: -- Summary: fop2.0 crashes if docbook note is last inside a listitem or a step. No bug in fop1.1 Key: FOP-2496 URL: https://issues.apache.org/jira/browse/FOP-2496 Project: FOP Issue Type: Bug Components: renderer/pdf Affects Versions: 2.0 Reporter: Lennart Johansson fop2.0 crashes if docbook note is last inside a listitem or a step. No bug in fop1.1 This works in fop1.1 and it is good docbook syntax and should not be a problem. A workaround, that also shows the problem, is to insert an empty para between /note and /listitem), or directly in the .fo file, insert an extra fo:block/fo.block. We are now forced to use this workaround in the building scripts - not nice! Appended: - note-problem-fop2.0-listitem-crash.fo = Small example .fo file with a note last in a listitem - note-problem-fop2.0-listitem-workaround-patched.fo = Workaround-patched .fo file (listitem) - note-problem-fop2.0-step-crash.fo = Small example .fo file with a note last in a step - note-problem-fop2.0-step-workaround-patched.fo = Workaround-patched .fo file (step) The fop CRASH log is below: INFO: Rendered page #1. INFO: Rendered page #2. Jul 8, 2015 8:18:06 PM org.apache.fop.cli.Main startFOP SEVERE: Exception java.lang.NullPointerException at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:288) at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:115) at org.apache.fop.cli.Main.startFOP(Main.java:186) at org.apache.fop.cli.Main.main(Main.java:217) Caused by: java.lang.NullPointerException at org.apache.fop.layoutmgr.list.ListItemLayoutManager.getCombinedKnuthElementsForListItem(ListItemLayoutManager.java:405) at org.apache.fop.layoutmgr.list.ListItemLayoutManager.getNextKnuthElements(ListItemLayoutManager.java:326) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:239) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextChildElements(BlockStackingLayoutManager.java:498) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289) at org.apache.fop.layoutmgr.list.ListBlockLayoutManager.getNextKnuthElements(ListBlockLayoutManager.java:103) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:239) at org.apache.fop.layoutmgr.FlowLayoutManager.getNextChildElements(FlowLayoutManager.java:223) at org.apache.fop.layoutmgr.FlowLayoutManager.addChildElements(FlowLayoutManager.java:147) at org.apache.fop.layoutmgr.FlowLayoutManager.getNextKnuthElements(FlowLayoutManager.java:116) at org.apache.fop.layoutmgr.FlowLayoutManager.getNextKnuthElements(FlowLayoutManager.java:69) at org.apache.fop.layoutmgr.PageBreaker.getNextKnuthElements(PageBreaker.java:252) at org.apache.fop.layoutmgr.AbstractBreaker.getNextBlockList(AbstractBreaker.java:643) at org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:178) at org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:158) at org.apache.fop.layoutmgr.AbstractBreaker.doLayout(AbstractBreaker.java:384) at org.apache.fop.layoutmgr.PageBreaker.doLayout(PageBreaker.java:112) at org.apache.fop.layoutmgr.PageSequenceLayoutManager.activateLayout(PageSequenceLayoutManager.java:138) at org.apache.fop.area.AreaTreeHandler.endPageSequence(AreaTreeHandler.java:267) at org.apache.fop.fo.pagination.PageSequence.endOfNode(PageSequence.java:130) at org.apache.fop.fo.FOTreeBuilder$MainFOHandler.endElement(FOTreeBuilder.java:360) at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:190) at org.apache.xalan.transformer.TransformerIdentityImpl.endElement(TransformerIdentityImpl.java:1101) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.xinclude.XIncludeHandler.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.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at
[jira] [Updated] (FOP-2496) fop2.0 crashes if docbook note is last inside a listitem or a step. No bug in fop1.1
[ https://issues.apache.org/jira/browse/FOP-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lennart Johansson updated FOP-2496: --- Attachment: note-problem-fop2.0-step-workaround-patched.fo note-problem-fop2.0-step-crash.fo note-problem-fop2.0-listitem-workaround-patched.fo note-problem-fop2.0-listitem-crash.fo fop2.0 crashes if docbook note is last inside a listitem or a step. No bug in fop1.1 -- Key: FOP-2496 URL: https://issues.apache.org/jira/browse/FOP-2496 Project: FOP Issue Type: Bug Components: renderer/pdf Affects Versions: 2.0 Reporter: Lennart Johansson Attachments: note-problem-fop2.0-listitem-crash.fo, note-problem-fop2.0-listitem-workaround-patched.fo, note-problem-fop2.0-step-crash.fo, note-problem-fop2.0-step-workaround-patched.fo fop2.0 crashes if docbook note is last inside a listitem or a step. No bug in fop1.1 This works in fop1.1 and it is good docbook syntax and should not be a problem. A workaround, that also shows the problem, is to insert an empty para between /note and /listitem), or directly in the .fo file, insert an extra fo:block/fo.block. We are now forced to use this workaround in the building scripts - not nice! Appended: - note-problem-fop2.0-listitem-crash.fo = Small example .fo file with a note last in a listitem - note-problem-fop2.0-listitem-workaround-patched.fo = Workaround-patched .fo file (listitem) - note-problem-fop2.0-step-crash.fo = Small example .fo file with a note last in a step - note-problem-fop2.0-step-workaround-patched.fo = Workaround-patched .fo file (step) The fop CRASH log is below: INFO: Rendered page #1. INFO: Rendered page #2. Jul 8, 2015 8:18:06 PM org.apache.fop.cli.Main startFOP SEVERE: Exception java.lang.NullPointerException at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:288) at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:115) at org.apache.fop.cli.Main.startFOP(Main.java:186) at org.apache.fop.cli.Main.main(Main.java:217) Caused by: java.lang.NullPointerException at org.apache.fop.layoutmgr.list.ListItemLayoutManager.getCombinedKnuthElementsForListItem(ListItemLayoutManager.java:405) at org.apache.fop.layoutmgr.list.ListItemLayoutManager.getNextKnuthElements(ListItemLayoutManager.java:326) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:239) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextChildElements(BlockStackingLayoutManager.java:498) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289) at org.apache.fop.layoutmgr.list.ListBlockLayoutManager.getNextKnuthElements(ListBlockLayoutManager.java:103) at org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:239) at org.apache.fop.layoutmgr.FlowLayoutManager.getNextChildElements(FlowLayoutManager.java:223) at org.apache.fop.layoutmgr.FlowLayoutManager.addChildElements(FlowLayoutManager.java:147) at org.apache.fop.layoutmgr.FlowLayoutManager.getNextKnuthElements(FlowLayoutManager.java:116) at org.apache.fop.layoutmgr.FlowLayoutManager.getNextKnuthElements(FlowLayoutManager.java:69) at org.apache.fop.layoutmgr.PageBreaker.getNextKnuthElements(PageBreaker.java:252) at org.apache.fop.layoutmgr.AbstractBreaker.getNextBlockList(AbstractBreaker.java:643) at org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:178) at org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:158) at org.apache.fop.layoutmgr.AbstractBreaker.doLayout(AbstractBreaker.java:384) at org.apache.fop.layoutmgr.PageBreaker.doLayout(PageBreaker.java:112) at org.apache.fop.layoutmgr.PageSequenceLayoutManager.activateLayout(PageSequenceLayoutManager.java:138) at org.apache.fop.area.AreaTreeHandler.endPageSequence(AreaTreeHandler.java:267) at org.apache.fop.fo.pagination.PageSequence.endOfNode(PageSequence.java:130) at org.apache.fop.fo.FOTreeBuilder$MainFOHandler.endElement(FOTreeBuilder.java:360) at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:190) at org.apache.xalan.transformer.TransformerIdentityImpl.endElement(TransformerIdentityImpl.java:1101) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.xinclude.XIncludeHandler.endElement(Unknown Source) at
[jira] [Commented] (FOP-2044) [PATCH] Hyphenation of Uppercase Words, Combined with Underlines
[ https://issues.apache.org/jira/browse/FOP-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13875614#comment-13875614 ] Lennart Johansson commented on FOP-2044: Highly appreciate the actions. Tips: Personally I would vote for an extra hardcoded break as a last effort if nothing else helps, to ensure that text in a table cell NEVER overflows into another cell, destroying other texts, due to hyphenation problems. Actually I have also seen that XEP tries another type of last-effort solution, to decrease the space-between-characters on the troublesome line causing horizontally dense text, rather than overflowing a table-cell. If the last effort is successful, use an INFO: instead of a WARNING message. Still it might be OK for text-that-could-not-be-broken to slightly overflow the text area into the page margin of a PDF-page (at least as long as it does not reach outside the page edge and disappears) - it is only in table cells that an overflow can destroys other text. However, maybe it is difficult for the FOP hyphenation code to know, if it is in a table cell or somewhere else, especially if if needs to consider also right-to-left text direction or similar? Best Regards / Lennart [PATCH] Hyphenation of Uppercase Words, Combined with Underlines Key: FOP-2044 URL: https://issues.apache.org/jira/browse/FOP-2044 Project: Fop Issue Type: Improvement Components: general Affects Versions: 1.0 Environment: Operating System: All Platform: All Reporter: Thomas Schraitle Assignee: Robert Meyer Fix For: trunk Attachments: fop-trunk-jan02-2014-test-fop-2044.fo, fop-trunk-jan02-2014.log, fop-trunk-jan92-2914-test-fop-2044.pdf, output.pdf, patch.diff, patch2.diff, uppercase-hyphen.fo, uppercase-hyphen.pdf Consider the attached FO file which combines words of lowercase and uppercase letters. As it is expected, the word expected is hyphenated correctly (example 2). Also the uppercase SUCCESS. Even combined with underlines before and after the word (see example 4 and 5). However, if there is another word (like OCF_SUCCESS) the word isn't hyphenated at all anymore. I don't know if this is an expected behaviour or an issue in the hyphenation patterns. Interestingly, XEP from RenderX hyphenates it as OCF_SUC-CESS. As far as I know, they use also the TeX hyphenation patterns as FOP. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (FOP-2044) [PATCH] Hyphenation of Uppercase Words, Combined with Underlines
[ https://issues.apache.org/jira/browse/FOP-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lennart Johansson updated FOP-2044: --- Attachment: fop-trunk-jan92-2914-test-fop-2044.pdf fop-trunk-jan02-2014.log fop-trunk-jan02-2014-test-fop-2044.fo I have attached the three files fop-trunk-jan02-2014-*** The .fo file, the .pdf file, and a log file showing the fop WARNING messages. There are 11 examples of words that fop can not hyphenate - the .fo files has been created from a test header file. A special program creates the docbook XML file and XML/XSLT libx* 2.7.8/1.1.26 creates the FO file, finally FOP creates the PDF. Hoping this can help you to test and find out what can be done to allow FOP to handle these somehow without overflowing. Best of Luck / Lennart [PATCH] Hyphenation of Uppercase Words, Combined with Underlines Key: FOP-2044 URL: https://issues.apache.org/jira/browse/FOP-2044 Project: Fop Issue Type: Improvement Components: general Affects Versions: 1.0 Environment: Operating System: All Platform: All Reporter: Thomas Schraitle Assignee: Robert Meyer Fix For: trunk Attachments: fop-trunk-jan02-2014-test-fop-2044.fo, fop-trunk-jan02-2014.log, fop-trunk-jan92-2914-test-fop-2044.pdf, output.pdf, patch.diff, patch2.diff, uppercase-hyphen.fo, uppercase-hyphen.pdf Consider the attached FO file which combines words of lowercase and uppercase letters. As it is expected, the word expected is hyphenated correctly (example 2). Also the uppercase SUCCESS. Even combined with underlines before and after the word (see example 4 and 5). However, if there is another word (like OCF_SUCCESS) the word isn't hyphenated at all anymore. I don't know if this is an expected behaviour or an issue in the hyphenation patterns. Interestingly, XEP from RenderX hyphenates it as OCF_SUC-CESS. As far as I know, they use also the TeX hyphenation patterns as FOP. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Comment Edited] (FOP-2044) [PATCH] Hyphenation of Uppercase Words, Combined with Underlines
[ https://issues.apache.org/jira/browse/FOP-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13874997#comment-13874997 ] Lennart Johansson edited comment on FOP-2044 at 1/17/14 5:46 PM: - I have attached the three files fop-trunk-jan02-2014-*** The .fo file, the .pdf file, and a log file showing the fop WARNING messages. There are 11 examples of words that fop can not hyphenate - the .fo files has been created from a test header file. A special program creates the docbook XML file and XML/XSLT libx* 2.7.8/1.1.26 creates the FO file, finally FOP creates the PDF. I am not using any other fonts than are default in the fop trunk. fop is run in a Linux 2.6.x server. Hoping this can help you to test and find out what can be done to allow FOP to handle these somehow without overflowing. Best of Luck / Lennart was (Author: ljo): I have attached the three files fop-trunk-jan02-2014-*** The .fo file, the .pdf file, and a log file showing the fop WARNING messages. There are 11 examples of words that fop can not hyphenate - the .fo files has been created from a test header file. A special program creates the docbook XML file and XML/XSLT libx* 2.7.8/1.1.26 creates the FO file, finally FOP creates the PDF. Hoping this can help you to test and find out what can be done to allow FOP to handle these somehow without overflowing. Best of Luck / Lennart [PATCH] Hyphenation of Uppercase Words, Combined with Underlines Key: FOP-2044 URL: https://issues.apache.org/jira/browse/FOP-2044 Project: Fop Issue Type: Improvement Components: general Affects Versions: 1.0 Environment: Operating System: All Platform: All Reporter: Thomas Schraitle Assignee: Robert Meyer Fix For: trunk Attachments: fop-trunk-jan02-2014-test-fop-2044.fo, fop-trunk-jan02-2014.log, fop-trunk-jan92-2914-test-fop-2044.pdf, output.pdf, patch.diff, patch2.diff, uppercase-hyphen.fo, uppercase-hyphen.pdf Consider the attached FO file which combines words of lowercase and uppercase letters. As it is expected, the word expected is hyphenated correctly (example 2). Also the uppercase SUCCESS. Even combined with underlines before and after the word (see example 4 and 5). However, if there is another word (like OCF_SUCCESS) the word isn't hyphenated at all anymore. I don't know if this is an expected behaviour or an issue in the hyphenation patterns. Interestingly, XEP from RenderX hyphenates it as OCF_SUC-CESS. As far as I know, they use also the TeX hyphenation patterns as FOP. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (FOP-2044) [PATCH] Hyphenation of Uppercase Words, Combined with Underlines
[ https://issues.apache.org/jira/browse/FOP-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13873498#comment-13873498 ] Lennart Johansson commented on FOP-2044: I am very greatful for the updates which have solved most hyphenation problems. It is amazing how good FOP works. But I found still 11 long words that fop-trunk Jan 1, 2014 can not handle and which we have trouble with, due to autogenerated XML, where it is difficult to use workarounds. FOP issues WARNING: messages for those listed below and there are overflows in PDF. QUEST: Is it possible to do something about these, with the help of our test results, even though this issue FOP-2044 has been set to resolved? Most of these seem to be of the same nature as what is discussed above in the 27/Jan/13 00:36 comment. There are only one or two characters overflow or in some cases less than a character. This is fatal when overflowing the text in the next column in a table, even though a similar small overflow is OK if it only overflows into the right page edge. A few others seem different. The first remaining problem is similar to what is described above, where there are very few characters overflowing, just one or two characters or in some cases even less that a full character. -1- ip6_ctlun.ip6_un1.ip6_un1_flowoverflows ow -2- ip6_ctlun.ip6_un1.ip6_un1_plenoverflows en -3- ip6_ctlun.ip6_un1.ip6_un1_nxt overflows t Comment: ip6_ctlun.ip6_un1.ip6_un1_hlim is CORRECTLY broken at _h- lim -4- EPM_REQUEST_TO_CLEAR_NONEXISTING_BP overflows tailing P even though it is hyphenated EPM_RE- much too early -5- OSE_BSP_EKRN_EVT_MISALIGNED_MSG_QUEUE gives WARNING but is very close to the column right edge, very slightly overflowing. Should be hyphenated somewhere -6- PROFILING_PC_STATUS_NO_COUNTER_AVAILABLE_FOR_TYPE overflows even though it breaks in one place PROFILING_PC_S- Should either be hyphenated later or twice, because the remaining part is very slightly too long -7- FOP breaks too early: SCTP_PARTIAL_DELIVERY_EVENT becomes SCT- followed by P_PARTIAL_DELIVERY_EVENT which overflows into next column Comment: A quick-test shows that in case of manually created XML, a soft-hyphen shy can solve SCTP_PARTIAL_DELIVERY_EVENT. -8- LINX_CM_ETH_EDESTROY_IN_PROGRESS overflows and also has a hyphenation break far out inside the overflow area, causing it to be displayed as follows. The ROY_IN_PRO- is overflowing the right column text with unreadable result. This table column is narrower than in the HV_ examples below: LINX_CM_ETH_EDESTROY_IN_PRO- (where ROY_IN_PRO- is overflow) GRESS The second problem is the following three words, which I do not understand why they are not hyphenated at all? -9- HV_GUEST_RESULT_EGUEST_NOT_INITIALIZED overflows NITIALIZED -10- HV_GUEST_TRANSITION_GUEST_USER_MODEoverflows ER_MODE -11- HV_GUEST_TRANSITION_GUEST_SU_MODE overflows MODE Comment: Much longer words are correctly hyphenated in same column, e.g. HV_GUEST_RESULT_EGUEST_AL- READY_INITIALIZED) A third problem in MINOR, because we can use WORKAROUND with soft-hyphen, because it only appears in a book where we manually create the XML files: -12- MINOR: FOP can not break numerical IPv6 addresses with only digits, causing overflow into next column. ff01:::::::0101 overflows :0101 INFO: In this case XEP uses denser font to squeeze it in if it can, or break it if needed! WORKAROUND - we make more space or use zero-width-space #8203 Note that soft-hyphen does not work here! Best Regards and Good Luck / Lennart [PATCH] Hyphenation of Uppercase Words, Combined with Underlines Key: FOP-2044 URL: https://issues.apache.org/jira/browse/FOP-2044 Project: Fop Issue Type: Improvement Components: general Affects Versions: 1.0 Environment: Operating System: All Platform: All Reporter: Thomas Schraitle Assignee: Robert Meyer Fix For: trunk Attachments: output.pdf, patch.diff, patch2.diff, uppercase-hyphen.fo, uppercase-hyphen.pdf Consider the attached FO file which combines words of lowercase and uppercase letters. As it is expected, the word expected is hyphenated correctly (example 2). Also the uppercase SUCCESS. Even combined with underlines before and after the word (see example 4 and 5). However, if there is another word (like OCF_SUCCESS) the word isn't hyphenated at all anymore. I don't know if this is an expected behaviour or an issue in the hyphenation patterns. Interestingly, XEP from RenderX hyphenates it
