[jira] [Commented] (FOP-2511) Null pointer exception when transforming to PDF with FOP 2.0

2015-08-12 Thread Johan Persson (JIRA)

[ 
https://issues.apache.org/jira/browse/FOP-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14694333#comment-14694333
 ] 

Johan Persson commented on FOP-2511:


I tried to find one of the nightly builds but the page seems to be missing the 
builds. 

https://ci.apache.org/projects/xmlgraphics/fop/snapshots/

The table headers seems to be there but no actual tar-balls to download.

Any ides where I can find a nightly build? (I guess I can try to put together 
the necessary files directly from the SVN-repo but it would surely save some 
time to have a pre-built-binary)

 Null pointer exception when transforming to PDF with FOP 2.0
 

 Key: FOP-2511
 URL: https://issues.apache.org/jira/browse/FOP-2511
 Project: FOP
  Issue Type: Bug
Affects Versions: 2.0
 Environment: OS X 10.9.5 . Tested both with JDK 1.7.0_45 and JDK 1.6.0
Reporter: Johan Persson
Priority: Critical
  Labels: fop, nullpointer

 When trying to transform to PDF I'm experiencing a NULL pointer exception. 
 See below. The same fo-file used as source works without problem with FOP 1.1
 The source for the fo-file is a set of DocBook 5 sources transformed using 
 XSLTproc. The fo-file that produces the crash can be found at my Google-Drive 
 at:
 https://drive.google.com/folderview?id=0BypRwfn2A3s6fnN6NW1PU1BEd3JiTzdyYlg0NjZxRTNFbFhUM21UMmw1ZUNjRGlYb1c2T28usp=sharing
 {{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.BlockLayoutManager.getNextChildElements(BlockLayoutManager.java:141)
   at 
 org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289)
   at 
 org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:113)
   at 
 org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:105)
   at 
 org.apache.fop.layoutmgr.BlockLayoutManager.getNextChildElements(BlockLayoutManager.java:141)
   at 
 org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289)
   at 
 org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:113)
   at 
 org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:105)
   at 
 org.apache.fop.layoutmgr.BlockLayoutManager.getNextChildElements(BlockLayoutManager.java:141)
   at 
 org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289)
   at 
 org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:113)
   at 
 org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:105)
   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 

[jira] [Closed] (FOP-2492) FOP-2.0 error when processing PDF with SVG image

2015-08-12 Thread Aleksei Badyaev (JIRA)

 [ 
https://issues.apache.org/jira/browse/FOP-2492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksei Badyaev closed FOP-2492.

   Resolution: Not A Problem
Fix Version/s: 2.0

I remove metrics attributes in my fop.xconf file - and my doc processed 
correctly!
Thank you, Thanasis!

 FOP-2.0 error when processing PDF with SVG image
 

 Key: FOP-2492
 URL: https://issues.apache.org/jira/browse/FOP-2492
 Project: FOP
  Issue Type: New Feature
  Components: image/svg
Affects Versions: 2.0
 Environment: Linux Gentoo x86
Reporter: Aleksei Badyaev
Priority: Blocker
 Fix For: 2.0

 Attachments: fop.xconf, object-model.svg, test.fo, test.xml


 I try process my small FO document with SVG image to PDF, and i got following 
 output:
 noformat
 июн 29, 2015 12:02:46 AM org.apache.fop.apps.FopConfParser configure
 INFO: Default page-height set to: 297mm
 июн 29, 2015 12:02:47 AM org.apache.fop.apps.FopConfParser configure
 INFO: Default page-width set to: 210mm
 июн 29, 2015 12:02:55 AM org.apache.fop.events.LoggingEventListener 
 processEvent
 WARNING: Font Symbol,normal,700 not found. Substituting with 
 Symbol,normal,400.
 июн 29, 2015 12:02:58 AM org.apache.fop.events.LoggingEventListener 
 processEvent
 SEVERE: SVG graphic could not be rendered. Reason: 
 java.lang.NullPointerException
 java.lang.NullPointerException
   at 
 org.apache.fop.fonts.MultiByteFont.getBoundingBox(MultiByteFont.java:210)
   at org.apache.fop.fonts.LazyFont.getBoundingBox(LazyFont.java:301)
   at 
 org.apache.fop.svg.font.FOPGVTGlyphVector.buildBoundingBoxes(FOPGVTGlyphVector.java:428)
   at 
 org.apache.fop.svg.font.FOPGVTGlyphVector.getBoundingBoxes(FOPGVTGlyphVector.java:420)
   at 
 org.apache.fop.svg.font.FOPGVTGlyphVector.getGlyphMetrics(FOPGVTGlyphVector.java:290)
   at org.apache.batik.bridge.GlyphLayout.doExplicitGlyphLayout(Unknown 
 Source)
   at org.apache.batik.bridge.GlyphLayout.adjustTextSpacing(Unknown Source)
   at org.apache.batik.bridge.GlyphLayout.getAdvance2D(Unknown Source)
   at org.apache.batik.bridge.StrokingTextPainter.getTextChunk(Unknown 
 Source)
   at org.apache.batik.bridge.StrokingTextPainter.computeTextRuns(Unknown 
 Source)
   at 
 org.apache.fop.svg.NativeTextPainter.computeTextRuns(NativeTextPainter.java:223)
   at org.apache.batik.bridge.StrokingTextPainter.getTextRuns(Unknown 
 Source)
   at org.apache.batik.bridge.StrokingTextPainter.getBounds2D(Unknown 
 Source)
   at org.apache.batik.bridge.TextNode.getPrimitiveBounds(Unknown Source)
   at 
 org.apache.batik.gvt.AbstractGraphicsNode.getTransformedPrimitiveBounds(Unknown
  Source)
   at 
 org.apache.batik.gvt.AbstractGraphicsNode.getTransformedBounds(Unknown Source)
   at 
 org.apache.batik.gvt.CompositeGraphicsNode.getPrimitiveBounds(Unknown Source)
   at 
 org.apache.batik.gvt.CompositeGraphicsNode.getTransformedPrimitiveBounds(Unknown
  Source)
   at 
 org.apache.batik.gvt.AbstractGraphicsNode.getTransformedBounds(Unknown Source)
   at 
 org.apache.batik.gvt.CompositeGraphicsNode.getPrimitiveBounds(Unknown Source)
   at 
 org.apache.batik.gvt.CompositeGraphicsNode.getTransformedPrimitiveBounds(Unknown
  Source)
   at 
 org.apache.batik.gvt.AbstractGraphicsNode.getTransformedBounds(Unknown Source)
   at 
 org.apache.batik.gvt.CompositeGraphicsNode.getPrimitiveBounds(Unknown Source)
   at org.apache.batik.gvt.AbstractGraphicsNode.getBounds(Unknown Source)
   at org.apache.batik.gvt.AbstractGraphicsNode.paint(Unknown Source)
   at 
 org.apache.fop.render.pdf.PDFImageHandlerSVG.handleImage(PDFImageHandlerSVG.java:207)
   at 
 org.apache.fop.render.intermediate.AbstractIFPainter.drawImage(AbstractIFPainter.java:249)
   at 
 org.apache.fop.render.intermediate.AbstractIFPainter.drawImage(AbstractIFPainter.java:205)
   at 
 org.apache.fop.render.intermediate.AbstractIFPainter.drawImageUsingImageHandler(AbstractIFPainter.java:170)
   at 
 org.apache.fop.render.intermediate.AbstractIFPainter.drawImageUsingURI(AbstractIFPainter.java:292)
   at org.apache.fop.render.pdf.PDFPainter.drawImage(PDFPainter.java:173)
   at 
 org.apache.fop.render.intermediate.IFRenderer.drawImage(IFRenderer.java:1295)
   at 
 org.apache.fop.render.intermediate.IFRenderer.renderImage(IFRenderer.java:1282)
   at 
 org.apache.fop.render.AbstractRenderer.renderInlineViewport(AbstractRenderer.java:858)
   at 
 org.apache.fop.render.AbstractPathOrientedRenderer.renderInlineViewport(AbstractPathOrientedRenderer.java:832)
   at 
 org.apache.fop.render.intermediate.IFRenderer.renderInlineViewport(IFRenderer.java:863)
   at 
 org.apache.fop.render.AbstractRenderer.renderInlineArea(AbstractRenderer.java:715)
  

[jira] [Commented] (FOP-2511) Null pointer exception when transforming to PDF with FOP 2.0

2015-08-12 Thread Thanasis Giannimaras (JIRA)

[ 
https://issues.apache.org/jira/browse/FOP-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14693061#comment-14693061
 ] 

Thanasis Giannimaras commented on FOP-2511:
---

Have you tried using trunk? I think this issue is a duplicate of 
https://issues.apache.org/jira/browse/FOP-2461 which was patched recently by 
Andreas L. Delmelle on trunk.

 Null pointer exception when transforming to PDF with FOP 2.0
 

 Key: FOP-2511
 URL: https://issues.apache.org/jira/browse/FOP-2511
 Project: FOP
  Issue Type: Bug
Affects Versions: 2.0
 Environment: OS X 10.9.5 . Tested both with JDK 1.7.0_45 and JDK 1.6.0
Reporter: Johan Persson
Priority: Critical
  Labels: fop, nullpointer

 When trying to transform to PDF I'm experiencing a NULL pointer exception. 
 See below. The same fo-file used as source works without problem with FOP 1.1
 The source for the fo-file is a set of DocBook 5 sources transformed using 
 XSLTproc. The fo-file that produces the crash can be found at my Google-Drive 
 at:
 https://drive.google.com/folderview?id=0BypRwfn2A3s6fnN6NW1PU1BEd3JiTzdyYlg0NjZxRTNFbFhUM21UMmw1ZUNjRGlYb1c2T28usp=sharing
 {{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.BlockLayoutManager.getNextChildElements(BlockLayoutManager.java:141)
   at 
 org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289)
   at 
 org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:113)
   at 
 org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:105)
   at 
 org.apache.fop.layoutmgr.BlockLayoutManager.getNextChildElements(BlockLayoutManager.java:141)
   at 
 org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289)
   at 
 org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:113)
   at 
 org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:105)
   at 
 org.apache.fop.layoutmgr.BlockLayoutManager.getNextChildElements(BlockLayoutManager.java:141)
   at 
 org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289)
   at 
 org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:113)
   at 
 org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:105)
   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 
 

[jira] [Commented] (FOP-1572) [PATCH] Internal PDF links from included SVG graphics

2015-08-12 Thread Olof Wolgast (JIRA)

[ 
https://issues.apache.org/jira/browse/FOP-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14693101#comment-14693101
 ] 

Olof Wolgast commented on FOP-1572:
---

Anything that can be done to have this feature implemented? It would be of 
great value to me. I'm willing to help but I'm not familiar with internal pdf 
design nor the source code for FOP so it would probably be very inefficient and 
yield with a bad solution if I tried to implement it. Perhaps I could help with 
testing?

 [PATCH] Internal PDF links from included SVG graphics
 -

 Key: FOP-1572
 URL: https://issues.apache.org/jira/browse/FOP-1572
 Project: FOP
  Issue Type: Improvement
  Components: renderer/pdf
Affects Versions: trunk
 Environment: Operating System: All
 Platform: All
Reporter: Stefan Bund
 Attachments: bugzilla45759-svg-linkback-counterproposal.patch, 
 fop-pdf-internal-link_r693020.patch.gz, svg-linking-back.fo, 
 svg_textexport__test_01.svg


 This patch adds support for internal PDF links to included SVG graphics. A 
 link with a target '#id' will be resolved to point to the object with the 
 given target id in the PDF.
 Limitations/shortcomings at the moment are:
 * Implemented at the renderer stage not the area stage and such only supported
 for PDF output
 * Resolving the links could certainly be optimized
 * The active area will always be rectangular (object bounding box)
 * I have only a few days of experience with Apahche-FOP and such there will 
 probably some other shortcomings or missunderstandings.
 See the mailing list thread  'Re: Links in SVGs included into PDFs' started 
 at   Tue, 02 Sep 2008 11:02:48 +0200 on fop-users and continued later on 
 fop-dev.
 (Thread at gmane: http://thread.gmane.org/gmane.text.xml.fop.user/26778)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (FOP-2511) Null pointer exception when transforming to PDF with FOP 2.0

2015-08-12 Thread Johan Persson (JIRA)

[ 
https://issues.apache.org/jira/browse/FOP-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14693361#comment-14693361
 ] 

Johan Persson commented on FOP-2511:


I will pull down the trunk and try it out. Will take a day to two though.

 Null pointer exception when transforming to PDF with FOP 2.0
 

 Key: FOP-2511
 URL: https://issues.apache.org/jira/browse/FOP-2511
 Project: FOP
  Issue Type: Bug
Affects Versions: 2.0
 Environment: OS X 10.9.5 . Tested both with JDK 1.7.0_45 and JDK 1.6.0
Reporter: Johan Persson
Priority: Critical
  Labels: fop, nullpointer

 When trying to transform to PDF I'm experiencing a NULL pointer exception. 
 See below. The same fo-file used as source works without problem with FOP 1.1
 The source for the fo-file is a set of DocBook 5 sources transformed using 
 XSLTproc. The fo-file that produces the crash can be found at my Google-Drive 
 at:
 https://drive.google.com/folderview?id=0BypRwfn2A3s6fnN6NW1PU1BEd3JiTzdyYlg0NjZxRTNFbFhUM21UMmw1ZUNjRGlYb1c2T28usp=sharing
 {{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.BlockLayoutManager.getNextChildElements(BlockLayoutManager.java:141)
   at 
 org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289)
   at 
 org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:113)
   at 
 org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:105)
   at 
 org.apache.fop.layoutmgr.BlockLayoutManager.getNextChildElements(BlockLayoutManager.java:141)
   at 
 org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289)
   at 
 org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:113)
   at 
 org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:105)
   at 
 org.apache.fop.layoutmgr.BlockLayoutManager.getNextChildElements(BlockLayoutManager.java:141)
   at 
 org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289)
   at 
 org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:113)
   at 
 org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:105)
   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 
 

[jira] [Updated] (FOP-2510) [PATCH] Flow name infinite Loop

2015-08-12 Thread simon steiner (JIRA)

 [ 
https://issues.apache.org/jira/browse/FOP-2510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

simon steiner updated FOP-2510:
---
Summary: [PATCH] Flow name infinite Loop  (was: [PATCH] Infinite Loop)

 [PATCH] Flow name infinite Loop
 ---

 Key: FOP-2510
 URL: https://issues.apache.org/jira/browse/FOP-2510
 Project: FOP
  Issue Type: Bug
Reporter: Thanasis Giannimaras
 Attachments: svnLoop.patch, test.fo


 If the flow-name in the fo:flow element maps to a region body  belonging to a 
 simple-page-master not referenced by the fo:page-sequence element , then fop 
 enters an infinite loop.  Submitted patch that throws a ValidationException 
 when this happens.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (FOP-2510) [PATCH] Flow name infinite loop

2015-08-12 Thread simon steiner (JIRA)

 [ 
https://issues.apache.org/jira/browse/FOP-2510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

simon steiner updated FOP-2510:
---
Summary: [PATCH] Flow name infinite loop  (was: [PATCH] Flow name infinite 
Loop)

 [PATCH] Flow name infinite loop
 ---

 Key: FOP-2510
 URL: https://issues.apache.org/jira/browse/FOP-2510
 Project: FOP
  Issue Type: Bug
Reporter: Thanasis Giannimaras
 Attachments: svnLoop.patch, test.fo


 If the flow-name in the fo:flow element maps to a region body  belonging to a 
 simple-page-master not referenced by the fo:page-sequence element , then fop 
 enters an infinite loop.  Submitted patch that throws a ValidationException 
 when this happens.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (FOP-2491) [PATCH] Adobe Reader error with OTF subset PDF

2015-08-12 Thread simon steiner (JIRA)

 [ 
https://issues.apache.org/jira/browse/FOP-2491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

simon steiner updated FOP-2491:
---
Summary: [PATCH] Adobe Reader error with OTF subset PDF  (was: [PATCH] FOP 
2.0 cannot support open-type font)

 [PATCH] Adobe Reader error with OTF subset PDF
 --

 Key: FOP-2491
 URL: https://issues.apache.org/jira/browse/FOP-2491
 Project: FOP
  Issue Type: Bug
Affects Versions: 2.0
 Environment: FOP: 2.0
 Open Font: Noto-Sans Cjk 
 (https://noto-website.storage.googleapis.com/pkgs/NotoSansCJKTC-hinted.zip)
Reporter: Leo Yang
 Attachments: after.pdf, before.pdf, fop.xconf, svnSubset.patch, 
 test.fo


 Symptom: Based on FOP 2.0 release, the open-type font can be embedded into 
 PDF document, however, based on the testing with FOP 2.0, the 
 google-noto-sans-Cjk font cannot be embedded into PDF document.
 How to repeat:
  1. Get FOP 2.0 library.
  2. Get Google-Noto-Sans from 
 https://noto-website.storage.googleapis.com/pkgs/NotoSansCJKTC-hinted.zip.
  3. Set the fop.xconf as following:
  font embed-url=file:///C:/Font/NotoSans.otf embedding-mode=subset
  font-triplet name=Noto Sans CJK TC Regular style=normal 
 weight=normal/
  /font
  4. Set the FOP as following:
  ?xml version=1.0 encoding=UTF-8?
  fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format;
  fo:layout-master-set
  fo:simple-page-master margin=2cm page-width=21.0cm page-height=29.7cm 
 master-name=A4-portrait
  fo:region-body/
  /fo:simple-page-master
  /fo:layout-master-set
  fo:page-sequence master-reference=A4-portrait
  fo:flow flow-name=xsl-region-body
  fo:block font-family=Noto Sans CJK TC RegularHello Noto-OTF!/fo:block
  /fo:flow
  /fo:page-sequence
  /fo:root
  5. Generate the PDF, there is no error reported.
  6. Open the PDF file in Acro-Reader, it will report the cannot extract the 
 embedded font error.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (FOP-2491) [PATCH] Adobe Reader error with OTF subset PDF

2015-08-12 Thread simon steiner (JIRA)

[ 
https://issues.apache.org/jira/browse/FOP-2491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14693540#comment-14693540
 ] 

simon steiner commented on FOP-2491:


Added http://svn.apache.org/viewvc?view=revisionrevision=1695526

 [PATCH] Adobe Reader error with OTF subset PDF
 --

 Key: FOP-2491
 URL: https://issues.apache.org/jira/browse/FOP-2491
 Project: FOP
  Issue Type: Bug
Affects Versions: 2.0
 Environment: FOP: 2.0
 Open Font: Noto-Sans Cjk 
 (https://noto-website.storage.googleapis.com/pkgs/NotoSansCJKTC-hinted.zip)
Reporter: Leo Yang
 Attachments: after.pdf, before.pdf, fop.xconf, svnSubset.patch, 
 test.fo


 Symptom: Based on FOP 2.0 release, the open-type font can be embedded into 
 PDF document, however, based on the testing with FOP 2.0, the 
 google-noto-sans-Cjk font cannot be embedded into PDF document.
 How to repeat:
  1. Get FOP 2.0 library.
  2. Get Google-Noto-Sans from 
 https://noto-website.storage.googleapis.com/pkgs/NotoSansCJKTC-hinted.zip.
  3. Set the fop.xconf as following:
  font embed-url=file:///C:/Font/NotoSans.otf embedding-mode=subset
  font-triplet name=Noto Sans CJK TC Regular style=normal 
 weight=normal/
  /font
  4. Set the FOP as following:
  ?xml version=1.0 encoding=UTF-8?
  fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format;
  fo:layout-master-set
  fo:simple-page-master margin=2cm page-width=21.0cm page-height=29.7cm 
 master-name=A4-portrait
  fo:region-body/
  /fo:simple-page-master
  /fo:layout-master-set
  fo:page-sequence master-reference=A4-portrait
  fo:flow flow-name=xsl-region-body
  fo:block font-family=Noto Sans CJK TC RegularHello Noto-OTF!/fo:block
  /fo:flow
  /fo:page-sequence
  /fo:root
  5. Generate the PDF, there is no error reported.
  6. Open the PDF file in Acro-Reader, it will report the cannot extract the 
 embedded font error.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Closed] (FOP-2491) [PATCH] Adobe Reader error with OTF subset PDF

2015-08-12 Thread simon steiner (JIRA)

 [ 
https://issues.apache.org/jira/browse/FOP-2491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

simon steiner closed FOP-2491.
--
Resolution: Fixed

 [PATCH] Adobe Reader error with OTF subset PDF
 --

 Key: FOP-2491
 URL: https://issues.apache.org/jira/browse/FOP-2491
 Project: FOP
  Issue Type: Bug
Affects Versions: 2.0
 Environment: FOP: 2.0
 Open Font: Noto-Sans Cjk 
 (https://noto-website.storage.googleapis.com/pkgs/NotoSansCJKTC-hinted.zip)
Reporter: Leo Yang
 Attachments: after.pdf, before.pdf, fop.xconf, svnSubset.patch, 
 test.fo


 Symptom: Based on FOP 2.0 release, the open-type font can be embedded into 
 PDF document, however, based on the testing with FOP 2.0, the 
 google-noto-sans-Cjk font cannot be embedded into PDF document.
 How to repeat:
  1. Get FOP 2.0 library.
  2. Get Google-Noto-Sans from 
 https://noto-website.storage.googleapis.com/pkgs/NotoSansCJKTC-hinted.zip.
  3. Set the fop.xconf as following:
  font embed-url=file:///C:/Font/NotoSans.otf embedding-mode=subset
  font-triplet name=Noto Sans CJK TC Regular style=normal 
 weight=normal/
  /font
  4. Set the FOP as following:
  ?xml version=1.0 encoding=UTF-8?
  fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format;
  fo:layout-master-set
  fo:simple-page-master margin=2cm page-width=21.0cm page-height=29.7cm 
 master-name=A4-portrait
  fo:region-body/
  /fo:simple-page-master
  /fo:layout-master-set
  fo:page-sequence master-reference=A4-portrait
  fo:flow flow-name=xsl-region-body
  fo:block font-family=Noto Sans CJK TC RegularHello Noto-OTF!/fo:block
  /fo:flow
  /fo:page-sequence
  /fo:root
  5. Generate the PDF, there is no error reported.
  6. Open the PDF file in Acro-Reader, it will report the cannot extract the 
 embedded font error.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Closed] (FOP-2510) [PATCH] Flow name infinite loop

2015-08-12 Thread simon steiner (JIRA)

 [ 
https://issues.apache.org/jira/browse/FOP-2510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

simon steiner closed FOP-2510.
--
Resolution: Fixed

 [PATCH] Flow name infinite loop
 ---

 Key: FOP-2510
 URL: https://issues.apache.org/jira/browse/FOP-2510
 Project: FOP
  Issue Type: Bug
Reporter: Thanasis Giannimaras
 Attachments: svnLoop.patch, test.fo


 If the flow-name in the fo:flow element maps to a region body  belonging to a 
 simple-page-master not referenced by the fo:page-sequence element , then fop 
 enters an infinite loop.  Submitted patch that throws a ValidationException 
 when this happens.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (FOP-2510) [PATCH] Flow name infinite loop

2015-08-12 Thread simon steiner (JIRA)

[ 
https://issues.apache.org/jira/browse/FOP-2510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14693511#comment-14693511
 ] 

simon steiner commented on FOP-2510:


Added http://svn.apache.org/viewvc?view=revisionrevision=1695517

 [PATCH] Flow name infinite loop
 ---

 Key: FOP-2510
 URL: https://issues.apache.org/jira/browse/FOP-2510
 Project: FOP
  Issue Type: Bug
Reporter: Thanasis Giannimaras
 Attachments: svnLoop.patch, test.fo


 If the flow-name in the fo:flow element maps to a region body  belonging to a 
 simple-page-master not referenced by the fo:page-sequence element , then fop 
 enters an infinite loop.  Submitted patch that throws a ValidationException 
 when this happens.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)