[jira] [Created] (FOP-2259) 1 bit TIFF error
simon steiner created FOP-2259: -- Summary: 1 bit TIFF error Key: FOP-2259 URL: https://issues.apache.org/jira/browse/FOP-2259 Project: Fop Issue Type: Bug Reporter: simon steiner fop test.fo out.pdf java.lang.ClassCastException: [S cannot be cast to [B -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FOP-2259) [PATCH] 1 bit TIFF error
[ https://issues.apache.org/jira/browse/FOP-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] simon steiner updated FOP-2259: --- Summary: [PATCH] 1 bit TIFF error (was: 1 bit TIFF error) [PATCH] 1 bit TIFF error Key: FOP-2259 URL: https://issues.apache.org/jira/browse/FOP-2259 Project: Fop Issue Type: Bug Reporter: simon steiner Attachments: fop1bit.patch, xgc1bit.patch fop test.fo out.pdf java.lang.ClassCastException: [S cannot be cast to [B -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FOP-2259) 1 bit TIFF error
[ https://issues.apache.org/jira/browse/FOP-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] simon steiner updated FOP-2259: --- Attachment: xgc1bit.patch fop1bit.patch 1 bit TIFF error Key: FOP-2259 URL: https://issues.apache.org/jira/browse/FOP-2259 Project: Fop Issue Type: Bug Reporter: simon steiner Attachments: fop1bit.patch, xgc1bit.patch fop test.fo out.pdf java.lang.ClassCastException: [S cannot be cast to [B -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FOP-2259) [PATCH] 1 bit TIFF error
[ https://issues.apache.org/jira/browse/FOP-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] simon steiner updated FOP-2259: --- Description: fop test.fo out.pdf java.lang.ClassCastException: [S cannot be cast to [B I cant share tiff due to private information. was: fop test.fo out.pdf java.lang.ClassCastException: [S cannot be cast to [B [PATCH] 1 bit TIFF error Key: FOP-2259 URL: https://issues.apache.org/jira/browse/FOP-2259 Project: Fop Issue Type: Bug Reporter: simon steiner Attachments: fop1bit.patch, xgc1bit.patch fop test.fo out.pdf java.lang.ClassCastException: [S cannot be cast to [B I cant share tiff due to private information. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FOP-1278) PNG causes NPE for RTF output
[ https://issues.apache.org/jira/browse/FOP-1278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Meyer updated FOP-1278: -- Attachment: test.fo I know this is an old bug, but thought I'd just investigate to see whether this is still reproducible and if it's worth keeping this open. I have attached the following FO and am not getting the NPE for which this bug was originally raised for. It now creates the RTF without error, however if you open the RTF instead of finding the image, some text in the RTF is written as the following: org.apache.fop.render.rtf.rtflib.rtfdoc.RtfExternalGraphic$ExternalGraphicException org.apache.fop.render.rtf.rtflib.rtfdoc.RtfExternalGraphic$ExternalGraphicException: The tag fo:external-graphic does not support png - image type. I guess that means this can be closed? PNG causes NPE for RTF output - Key: FOP-1278 URL: https://issues.apache.org/jira/browse/FOP-1278 Project: Fop Issue Type: Bug Components: 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FOP-1333) External graphic doesnt size properly with height set at 100%
[ https://issues.apache.org/jira/browse/FOP-1333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13673190#comment-13673190 ] Robert Meyer commented on FOP-1333: --- Another old one, but seemingly still valid today. I am sure this issue has come up elsewhere on the message board before now. I think the block is taking into consideration the line spacing even though there is no text. If you specify the parent block of the image to have font-size=0, the image fills the complete height I think this is a bit of a grey area with regard to whether the block takes into consideration line spacing if there is no text. Again, not sure if this should be left open as this is unlikely to be changed unless someone has some strong views on removing line spacing with no text. External graphic doesnt size properly with height set at 100% - Key: FOP-1333 URL: https://issues.apache.org/jira/browse/FOP-1333 Project: Fop Issue Type: Bug Components: general Affects Versions: 0.93 Environment: Operating System: other Platform: PC Reporter: Barry Pearce Attachments: logo.jpg, test.pdf The following XSL-FO causes a complaint about the graphics being out of limits and DOES NOT render at the scaled size. The specification states that a height of 100% should cause the area to be set at the same size of the parent (which should be the size of extent in this case. ?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 master-name=Form page-width=210mm page-height=297mm margin-top=10mm margin-bottom=10mm margin-left=10mm margin-right=10mm padding=0 fo:region-body margin=0 margin-top=32mm padding=0/ fo:region-before extent=32mm margin=0 padding=0/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence master-reference=Form fo:static-content flow-name=xsl-region-before fo:block text-align=center height=100% width=100% border-style=solid border-color=orange border-width=0.25mm fo:external-graphic border-style=solid border-color=black border-width=0.25mm scaling=uniform scaling-method=resample-any-method height=100% content-height=scale-to-fit src=logo.jpg / /fo:block /fo:static-content fo:flow flow-name=xsl-region-body fo:block-container height=100% width=100% border-style=solid border-color=blue border-width=0.25mm fo:block text-align=center font-size=20pt font-family=serif line-height=30pt LOGO CHECK /fo:block /fo:block-container /fo:flow /fo:page-sequence /fo:root -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FOP-2260) [PATCH] Smart quotes broken in RTF if at start of text
Christopher Lowdon created FOP-2260: --- Summary: [PATCH] Smart quotes broken in RTF if at start of text Key: FOP-2260 URL: https://issues.apache.org/jira/browse/FOP-2260 Project: Fop Issue Type: Bug Components: rtf Affects Versions: 1.1 Reporter: Christopher Lowdon Priority: Minor Attachments: mypatch.diff When you have a quote at the start of your string, it is transformed into a smart quote incorrectly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FOP-2260) [PATCH] Smart quotes broken in RTF if at start of text
[ https://issues.apache.org/jira/browse/FOP-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Lowdon updated FOP-2260: Attachment: mypatch.diff [PATCH] Smart quotes broken in RTF if at start of text -- Key: FOP-2260 URL: https://issues.apache.org/jira/browse/FOP-2260 Project: Fop Issue Type: Bug Components: rtf Affects Versions: 1.1 Reporter: Christopher Lowdon Priority: Minor Labels: patch Attachments: mypatch.diff When you have a quote at the start of your string, it is transformed into a smart quote incorrectly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FOP-2151) maven dependency has wrong avalon group id
[ https://issues.apache.org/jira/browse/FOP-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13673983#comment-13673983 ] Daniel Manchester commented on FOP-2151: At least with sbt (http://www.scala-sbt.org/), the build tool I'm using, it was possible to work around this issue and still pull in FOP 1.1 as a managed dependency. More here: http://oklampy.wordpress.com/2013/05/30/working-around-bad-dependency-declarations/ maven dependency has wrong avalon group id -- Key: FOP-2151 URL: https://issues.apache.org/jira/browse/FOP-2151 Project: Fop Issue Type: Bug Components: general Affects Versions: 1.1 Environment: Operating System: Platform: PC Reporter: Lloyd The maven pom for fop 1.1 uses incorrect dependency for avalon framework. With 4.2.0 the the group id changed to avalon-framework from org.apache.avalon.framework workaround: update pom as follows dependency groupIdorg.apache.xmlgraphics/groupId artifactIdfop/artifactId version1.1/version exclusions exclusion artifactIdavalon-framework-api/artifactId groupIdorg.apache.avalon.framework/groupId /exclusion exclusion artifactIdavalon-framework-impl/artifactId groupIdorg.apache.avalon.framework/groupId /exclusion /exclusions /dependency !-- these two are to correct issues in fop dependency -- dependency groupIdavalon-framework/groupId artifactIdavalon-framework-api/artifactId version4.2.0/version /dependency dependency groupIdavalon-framework/groupId artifactIdavalon-framework-impl/artifactId version4.2.0/version /dependency -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (FOP-2151) maven dependency has wrong avalon group id
[ https://issues.apache.org/jira/browse/FOP-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13673983#comment-13673983 ] Daniel Manchester edited comment on FOP-2151 at 6/4/13 3:05 AM: At least with sbt ( http://www.scala-sbt.org/ ), the build tool I'm using, it was possible to work around this issue and still pull in FOP 1.1 as a managed dependency. More here: http://oklampy.wordpress.com/2013/05/30/working-around-bad-dependency-declarations/ was (Author: dmanchester): At least with sbt (http://www.scala-sbt.org/), the build tool I'm using, it was possible to work around this issue and still pull in FOP 1.1 as a managed dependency. More here: http://oklampy.wordpress.com/2013/05/30/working-around-bad-dependency-declarations/ maven dependency has wrong avalon group id -- Key: FOP-2151 URL: https://issues.apache.org/jira/browse/FOP-2151 Project: Fop Issue Type: Bug Components: general Affects Versions: 1.1 Environment: Operating System: Platform: PC Reporter: Lloyd The maven pom for fop 1.1 uses incorrect dependency for avalon framework. With 4.2.0 the the group id changed to avalon-framework from org.apache.avalon.framework workaround: update pom as follows dependency groupIdorg.apache.xmlgraphics/groupId artifactIdfop/artifactId version1.1/version exclusions exclusion artifactIdavalon-framework-api/artifactId groupIdorg.apache.avalon.framework/groupId /exclusion exclusion artifactIdavalon-framework-impl/artifactId groupIdorg.apache.avalon.framework/groupId /exclusion /exclusions /dependency !-- these two are to correct issues in fop dependency -- dependency groupIdavalon-framework/groupId artifactIdavalon-framework-api/artifactId version4.2.0/version /dependency dependency groupIdavalon-framework/groupId artifactIdavalon-framework-impl/artifactId version4.2.0/version /dependency -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Deleted] (FOP-2151) maven dependency has wrong avalon group id
[ https://issues.apache.org/jira/browse/FOP-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Manchester updated FOP-2151: --- Comment: was deleted (was: At least with sbt ( http://www.scala-sbt.org/ ), the build tool I'm using, it was possible to work around this issue and still pull in FOP 1.1 as a managed dependency. More here: http://oklampy.wordpress.com/2013/05/30/working-around-bad-dependency-declarations/) maven dependency has wrong avalon group id -- Key: FOP-2151 URL: https://issues.apache.org/jira/browse/FOP-2151 Project: Fop Issue Type: Bug Components: general Affects Versions: 1.1 Environment: Operating System: Platform: PC Reporter: Lloyd The maven pom for fop 1.1 uses incorrect dependency for avalon framework. With 4.2.0 the the group id changed to avalon-framework from org.apache.avalon.framework workaround: update pom as follows dependency groupIdorg.apache.xmlgraphics/groupId artifactIdfop/artifactId version1.1/version exclusions exclusion artifactIdavalon-framework-api/artifactId groupIdorg.apache.avalon.framework/groupId /exclusion exclusion artifactIdavalon-framework-impl/artifactId groupIdorg.apache.avalon.framework/groupId /exclusion /exclusions /dependency !-- these two are to correct issues in fop dependency -- dependency groupIdavalon-framework/groupId artifactIdavalon-framework-api/artifactId version4.2.0/version /dependency dependency groupIdavalon-framework/groupId artifactIdavalon-framework-impl/artifactId version4.2.0/version /dependency -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FOP-2151) maven dependency has wrong avalon group id
[ https://issues.apache.org/jira/browse/FOP-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13673985#comment-13673985 ] Daniel Manchester commented on FOP-2151: At least with sbt ( http://www.scala-sbt.org/ ), the build tool I'm using, it was possible to work around this issue and still pull in FOP 1.1 as a managed dependency. More here: http://oklampy.wordpress.com/2013/05/30/working-around-bad-dependency-declarations/ maven dependency has wrong avalon group id -- Key: FOP-2151 URL: https://issues.apache.org/jira/browse/FOP-2151 Project: Fop Issue Type: Bug Components: general Affects Versions: 1.1 Environment: Operating System: Platform: PC Reporter: Lloyd The maven pom for fop 1.1 uses incorrect dependency for avalon framework. With 4.2.0 the the group id changed to avalon-framework from org.apache.avalon.framework workaround: update pom as follows dependency groupIdorg.apache.xmlgraphics/groupId artifactIdfop/artifactId version1.1/version exclusions exclusion artifactIdavalon-framework-api/artifactId groupIdorg.apache.avalon.framework/groupId /exclusion exclusion artifactIdavalon-framework-impl/artifactId groupIdorg.apache.avalon.framework/groupId /exclusion /exclusions /dependency !-- these two are to correct issues in fop dependency -- dependency groupIdavalon-framework/groupId artifactIdavalon-framework-api/artifactId version4.2.0/version /dependency dependency groupIdavalon-framework/groupId artifactIdavalon-framework-impl/artifactId version4.2.0/version /dependency -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
