[jira] [Created] (FOP-2690) text-align does not work in table-column
Oblio Leitch created FOP-2690:
-
Summary: text-align does not work in table-column
Key: FOP-2690
URL: https://issues.apache.org/jira/browse/FOP-2690
Project: FOP
Issue Type: Bug
Affects Versions: 2.1
Reporter: Oblio Leitch
When I put a {{text-align}} attribute in a {{table-column}}, it's not
formatting the text in the table accordingly.
Example:
{code:xml}
test
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (FOP-2143) Add PDF/A-2 output option
[ https://issues.apache.org/jira/browse/FOP-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] simon steiner resolved FOP-2143. Resolution: Works for Me > Add PDF/A-2 output option > - > > Key: FOP-2143 > URL: https://issues.apache.org/jira/browse/FOP-2143 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: trunk > Environment: Operating System: Linux > Platform: PC >Reporter: Vincent Hennebert > > In the context of FOP, this would mainly allow to produce PDF/A compliant > documents that include transparency. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (FOP-1678) Infinite loop in footnotes
[ https://issues.apache.org/jira/browse/FOP-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] simon steiner resolved FOP-1678. Resolution: Works for Me > Infinite loop in footnotes > -- > > Key: FOP-1678 > URL: https://issues.apache.org/jira/browse/FOP-1678 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: trunk > Environment: Operating System: Linux > Platform: PC >Reporter: Johan Pretorius > Attachments: c.fo, footnote-bug.fo, footnote-infinite-loop.fo > > > See post http://www.nabble.com/fop-trunk-hangs-ts24166975.html > Attached is the fo file that refuses to run to completion. > I have downloaded the most recent trunk version from svn 2 days ago. > Compilation worked fine. > When trying to produce a pdf file from it fop hangs, it seems, after > processing all my paragraphs. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (FOP-1659) Hyperlinks to a directory containing a %20 space are not correctly handled
[ https://issues.apache.org/jira/browse/FOP-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] simon steiner resolved FOP-1659. Resolution: Works for Me > Hyperlinks to a directory containing a %20 space are not correctly handled > -- > > Key: FOP-1659 > URL: https://issues.apache.org/jira/browse/FOP-1659 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: trunk > Environment: Operating System: All > Platform: All >Reporter: Trejkaz > Attachments: b47122.patch, PDF Linking Test Broken.zip, PDF Linking > Test Fixed.zip > > > Attached zip file contains two FO files which are intended to link to each > other's PDF after generation. > The directories contain spaces, thus the url has %20 in it. However, on > conversion to PDF, FOP appears to have mangled the URL somehow so that it no > longer works. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (FOP-1663) ImageIO-based images are blurry when rendering a PDF
[ https://issues.apache.org/jira/browse/FOP-1663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15878528#comment-15878528 ] simon steiner commented on FOP-1663: Try zooming pdf to 65% in a viewer, so image is same same as original > ImageIO-based images are blurry when rendering a PDF > > > Key: FOP-1663 > URL: https://issues.apache.org/jira/browse/FOP-1663 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: trunk > Environment: Operating System: All > Platform: All >Reporter: David Green > Attachments: Picture 2.png, test.fo, test-image.png, test.pdf > > > When using PNG or JPG images are blurry when rendering PDF output. The > problem appears to be related to image size computations even when scaling is > not used, however this may not be the only factor. Running with a patched > version of FOP (with a fix for bug 27151) images are still blurry (though > slightly better than running without the patch). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FOP-1608) [PATCH] Synchronization fault in FontInfoFinder
[
https://issues.apache.org/jira/browse/FOP-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
simon steiner updated FOP-1608:
---
Summary: [PATCH] Synchronization fault in FontInfoFinder (was:
Synchronization fault in FontInfoFinder)
> [PATCH] Synchronization fault in FontInfoFinder
> ---
>
> Key: FOP-1608
> URL: https://issues.apache.org/jira/browse/FOP-1608
> Project: FOP
> Issue Type: Bug
> Components: font/unqualified
>Affects Versions: trunk
> Environment: Operating System: All
> Platform: All
>Reporter: ilj
> Attachments: b46336.diff, b46336.diff, b46336.diff
>
>
> I have a multi-threaded rendering application. It produced this exception:
> java.lang.NullPointerException
> at
> org.apache.fop.fonts.autodetect.FontInfoFinder.find(FontInfoFinder.java:172)
> at
> org.apache.fop.render.PrintRendererConfigurator.addFontInfoListFromFileList(PrintRendererConfigurator.java:233)
> at
> org.apache.fop.render.PrintRendererConfigurator.buildFontListFromConfiguration(PrintRendererConfigurator.java:140)
> at
> org.apache.fop.render.PrintRendererConfigurator.configure(PrintRendererConfigurator.java:95)
> at
> org.apache.fop.render.pdf.PDFRendererConfigurator.configure(PDFRendererConfigurator.java:71)
> at
> org.apache.fop.render.RendererFactory.createRenderer(RendererFactory.java:187)
> at org.apache.fop.area.RenderPagesModel.(RenderPagesModel.java:68)
> at org.apache.fop.area.AreaTreeHandler.setupModel(AreaTreeHandler.java:127)
> at org.apache.fop.area.AreaTreeHandler.(AreaTreeHandler.java:102)
> at
> org.apache.fop.render.RendererFactory.createFOEventHandler(RendererFactory.java:224)
> at org.apache.fop.fo.FOTreeBuilder.(FOTreeBuilder.java:100)
> at org.apache.fop.apps.Fop.createDefaultHandler(Fop.java:100)
> at org.apache.fop.apps.Fop.(Fop.java:78)
> at org.apache.fop.apps.FopFactory.newFop(FopFactory.java:247)
> ...
> I guess the problem is, that you don't synchronize usage of FontCache in this
> method:
> 150 public EmbedFontInfo find(URL fontUrl, FontResolver resolver,
> FontCache fontCache) {
> 151 String embedUrl = null;
> 152 embedUrl = fontUrl.toExternalForm();
> 153
> 154 long fileLastModified = -1;
> 155 if (fontCache != null) {
> 156 try {
> 157 URLConnection conn = fontUrl.openConnection();
> 158 try {
> 159 fileLastModified = conn.getLastModified();
> 160 } finally {
> 161 //An InputStream is created even if it's not
> accessed, but we need to close it.
> 162 IOUtils.closeQuietly(conn.getInputStream());
> 163 }
> 164 } catch (IOException e) {
> 165 // Should never happen, because URL must be local
> 166 log.debug("IOError: " + e.getMessage());
> 167 fileLastModified = 0;
> 168 }
> 169 // firstly try and fetch it from cache before loading/parsing
> the font file
> 170 if (fontCache.containsFont(embedUrl)) {
> 171 CachedFontInfo fontInfo = fontCache.getFont(embedUrl);
> 172 if (fontInfo.lastModified() == fileLastModified) {
> 173 return fontInfo;
> 174 } else {
> 175 // out of date cache item
> 176 fontCache.removeFont(embedUrl);
> 177 }
> 178 // is this a previously failed parsed font?
> 179 } else if (fontCache.isFailedFont(embedUrl,
> fileLastModified)) {
> 180 if (log.isDebugEnabled()) {
> 181 log.debug("Skipping font file that failed to load
> previously: " + embedUrl);
> 182 }
> 183 return null;
> 184 }
> 185 }
> 186
> 187 // try to determine triplet information from font file
> 188 CustomFont customFont = null;
> 189 try {
> 190 customFont = FontLoader.loadFont(fontUrl, resolver);
> 191 } catch (Exception e) {
> 192 //TODO Too verbose (it's an error but we don't care if some
> fonts can't be loaded)
> 193 if (log.isErrorEnabled()) {
> 194 log.error("Unable to load font file: " + embedUrl + ".
> Reason: " + e.getMessage());
> 195 }
> 196 if (fontCache != null) {
> 197 fontCache.registerFailedFont(embedUrl, fileLastModified);
> 198 }
> 199 return null;
> 200 }
> 201 return fontInfoFromCustomFont(fontUrl, customFont, fontCache);
>
> 202 }
> 203 }
> 204
> When thread1 and thread2 both enter IF at line 170, one can remove the font
> and then the other will get null at line 171.
--
This message
[jira] [Resolved] (FOP-1556) PDF Extensions - Prototype
[ https://issues.apache.org/jira/browse/FOP-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] simon steiner resolved FOP-1556. Resolution: Works for Me https://xmlgraphics.apache.org/fop/trunk/metadata.html#pdf-custom-properties > PDF Extensions - Prototype > -- > > Key: FOP-1556 > URL: https://issues.apache.org/jira/browse/FOP-1556 > Project: FOP > Issue Type: Bug > Components: unqualified >Affects Versions: trunk > Environment: Operating System: All > Platform: All >Reporter: Andreas L. Delmelle > Attachments: pdf-extensions-prototype.diff, > pdf-extensions-prototype.diff, pdf-extensions-prototype.diff > > > The attached patch contains a working prototype implementation for PDF > extension objects, as discussed on > http://wiki.apache.org/xmlgraphics-fop/ExtensionsForPdf. > There's still quite some unfinished business there, but it should suffice to > give interested parties a starting-point (no idea when I'll be able to spend > more time on this). > After applying the patch, Jiri Tyr's requirement can be met by adding: > xmlns:pdf="http://xmlgraphics.apache.org/fop/extensions/pdf;> > FullScreen > > basically anywhere in the document (I think; I've only tried specifying it as > a descendant of fo:root). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (FOP-1466) About AFP renderer Issues when i try to using Aria Fonts which come from Mainframe
[ https://issues.apache.org/jira/browse/FOP-1466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] simon steiner resolved FOP-1466. Resolution: Works for Me > About AFP renderer Issues when i try to using Aria Fonts which come from > Mainframe > -- > > Key: FOP-1466 > URL: https://issues.apache.org/jira/browse/FOP-1466 > Project: FOP > Issue Type: Bug > Components: font/unqualified >Affects Versions: 0.94 > Environment: Operating System: other > Platform: Other >Reporter: feelyn > Attachments: b44024 > > > Exception: > system properly. > java.lang.IllegalArgumentException: Transparent data is longer than 253 > bytes: > [B@2e8e2e8e > at > org.apache.fop.render.afp.modca.PresentationTextData.addTransparentData > (PresentationTextData.java:213) > at org.apache.fop.render.afp.modca.PresentationTextData.createTextData > (PresentationTextData.java:348) > at > org.apache.fop.render.afp.modca.PresentationTextObject.createTextData > (PresentationTextObject.java:128) > at org.apache.fop.render.afp.modca.AbstractPageObject.createText > (AbstractPageObject.java:221) > at org.apache.fop.render.afp.modca.AFPDataStream.createText > (AFPDataStream.java:353) > at org.apache.fop.render.afp.AFPRenderer.renderText > (AFPRenderer.java:1178) > at org.apache.fop.render.AbstractRenderer.renderInlineArea > (AbstractRenderer.java:617) > at org.apache.fop.render.AbstractRenderer.renderLineArea > (AbstractRenderer.java:606) > at org.apache.fop.render.AbstractRenderer.renderBlocks > (AbstractRenderer.java:532) > at org.apache.fop.render.AbstractRenderer.renderBlock > (AbstractRenderer.java:582) > at org.apache.fop.render.AbstractRenderer.renderBlocks > (AbstractRenderer.java:522) > at org.apache.fop.render.AbstractRenderer.renderBlock > (AbstractRenderer.java:582) > at org.apache.fop.render.AbstractRenderer.renderBlocks > (AbstractRenderer.java:522) > at org.apache.fop.render.AbstractRenderer.renderBlock > (AbstractRenderer.java:582) > at org.apache.fop.render.AbstractRenderer.renderBlocks > (AbstractRenderer.java:522) > at org.apache.fop.render.AbstractRenderer.renderFlow > (AbstractRenderer.java:427) > at org.apache.fop.render.AbstractRenderer.renderMainReference > (AbstractRenderer.java:406) > at org.apache.fop.render.AbstractRenderer.renderBodyRegion > (AbstractRenderer.java:340) > at org.apache.fop.render.afp.AFPRenderer.renderRegionViewport > (AFPRenderer.java:431) > at org.apache.fop.render.AbstractRenderer.renderPageAreas > (AbstractRenderer.java:258) > at org.apache.fop.render.afp.AFPRenderer.renderPage > (AFPRenderer.java:585) > at org.apache.fop.area.RenderPagesModel.addPage > (RenderPagesModel.java:120) > at org.apache.fop.layoutmgr.PageSequenceLayoutManager.finishPage > (PageSequenceLayoutManager.java:424) > at org.apache.fop.layoutmgr.PageSequenceLayoutManager.makeNewPage > (PageSequenceLayoutManager.java:377) > at org.apache.fop.layoutmgr.PageBreaker.handleBreakTrait > (PageBreaker.java:492) > at org.apache.fop.layoutmgr.PageBreaker.startPart(PageBreaker.java:398) > at org.apache.fop.layoutmgr.AbstractBreaker.addAreas > (AbstractBreaker.java:420) > at org.apache.fop.layoutmgr.AbstractBreaker.addAreas > (AbstractBreaker.java:370) > at org.apache.fop.layoutmgr.PageBreaker.doPhase3(PageBreaker.java:262) > at org.apache.fop.layoutmgr.AbstractBreaker.doLayout > (AbstractBreaker.java:345) > at org.apache.fop.layoutmgr.AbstractBreaker.doLayout > (AbstractBreaker.java:263) > at org.apache.fop.layoutmgr.PageSequenceLayoutManager.activateLayout > (PageSequenceLayoutManager.java:144) > at org.apache.fop.area.AreaTreeHandler.endPageSequence > (AreaTreeHandler.java:233) > at org.apache.fop.fo.pagination.PageSequence.endOfNode > (PageSequence.java:145) > at org.apache.fop.fo.FOTreeBuilder$MainFOHandler.endElement > (FOTreeBuilder.java:378) > at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:194) > at org.apache.xalan.transformer.TransformerIdentityImpl.endElement > (TransformerIdentityImpl.java:1101) > at org.apache.xerces.parsers.AbstractSAXParser.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
[jira] [Updated] (FOP-933) [PATCH] Allow Print Renderer to select Printer and Tray.
[ https://issues.apache.org/jira/browse/FOP-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] simon steiner updated FOP-933: -- Summary: [PATCH] Allow Print Renderer to select Printer and Tray. (was: Allow Print Renderer to select Printer and Tray.) > [PATCH] Allow Print Renderer to select Printer and Tray. > > > Key: FOP-933 > URL: https://issues.apache.org/jira/browse/FOP-933 > Project: FOP > Issue Type: Improvement > Components: renderer/awt >Affects Versions: 0.20.5 > Environment: Operating System: Linux > Platform: PC >Reporter: Andres Galeano > Attachments: diff.txt > > > [PATCH] > Hello, > I have added tested and deployed code that allows the Print Renderer to > select a > Printer and a Tray. > I'm going to try to attach my patch to this bug report. (although I don't see > that attach option at the moment...) > I added code to add a logger, and changed the margins a bit. I really did not > intend to include these changes in the patch, but I did not feel confident > enough to rip them out with out re-testing everything. I thought a savvy > developer could weed though the mistake and grab the important Printer and > Tray > code. > I also added an option to not exit when the task is completed. This made it > easier for me to call the FOP Java classes from my Java code. > Finally I ended up using environment variables for my options. I really don't > think this is a good idea, but I did not have the time to add real parameter > options to the fop code. > Any way, I realize this may be too sloppy to use, and I apologize. I figured > I > should offer it any way, since I may not be the only developer interested in > selecting a printer and tray to print to. (I really hope to offer a cleaner > version of this in the future, if it's something FOP is interested in.) > Thanks alot, > Andy. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FOP-940) [PATCH] Pluggable area creation: AreaFactory
[ https://issues.apache.org/jira/browse/FOP-940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] simon steiner updated FOP-940: -- Summary: [PATCH] Pluggable area creation: AreaFactory (was: Pluggable area creation: AreaFactory) > [PATCH] Pluggable area creation: AreaFactory > > > Key: FOP-940 > URL: https://issues.apache.org/jira/browse/FOP-940 > Project: FOP > Issue Type: Improvement > Components: unqualified >Affects Versions: trunk > Environment: Operating System: other > Platform: Other >Reporter: Tibor Vyletel > Attachments: AreaFactoryPhase2.patch > > > Creation of area objects was moved from LMs to classes implementing > org.apache.fop.area.AreaFactory interface. This interface provides a set of > create methods for different types of area objects. > Default implementation of this interface is in class called > DefaultAreaFactory. > Additional changes: > + FOUserAgent - getter & setter for AreaFactory > + AbstractLayoutManager - getAreaFactory() --> convenience method for accesing > current area factory in layout manager > + Default constructor was added to several area classes -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FOP-1278) PNG missing for RTF output
[ https://issues.apache.org/jira/browse/FOP-1278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] simon steiner updated FOP-1278: --- Summary: PNG missing for RTF output (was: PNG causes NPE for RTF output) > PNG missing for RTF output > -- > > Key: FOP-1278 > URL: https://issues.apache.org/jira/browse/FOP-1278 > Project: FOP > Issue Type: Bug > Components: renderer/rtf >Affects Versions: trunk > Environment: Operating System: other > Platform: Other >Reporter: Chris Bowditch > Attachments: moon.png, test.fo > > > Attached PNG causes a NPE when rendering to RTF. Submitted by Dominic Brugger > (brugger.at.puzzle.ch) Stack trace below: > SEVERE: Error while handling an external-graphic: null > java.lang.NullPointerException > at org.apache.commons.io.IOUtils.copy(IOUtils.java:920) > at org.apache.commons.io.IOUtils.toByteArray(IOUtils.java:215) > at org.apache.fop.image.AbstractFopImage.loadDefaultOriginalData > (AbstractFopImage.java:223) > at org.apache.fop.image.ImageIOImage.loadOriginalData > (ImageIOImage.java:217) > at org.apache.fop.image.AbstractFopImage.load > (AbstractFopImage.java:174) > at org.apache.fop.render.rtf.RTFHandler.image(RTFHandler.java:1131) > at org.apache.fop.render.rtf.RTFHandler.invokeDeferredEvent > (RTFHandler.java:1492) > at org.apache.fop.render.rtf.RTFHandler.recurseFONode > (RTFHandler.java:1616) > at org.apache.fop.render.rtf.RTFHandler.recurseFONode > (RTFHandler.java:1687) > at org.apache.fop.render.rtf.RTFHandler.recurseFONode > (RTFHandler.java:1687) > at org.apache.fop.render.rtf.RTFHandler.recurseFONode > (RTFHandler.java:1639) > at org.apache.fop.render.rtf.RTFHandler.endPageSequence > (RTFHandler.java: -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (FOP-1422) NPE using a Tiff Image
[ https://issues.apache.org/jira/browse/FOP-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] simon steiner resolved FOP-1422. Resolution: Works for Me > NPE using a Tiff Image > -- > > Key: FOP-1422 > URL: https://issues.apache.org/jira/browse/FOP-1422 > Project: FOP > Issue Type: Bug > Components: image/unqualified >Affects Versions: trunk > Environment: Operating System: Windows XP > Platform: All >Reporter: Chris Bowditch > Attachments: 27101358~58841f14.TIFF, test_tiff.fo, tiff.diff > > > I receive the following NPE when running the attahed FO and TIFF image: > SEVERE: Exception > java.lang.NullPointerException > at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:168) > at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:115) > at org.apache.fop.cli.Main.startFOP(Main.java:166) > at org.apache.fop.cli.Main.main(Main.java:197) > - > java.lang.NullPointerException > at org.apache.fop.image.TIFFImage.decodeImage(TIFFImage.java:77) > at org.apache.fop.image.XmlGraphicsCommonsImage.loadDimensions > (XmlGraphi > csCommonsImage.java:79) > at org.apache.fop.image.AbstractFopImage.load > (AbstractFopImage.java:160) > at > org.apache.fop.fo.flow.ExternalGraphic.bind(ExternalGraphic.java:75) > at org.apache.fop.fo.FObj.processNode(FObj.java:125) > at org.apache.fop.fo.FOTreeBuilder$MainFOHandler.startElement > (FOTreeBuil > der.java:313) > at > org.apache.fop.fo.FOTreeBuilder.startElement(FOTreeBuilder.java:180) > at org.apache.xalan.transformer.TransformerIdentityImpl.startElement > (Tra > nsformerIdentityImpl.java:1072) > at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown > Sour > ce) > at org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement > (Unkn > own Source) > at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement > (Unkn > own Source) > at > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContent > Dispatcher.dispatch(Unknown Source) > at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument > (Un > known 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.xalan.transformer.TransformerIdentityImpl.transform > (Transf > ormerIdentityImpl.java:484) > at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:165) > at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:115) > at org.apache.fop.cli.Main.startFOP(Main.java:166) > at org.apache.fop.cli.Main.main(Main.java:197) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FOP-1409) PageBreakingAlgorithm IndexOutOfBoundsException
[
https://issues.apache.org/jira/browse/FOP-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
simon steiner updated FOP-1409:
---
Summary: PageBreakingAlgorithm IndexOutOfBoundsException (was:
IndexOutOfBoundsException)
> PageBreakingAlgorithm IndexOutOfBoundsException
> ---
>
> Key: FOP-1409
> URL: https://issues.apache.org/jira/browse/FOP-1409
> Project: FOP
> Issue Type: Bug
> Components: unqualified
>Affects Versions: 0.94
> Environment: Operating System: other
> Platform: All
>Reporter: Hussein Shafie
>
> This IndexOutOfBoundsException:
> ===
> java.lang.IndexOutOfBoundsException: Index: 1, Size: 1
> at java.util.ArrayList.RangeCheck(ArrayList.java:508)
> at java.util.ArrayList.get(ArrayList.java:320)
> at
> org.apache.fop.layoutmgr.PageBreakingAlgorithm.computeDemerits(PageBreakingAlgorithm.java:644)
> at
> org.apache.fop.layoutmgr.BreakingAlgorithm.considerLegalBreak(BreakingAlgorithm.java:737)
> at
> org.apache.fop.layoutmgr.PageBreakingAlgorithm.considerLegalBreak(PageBreakingAlgorithm.java:309)
> at
> org.apache.fop.layoutmgr.BreakingAlgorithm.findBreakingPoints(BreakingAlgorithm.java:485)
> at
> org.apache.fop.layoutmgr.BreakingAlgorithm.findBreakingPoints(BreakingAlgorithm.java:403)
> at
> org.apache.fop.layoutmgr.AbstractBreaker.doLayout(AbstractBreaker.java:338)
> at
> org.apache.fop.layoutmgr.AbstractBreaker.doLayout(AbstractBreaker.java:263)
> at
> org.apache.fop.layoutmgr.PageSequenceLayoutManager.activateLayout(PageSequenceLayoutManager.java:144)
> at
> org.apache.fop.area.AreaTreeHandler.endPageSequence(AreaTreeHandler.java:233)
> at
> org.apache.fop.fo.pagination.PageSequence.endOfNode(PageSequence.java:145)
> at
> org.apache.fop.fo.FOTreeBuilder$MainFOHandler.endElement(FOTreeBuilder.java:378)
> at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:194)
> ===
> Workaround:
> In src/java/org/apache/fop/layoutmgr/PageBreakingAlgorithm.java, replace:
> ===
> if (footnotesPending) {
> if (footnoteListIndex < footnotesList.size() - 1) {
> // add demerits for the deferred footnotes
> demerits += (footnotesList.size() - 1 - footnoteListIndex)
> * deferredFootnoteDemerits;
> }
> if (footnoteElementIndex
> < ((LinkedList) footnotesList.get(footnoteListIndex)).size() - 1)
> {
> // add demerits for the footnote split between pages
> demerits += splitFootnoteDemerits;
> }
> }
> ===
>
> by:
> ===
> if (footnotesPending) {
> int footnotesListSize = footnotesList.size();
> if (footnoteListIndex < footnotesListSize - 1) {
> // add demerits for the deferred footnotes
> demerits += (footnotesListSize - 1 - footnoteListIndex)
> * deferredFootnoteDemerits;
> }
> if (footnoteListIndex < footnotesListSize &&
> footnoteElementIndex
> < ((LinkedList) footnotesList.get(footnoteListIndex)).size() - 1)
> {
> // add demerits for the footnote split between pages
> demerits += splitFootnoteDemerits;
> }
> }
> ===
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (FOP-1358) Tibetan characters not rendered correctly in PDF
[ https://issues.apache.org/jira/browse/FOP-1358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] simon steiner resolved FOP-1358. Resolution: Works for Me > Tibetan characters not rendered correctly in PDF > > > Key: FOP-1358 > URL: https://issues.apache.org/jira/browse/FOP-1358 > Project: FOP > Issue Type: Bug > Components: renderer/pdf >Affects Versions: 0.93 > Environment: Operating System: other > Platform: Other >Reporter: Mildred > Attachments: hung1.png, Hung.xml > > > The tibetan characters are not drawn correctly in my PDf documents. Aparently > it's not the PDF reader's fault because OpenOffice can generate correct > documents that can be seen in every PDF reader i have. Moreover, even Adobe > Reader can't display correctly FOP's PDF documents. > I already filled a poppler bug I closed because it's not the poppler's fault : > https://bugs.freedesktop.org/show_bug.cgi?id=10845 > I'll attach the FO document I use and screenshoot of the result. If you need > the > tibetan font, it is called "TibetanMachineUni" and can be found in the tools > section of the website http://www.thdl.org/. Because it became a little harder > to download it I made it avaible on my website: > http://silkensedai.free.fr/TibetanMachineUni.ttf (licence is GPL) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (FOP-1318) ImageProvider should be overridable in ImageFactory
[ https://issues.apache.org/jira/browse/FOP-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] simon steiner resolved FOP-1318. Resolution: Works for Me > ImageProvider should be overridable in ImageFactory > --- > > Key: FOP-1318 > URL: https://issues.apache.org/jira/browse/FOP-1318 > Project: FOP > Issue Type: Bug > Components: image/unqualified >Affects Versions: 0.93 > Environment: Operating System: other > Platform: PC >Reporter: Torok Edwin > Attachments: tiffbug.zip, tiff_jaio.patch > > > Fop-0.93 uses its internal TIFFImage reader, and I have encountered problems > with it: > - tiff is compressed using group4 compression > - I include the tiff in a generated PDF by using external-graphic in my .fo > file > The resulting image is corrupt (size wrong, extra white lines in the middle of > the image, like for a broken interlaced file). > Using JAI ImageIO the generated PDF looks ok. Using JAI only, the generated > PDF > looks ok, but the size of the image is wrong. > The imageprovider being used is hardcoded in the ImageFactory constructor. > This > should be overridable. (eg: a setting in FOUserAgent). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (FOP-860) fop.sh doesn't set exit status
[ https://issues.apache.org/jira/browse/FOP-860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] simon steiner resolved FOP-860. --- Resolution: Works for Me > fop.sh doesn't set exit status > -- > > Key: FOP-860 > URL: https://issues.apache.org/jira/browse/FOP-860 > Project: FOP > Issue Type: Bug > Components: unqualified >Affects Versions: 0.20.5 > Environment: Operating System: Linux > Platform: Other >Reporter: Roland Neilands > > Previously reported, noticed one more occurrence. > Diff to fix: > < echo " We cannot execute $JAVACMD" > < exit > ... > > echo " We cannot execute $JAVACMD" > > exit 1 > < $JAVACMD ... fop > ... > > $JAVACMD ... fop > > exit $? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (FOP-2564) [PATCH] Ignore ICC profiles added by ImageIO loader
[ https://issues.apache.org/jira/browse/FOP-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15878060#comment-15878060 ] simon steiner commented on FOP-2564: Can we see fo? > [PATCH] Ignore ICC profiles added by ImageIO loader > --- > > Key: FOP-2564 > URL: https://issues.apache.org/jira/browse/FOP-2564 > Project: FOP > Issue Type: Bug > Components: image/png >Reporter: Matthias Reischenbacher > Attachments: fop-2564-commons.patch, fop-2564.patch > > > When rendering PNG files for PDF output, ICC profiles are taken into account > which were added by the ImageIO loader. This causes an unexpected color > display (light, dull colors) and should be avoided. > This bug only applies to image files that don't have an embedded ICC profile > and are loaded by ImageLoaderImageIO. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (FOP-1575) PNGs are rendered with dull colors
[ https://issues.apache.org/jira/browse/FOP-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15878057#comment-15878057 ] simon steiner commented on FOP-1575: Works in trunk on adobe reader on windows > PNGs are rendered with dull colors > -- > > Key: FOP-1575 > URL: https://issues.apache.org/jira/browse/FOP-1575 > Project: FOP > Issue Type: Bug > Components: image/unqualified >Affects Versions: trunk > Environment: Operating System: Windows XP > Platform: PC >Reporter: Jean-François El Fouly > Attachments: example.png, GenerateTestImage.java, image-dump.png, > output2.pdf, output.pdf, soft-mask-dump.png, test-ais-false.pdf, > test-ais-true.pdf, test-atsa47-1.fo, test-atsa47-2.fo, test-atsa47-2.pdf, > test-image.png > > > At least some 24-bit PNG files, but probably all of them, are rendered by FOP > with dull colors (see example.png). > This can be seen even in a simple 8 pixel example. The image and its colors > are correct (object 11 in the PDF); and the soft mask too (object 10 in the > PDF). So there could be a problem with the ICC color profile after all (obj > 5). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (FOP-1575) PNGs are rendered with dull colors
[ https://issues.apache.org/jira/browse/FOP-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] simon steiner resolved FOP-1575. Resolution: Works for Me > PNGs are rendered with dull colors > -- > > Key: FOP-1575 > URL: https://issues.apache.org/jira/browse/FOP-1575 > Project: FOP > Issue Type: Bug > Components: image/unqualified >Affects Versions: trunk > Environment: Operating System: Windows XP > Platform: PC >Reporter: Jean-François El Fouly > Attachments: example.png, GenerateTestImage.java, image-dump.png, > output2.pdf, output.pdf, soft-mask-dump.png, test-ais-false.pdf, > test-ais-true.pdf, test-atsa47-1.fo, test-atsa47-2.fo, test-atsa47-2.pdf, > test-image.png > > > At least some 24-bit PNG files, but probably all of them, are rendered by FOP > with dull colors (see example.png). > This can be seen even in a simple 8 pixel example. The image and its colors > are correct (object 11 in the PDF); and the soft mask too (object 10 in the > PDF). So there could be a problem with the ICC color profile after all (obj > 5). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (FOP-2570) [PATCH] Misplaced border of spanned table cells in RTL WM context
[ https://issues.apache.org/jira/browse/FOP-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Bowditch reassigned FOP-2570: --- Assignee: Matthias Reischenbacher > [PATCH] Misplaced border of spanned table cells in RTL WM context > - > > Key: FOP-2570 > URL: https://issues.apache.org/jira/browse/FOP-2570 > Project: FOP > Issue Type: Bug > Components: layout/unqualified >Reporter: Matthias Reischenbacher >Assignee: Matthias Reischenbacher > Attachments: fop-2570.patch > > > FOP-2047 fixed table borders of spanned table cells. Since FOP-2310 some > borders are misplaced again. > I'm adding a patch for a first review. I'll add additional checks in the > layout test case of FOP-2047 a bit later. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (FOP-2628) [PATCH] Bugfix in URISpecification.java: 'a', not 'A'
[ https://issues.apache.org/jira/browse/FOP-2628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15877849#comment-15877849 ] Chris Bowditch commented on FOP-2628: - Please can you attach a XSL-FO File that replicates the issue? > [PATCH] Bugfix in URISpecification.java: 'a', not 'A' > - > > Key: FOP-2628 > URL: https://issues.apache.org/jira/browse/FOP-2628 > Project: FOP > Issue Type: Bug > Components: unqualified >Affects Versions: 2.1 >Reporter: Agneta Walterscheidt >Priority: Trivial > Labels: patch > Attachments: fixbug.patch > > > [PATCH] > I fixed a bug in URISpecification.java (an 'A' was used where an 'a' was > meant). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (FOP-2570) [PATCH] Misplaced border of spanned table cells in RTL WM context
[ https://issues.apache.org/jira/browse/FOP-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15877847#comment-15877847 ] Chris Bowditch commented on FOP-2570: - Please can you attach an XSL-FO File that replicates the issue? > [PATCH] Misplaced border of spanned table cells in RTL WM context > - > > Key: FOP-2570 > URL: https://issues.apache.org/jira/browse/FOP-2570 > Project: FOP > Issue Type: Bug > Components: layout/unqualified >Reporter: Matthias Reischenbacher > Attachments: fop-2570.patch > > > FOP-2047 fixed table borders of spanned table cells. Since FOP-2310 some > borders are misplaced again. > I'm adding a patch for a first review. I'll add additional checks in the > layout test case of FOP-2047 a bit later. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (FOP-2659) [PATCH] Arabic glyph not substituted
[ https://issues.apache.org/jira/browse/FOP-2659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Bowditch reassigned FOP-2659: --- Assignee: simon steiner > [PATCH] Arabic glyph not substituted > > > Key: FOP-2659 > URL: https://issues.apache.org/jira/browse/FOP-2659 > Project: FOP > Issue Type: Bug >Reporter: simon steiner >Assignee: simon steiner > Attachments: arabicbold.patch, fop.xconf, test.fo > > > Arial bold looks different from Arial non bold > fop test.fo -c fop.xconf out.pdf > Patch fails on some serialized data tests, can be fixed by calling > GenerateArabicTestData > https://www.microsoft.com/typography/otfntdev/arabicot/features.aspx -- This message was sent by Atlassian JIRA (v6.3.15#6346)
