[Bug 64126] [PATCH] AFP plot values are incorrectly calculated in page overlays when renderer-resolution setting not 240dpi
https://bz.apache.org/bugzilla/show_bug.cgi?id=64126 William A. Rowe Jr. changed: What|Removed |Added Status|NEW |RESOLVED OS||All Resolution|--- |INVALID --- Comment #3 from William A. Rowe Jr. --- More spam -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 64126] [PATCH] AFP plot values are incorrectly calculated in page overlays when renderer-resolution setting not 240dpi
https://bz.apache.org/bugzilla/show_bug.cgi?id=64126 Ebarg changed: What|Removed |Added Hardware|PC |Macintosh OS|Linux |Mac OS X 10.13 Component|Win32 MSI Installer |mod_usertrack Severity|major |critical --- Comment #2 from Ebarg --- Remove all files from hardware and remove all files from software files -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 64126] [PATCH] AFP plot values are incorrectly calculated in page overlays when renderer-resolution setting not 240dpi
https://bz.apache.org/bugzilla/show_bug.cgi?id=64126
Ebarg changed:
What|Removed |Added
Alias||Feds
CC||e.barg0...@icloud.com
Severity|normal |major
--- Comment #1 from Ebarg ---
rest/bug/(id_or_alias)
{
"ids" : [35],
"status" : "IN_PROGRESS",
"keywords" : {
"add" : ["funny", "stupid"]
}
}
The par
--
You are receiving this mail because:
You are on the CC list for the bug.
[Bug 64126] New: [PATCH] AFP plot values are incorrectly calculated in page overlays when renderer-resolution setting not 240dpi
https://bz.apache.org/bugzilla/show_bug.cgi?id=64126 Bug ID: 64126 Summary: [PATCH] AFP plot values are incorrectly calculated in page overlays when renderer-resolution setting not 240dpi Product: Apache httpd-2 Version: 2.5-HEAD Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P2 Component: Win32 MSI Installer Assignee: b...@httpd.apache.org Reporter: e.barg0...@icloud.com CC: d...@cumiskey.com, fop-dev@xmlgraphics.apache.org Depends on: 48002 Target Milestone: --- +++ This bug was initially created as a clone of Bug #48002 +++ Plot values for AFP page overlays are always calculated at a resolution of 240dpi regardless of configuration settings. This calculation should be done at rendering time - not during configuration (See http://markmail.org/search/?q=fop-dev#query:fop-dev%20order%3Adate-backward+page:1+mid:6xesm7i7jkwiozjg+state:results) for details. Adrian. Referenced Bugs: https://bz.apache.org/bugzilla/show_bug.cgi?id=48002 [Bug 48002] [PATCH] AFP plot values are incorrectly calculated in page overlays when renderer-resolution setting not 240dpi -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 48002] [PATCH] AFP plot values are incorrectly calculated in page overlays when renderer-resolution setting not 240dpi
https://bz.apache.org/bugzilla/show_bug.cgi?id=48002 Ebarg changed: What|Removed |Added Blocks||64126 Referenced Bugs: https://bz.apache.org/bugzilla/show_bug.cgi?id=64126 [Bug 64126] [PATCH] AFP plot values are incorrectly calculated in page overlays when renderer-resolution setting not 240dpi -- You are receiving this mail because: You are the assignee for the bug.
[Bug 51843] Surrogate pairs not treated as single unicode codepoint for display purposes
https://issues.apache.org/bugzilla/show_bug.cgi?id=51843 --- Comment #37 from Sameh Ayoub --- (In reply to comment #36) > (In reply to comment #35) > > Nice to see you'd considered this thread. As I knew, even mainframe has > > similiar issues in using supporting surrogate pairs. Is that any workaround > > if stick to latest FOP version, or any news on tenative rollout of v1.2? > > FOP 1.1rc1 was just release, and perhaps one month later 1.1 will be > released. After that, I intend to put this work item on my list for possible > 1.2 features. There is no schedule for 1.2, but I'd like to do it by the end > of this year. Hi Glenn, Thanks for considering adding this feature in FOP 1.2 by the end of this year. We are using FOP 1.1, and we want to have this feature as soon as it is get added. So, we are wondering: - Do you think this will be done in the near future? - Will the solution can be patched to FOP 1.1 easily? Thanks for your coordination. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54236] source-resolution and font-size do not play well together
https://issues.apache.org/bugzilla/show_bug.cgi?id=54236 Luis Bernardo changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #1 from Luis Bernardo --- I thought more about this and came to the conclusion that it does make sense that the font sizes specified as a number (i.e., not a length) be scaled the same way images are when the source-resolution is not the default one. So this is a non bug. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 53249] fop sample.fo -print does not work on Mac OS X
https://issues.apache.org/bugzilla/show_bug.cgi?id=53249 Luis Bernardo changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from Luis Bernardo --- this is not reproducible in trunk anymore but it does happen with FOP-1.1. closing the issue until there is further reason to reopen it. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54236] New: source-resolution and font-size do not play well together
https://issues.apache.org/bugzilla/show_bug.cgi?id=54236 Bug ID: 54236 Summary: source-resolution and font-size do not play well together Product: Fop Version: trunk Hardware: All OS: All Status: NEW Severity: normal Priority: P2 Component: fonts Assignee: fop-dev@xmlgraphics.apache.org Reporter: lmpmberna...@gmail.com Classification: Unclassified Created attachment 29674 --> https://issues.apache.org/bugzilla/attachment.cgi?id=29674&action=edit examples specifying a source-resolution different from 72 affects the size of fonts if the font-size attribute is specified. no impact is seen if the font-size is not specified. note that this is independent of SVG. the attached example, together with fop.xconf for different source-resolutions, exemplify the issue. the example is for PDF but the same happens with PostScript and other output formats. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54113] Deadlock in CompareUtil class
https://issues.apache.org/bugzilla/show_bug.cgi?id=54113 --- Comment #5 from gar...@motorweb.co.nz --- (In reply to comment #4) Right, that makes sense. Unfortunately it's not possible to determine from our stack trace which fo was being used, but it's quite likely somewhere in our codebase we have defined the parameters in a different order. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54113] Deadlock in CompareUtil class
https://issues.apache.org/bugzilla/show_bug.cgi?id=54113 Alex Giotis changed: What|Removed |Added CC||alex.gio...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54113] Deadlock in CompareUtil class
https://issues.apache.org/bugzilla/show_bug.cgi?id=54113 --- Comment #4 from Alex Giotis --- Gareth, I believe that this is a bug exposed by fixing some equals/hashcode implementations. Those changes were introduced during the refactoring of PropertyCache (as you wrote) and I also believe that the usage of Vectors is problematic. I would prefer to have UnmodifiableLists (or some other immutable structure) containing trimToSize() ArrayLists to minimise memory requirements. With my previous comment, I was asking for an XSL:FO that has the potential of triggering this deadlock. To reproduce it, one would need to render it concurrently by different threads, probably connect a debugger and put some breakpoints or change code to add some delays. I understand that this is not always easy as one may need to anonymise the input. I guess I would see blocks like: and but the effort to fix it would be wasted if this is wrong. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54234] New: Documentation is misleading
https://issues.apache.org/bugzilla/show_bug.cgi?id=54234 Bug ID: 54234 Summary: Documentation is misleading Product: Fop Version: trunk Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P2 Component: ps Assignee: fop-dev@xmlgraphics.apache.org Reporter: sstei...@thunderhead.com Classification: Unclassified http://xmlgraphics.apache.org/fop/trunk/fonts.html says "When embedding PostScript fonts, the entire font is always embedded." Specific character embedded is supported -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54113] Deadlock in CompareUtil class
https://issues.apache.org/bugzilla/show_bug.cgi?id=54113 gar...@motorweb.co.nz changed: What|Removed |Added Status|NEEDINFO|NEW --- Comment #3 from gar...@motorweb.co.nz --- I've just hit this deadlock with FOP 1.1 in our production system (thread dump snippet attached). It ran fine for a couple of weeks and then locked up. Given this it would appear to be a race condition, and could not be reproduced by running the same XSL-FO as requested by Alex Giotis. It looks like this may have been exposed by the refactoring of PropertyCache for 1.1, but my initial investigation suggests the root of the cause is putting a Vector in the PropertyCache. When two threads are fetching from the cache they compare two Vectors to each other and deadlock on the synchronized equals and listIterator methods. It would be better to use some other List implementation, or failing that, synchronizing the cache fetch method. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54113] Deadlock in CompareUtil class
https://issues.apache.org/bugzilla/show_bug.cgi?id=54113 --- Comment #2 from gar...@motorweb.co.nz --- Created attachment 29665 --> https://issues.apache.org/bugzilla/attachment.cgi?id=29665&action=edit Thread dump snippet -- You are receiving this mail because: You are the assignee for the bug.
Bug report for Fop [2012/12/02]
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned| | | OPN=ReopenedVER=Verified(Skipped Closed/Resolved) | | | +-+ | | | Severity: BLK=Blocker CRI=Critical REG=Regression MAJ=Major | | | | MIN=Minor NOR=NormalENH=Enhancement TRV=Trivial | | | | +-+ | | | | Date Posted | | | | | +--+ | | | | | Description | | | | | | | |17369|New|Nor|2003-02-25|Footnote duplication | |17380|New|Nor|2003-02-25|Batik Component will not recognize fe SVG elem| |17921|New|Nor|2003-03-12|Kerning is broken for standard fonts | |18801|New|Nor|2003-04-08|[PATCH] "visibility" property is not implemented | |19228|New|Nor|2003-04-22|[PATCH] Child LayoutContext is null in certain cir| |19695|New|Enh|2003-05-06|[PATCH] Allow fox:destination as child of fox:outl| |20280|New|Enh|2003-05-27|text-align and text-align-last only partially impl| |20407|New|Enh|2003-06-02|[PATCH] Configure image caching using the configur| |21265|Inf|Nor|2003-07-02|referencing a custom font (TTF or Adobe Type 1) fo| |21905|New|Nor|2003-07-26|large list-item-label bleeds into following block | |21982|New|Nor|2003-07-30|NullPointer Exception in LazyFont with embedded fo| |22450|New|Nor|2003-08-15|Unterminated iteration in JPEGReader class| |24148|New|Nor|2003-10-27|Kerning upsets text-align="end" | |24378|New|Nor|2003-11-04|Minor problem in sample code for embedding| |24663|New|Nor|2003-11-12|fo:block space-after property needs fixing| |25022|New|Nor|2003-11-26|XSL-FO to PCL : images not included | |25341|New|Nor|2003-12-08|percentage resolution not being recalculated on di| |25432|New|Nor|2003-12-11|Cannot embed the User Defined Characters into the | |26047|New|Nor|2004-01-11|Space-after value remembered and used on second do| |26590|New|Nor|2004-02-02|last character width in winansi font is missed| |27107|New|Nor|2004-02-20|TTF Reader fails | |27727|New|Nor|2004-03-17|problem displaying Japanese fonts in PDF. | |27890|New|Min|2004-03-24|fop.sh doesn't set exit status| |29632|New|Nor|2004-06-17|Rendered reads fonts from disk everytime it render| |30006|New|Nor|2004-07-09|eps doesn't show up in recent GhostScript versions| |30214|New|Nor|2004-07-20|PSGraphics2D.drawImage incorrect matrix generated | |31039|New|Nor|2004-09-03|URL in basic-link is scrambled by encryption | |31225|New|Nor|2004-09-14|Need embedded page sequence functionality | |31301|New|Nor|2004-09-19|FOP limitation-Summary of columns value at Table F| |31674|New|Enh|2004-10-12|Allow Print Renderer to select Printer and Tray. | |32054|New|Enh|2004-11-04|Pluggable area creation: AreaFactory | |32970|New|Nor|2005-01-06|incorrect elision of word space in czech text | |33174|New|Nor|2005-01-20|An unrecognized token'NaN' was found when opening | |35500|New|Nor|2005-06-24|Missing .close() call on stream opened for JPEG im| |35939|New|Nor|2005-07-30|[PATCH] Port of 0.20.5 Driver.java class | |36011|New|Nor|2005-08-04|Setting word-spacing on justified blocks removes j| |36238|New|Nor|2005-08-18|text-align="justify" doesn't work on custom fonts | |36395|New|Nor|2005-08-27|Common Border and Background Properties not suppor| |36408|Inf|Min|2005-08-29|FOP hyphenation splits consecutive digits onto sep| |36533|Inf|Nor|2005-09-07|Incorrect ipd and twsadjust settings | |36977|New|Nor|2005-10-09|[PATCH] TextLayoutManager CJK line break | |37114|New|Min|2005-10-17|No error message on illegal/unknown values on a pr| |37136|Inf|Nor|2005-10-18|external-graphic dimensions and rendering | |37236|New|Nor|2005-10-25|[PATCH] Fix gradients and patterns| |37305|New|Nor|2005-10-30|Added deviceDPI to PDFDocumentGraphics2D | |37579|New|Nor|2005-11-21|footnotes within tables and listsl get lost | |38121|New|Nor|2006-01-04|border-separation disturbs table layout | |38244|New|Nor|2006-01-12|table-column and number-columns-spanned (prepatch)| |38862|Inf|Nor|2006-03-06|No ImageReader for this type of image | |39034|New|Nor|2006-03-20|page-number-citation : the text after overlaps the| |39118|New|Nor|2006-03-27|[PA
[Bug 49801] [PATCH] Region-Body Column balancing incorrect if content is table with header
https://issues.apache.org/bugzilla/show_bug.cgi?id=49801 --- Comment #18 from Alex Giotis --- Great work !! I tested it with a multi-page complex layout and it is working very well. Luckily for us, I see the same output as with the hack I had attached. Next week, a colleague will execute more tests on other documents with complex layout and will check some corner cases. I will add a comment if something comes up. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 50514] Images being created with a blueish tint in the PDF
https://issues.apache.org/bugzilla/show_bug.cgi?id=50514 --- Comment #7 from Luis Bernardo --- thank you for the hint but can you provide an example image that shows the issue? I was never able to see the problem with the image originally provided. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 50514] Images being created with a blueish tint in the PDF
https://issues.apache.org/bugzilla/show_bug.cgi?id=50514 --- Comment #6 from Phil Varner --- This appears to be an issue with PNGs _without_ and alpha channel in 0.95. Verified that this issue does not exist in 1.0. Please close as you please. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 49801] [PATCH] Region-Body Column balancing incorrect if content is table with header
https://issues.apache.org/bugzilla/show_bug.cgi?id=49801 --- Comment #17 from Robert Meyer --- Created attachment 29655 --> https://issues.apache.org/bugzilla/attachment.cgi?id=29655&action=edit Sample list of test column balancing fo files A zip containing a list of sample column balancing FO files -- You are receiving this mail because: You are the assignee for the bug.
[Bug 49801] [PATCH] Region-Body Column balancing incorrect if content is table with header
https://issues.apache.org/bugzilla/show_bug.cgi?id=49801 Robert Meyer changed: What|Removed |Added Summary|Region-Body Column |[PATCH] Region-Body Column |balancing incorrect if |balancing incorrect if |content is table with |content is table with |header |header -- You are receiving this mail because: You are the assignee for the bug.
[Bug 49801] Region-Body Column balancing incorrect if content is table with header
https://issues.apache.org/bugzilla/show_bug.cgi?id=49801 --- Comment #16 from Robert Meyer --- Created attachment 29653 --> https://issues.apache.org/bugzilla/attachment.cgi?id=29653&action=edit New column balancing algorithm implementation This patch is a re-write of the coloumn balancing algorithm to fix the issues that existed within the old code. We have been working on this for the last couple of weeks and has been a team effort by me, Luis Bernado and Vincent Hennebert. It passes all unit tests and renders not only the tests above correctly but also many others we have thrown at it. I will post another zip attachment containing sample balancing fo's for you to try should you wish. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54219] New: The ANT task "org.apache.fop.tools.anttasks.Fop" never throws a build exception
https://issues.apache.org/bugzilla/show_bug.cgi?id=54219 Bug ID: 54219 Summary: The ANT task "org.apache.fop.tools.anttasks.Fop" never throws a build exception Product: Fop Version: all Hardware: PC Status: NEW Severity: normal Priority: P2 Component: general Assignee: fop-dev@xmlgraphics.apache.org Reporter: radu_cor...@sync.ro Classification: Unclassified A concrete example, the DITA OT project uses a series of ANT build files to publish DITA to PDF. The Apache FOP task "org.apache.fop.tools.anttasks.Fop" is used for this. If the task fails (for example the PDF is opened in another application or the XSL-FO file has severe validation problems) it should throw an ANT BuildException because there is no need to continue the entire ANT build as if nothing happened. Instead, the method "org.apache.fop.tools.anttasks.FOPTaskStarter.render(File, File, String)" catches all exceptions and just logs them in the console. This means that it is possible that ANT finishes with a "Build succesfull" message and in fact the PDF was not produced at all. Maybe you should add a "failonerror" attribute to the task and have it fail by default when an error is encountered. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54212] Only White pages are produces
https://issues.apache.org/bugzilla/show_bug.cgi?id=54212 Luis Bernardo changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE OS||All --- Comment #1 from Luis Bernardo --- This has been fixed in trunk. Please try that. *** This bug has been marked as a duplicate of bug 53942 *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 53942] [PATCH] Contents of fo:flow aren't rendered
https://issues.apache.org/bugzilla/show_bug.cgi?id=53942 Luis Bernardo changed: What|Removed |Added CC||koes...@bue-gmbh.de --- Comment #4 from Luis Bernardo --- *** Bug 54212 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54209] Dead link to compliance list on FOP 1.1 page
https://issues.apache.org/bugzilla/show_bug.cgi?id=54209 Chris Bowditch changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED OS||All --- Comment #1 from Chris Bowditch --- Thanks for reporting. Both the 1.0 and 1.1 overview pages were referencing compliance.html but the compliance page is compliance-static.html. I have updated both 1.0 and 1.1 overview pages and published the website in revision 839780 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54212] New: Only White pages are produces
https://issues.apache.org/bugzilla/show_bug.cgi?id=54212 Bug ID: 54212 Summary: Only White pages are produces Product: Fop Version: 1.1 Hardware: PC Status: NEW Severity: regression Priority: P2 Component: awt renderer Assignee: fop-dev@xmlgraphics.apache.org Reporter: koes...@bue-gmbh.de Classification: Unclassified Using Fop 1.1 the command: java -cp "build\fop.jar;lib\avalon-framework-4.2.0.jar;lib\batik-all-1.7.jar;lib\commons-io-1.3.1.jar;lib\commons-logging-1.0.4.jar;lib\serializer-2.7.0.jar;lib\xalan-2.7.0.jar;lib\xercesImpl-2.7.1.jar;lib\xml-apis-1.3.04.jar;lib\xml-apis-ext-1.3.04.jar;lib\xmlgraphics-commons-1.5.jar" org.apache.fop.cli.Main -fo examples\fo\basic\simple.fo -awt shows only white pages. I use used the binary download from the webpage. The command with fop 1.0 fop -fo examples\fo\basic\simple.fo -awt Shows the content of the simple.fo. (Due to an error I have to click the up and down arrows - button) java -version output: java version "1.7.0_09" Java(TM) SE Runtime Environment (build 1.7.0_09-b05) Java HotSpot(TM) 64-Bit Server VM (build 23.5-b02, mixed mode) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 41959] External links are broken if pdf is encryped
https://issues.apache.org/bugzilla/show_bug.cgi?id=41959 Charles Leduc changed: What|Removed |Added CC||cle...@broadsoft.com -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54209] New: Dead link to compliance list on FOP 1.1 page
https://issues.apache.org/bugzilla/show_bug.cgi?id=54209 Bug ID: 54209 Summary: Dead link to compliance list on FOP 1.1 page Product: Fop Version: trunk Hardware: All Status: NEW Severity: normal Priority: P2 Component: documentation Assignee: fop-dev@xmlgraphics.apache.org Reporter: andreas.pehn...@me.com Classification: Unclassified There's a link on http://xmlgraphics.apache.org/fop/1.1/index.html that points to http://xmlgraphics.apache.org/fop/compliance.html however the page doesn't exist. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 49827] integration of barcode in fop 1.0
https://issues.apache.org/bugzilla/show_bug.cgi?id=49827 Joshy Cyriac changed: What|Removed |Added CC||j.cyr...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54196] [PATCH] Added an option to configure big / little endian support for TIFF images
https://issues.apache.org/bugzilla/show_bug.cgi?id=54196 Luis Bernardo changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Luis Bernardo --- applied (attachment 29628): http://svn.apache.org/viewvc?view=revision&revision=1413442 -- You are receiving this mail because: You are the assignee for the bug.
Bug report for Fop [2012/11/25]
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned| | | OPN=ReopenedVER=Verified(Skipped Closed/Resolved) | | | +-+ | | | Severity: BLK=Blocker CRI=Critical REG=Regression MAJ=Major | | | | MIN=Minor NOR=NormalENH=Enhancement TRV=Trivial | | | | +-+ | | | | Date Posted | | | | | +--+ | | | | | Description | | | | | | | |17369|New|Nor|2003-02-25|Footnote duplication | |17380|New|Nor|2003-02-25|Batik Component will not recognize fe SVG elem| |17921|New|Nor|2003-03-12|Kerning is broken for standard fonts | |18801|New|Nor|2003-04-08|[PATCH] "visibility" property is not implemented | |19228|New|Nor|2003-04-22|[PATCH] Child LayoutContext is null in certain cir| |19695|New|Enh|2003-05-06|[PATCH] Allow fox:destination as child of fox:outl| |20280|New|Enh|2003-05-27|text-align and text-align-last only partially impl| |20407|New|Enh|2003-06-02|[PATCH] Configure image caching using the configur| |21265|Inf|Nor|2003-07-02|referencing a custom font (TTF or Adobe Type 1) fo| |21905|New|Nor|2003-07-26|large list-item-label bleeds into following block | |21982|New|Nor|2003-07-30|NullPointer Exception in LazyFont with embedded fo| |22450|New|Nor|2003-08-15|Unterminated iteration in JPEGReader class| |24148|New|Nor|2003-10-27|Kerning upsets text-align="end" | |24378|New|Nor|2003-11-04|Minor problem in sample code for embedding| |24663|New|Nor|2003-11-12|fo:block space-after property needs fixing| |25022|New|Nor|2003-11-26|XSL-FO to PCL : images not included | |25341|New|Nor|2003-12-08|percentage resolution not being recalculated on di| |25432|New|Nor|2003-12-11|Cannot embed the User Defined Characters into the | |26047|New|Nor|2004-01-11|Space-after value remembered and used on second do| |26590|New|Nor|2004-02-02|last character width in winansi font is missed| |27107|New|Nor|2004-02-20|TTF Reader fails | |27727|New|Nor|2004-03-17|problem displaying Japanese fonts in PDF. | |27890|New|Min|2004-03-24|fop.sh doesn't set exit status| |29632|New|Nor|2004-06-17|Rendered reads fonts from disk everytime it render| |30006|New|Nor|2004-07-09|eps doesn't show up in recent GhostScript versions| |30214|New|Nor|2004-07-20|PSGraphics2D.drawImage incorrect matrix generated | |31039|New|Nor|2004-09-03|URL in basic-link is scrambled by encryption | |31225|New|Nor|2004-09-14|Need embedded page sequence functionality | |31301|New|Nor|2004-09-19|FOP limitation-Summary of columns value at Table F| |31674|New|Enh|2004-10-12|Allow Print Renderer to select Printer and Tray. | |32054|New|Enh|2004-11-04|Pluggable area creation: AreaFactory | |32970|New|Nor|2005-01-06|incorrect elision of word space in czech text | |33174|New|Nor|2005-01-20|An unrecognized token'NaN' was found when opening | |35500|New|Nor|2005-06-24|Missing .close() call on stream opened for JPEG im| |35939|New|Nor|2005-07-30|[PATCH] Port of 0.20.5 Driver.java class | |36011|New|Nor|2005-08-04|Setting word-spacing on justified blocks removes j| |36238|New|Nor|2005-08-18|text-align="justify" doesn't work on custom fonts | |36395|New|Nor|2005-08-27|Common Border and Background Properties not suppor| |36408|Inf|Min|2005-08-29|FOP hyphenation splits consecutive digits onto sep| |36533|Inf|Nor|2005-09-07|Incorrect ipd and twsadjust settings | |36977|New|Nor|2005-10-09|[PATCH] TextLayoutManager CJK line break | |37114|New|Min|2005-10-17|No error message on illegal/unknown values on a pr| |37136|Inf|Nor|2005-10-18|external-graphic dimensions and rendering | |37236|New|Nor|2005-10-25|[PATCH] Fix gradients and patterns| |37305|New|Nor|2005-10-30|Added deviceDPI to PDFDocumentGraphics2D | |37579|New|Nor|2005-11-21|footnotes within tables and listsl get lost | |38121|New|Nor|2006-01-04|border-separation disturbs table layout | |38244|New|Nor|2006-01-12|table-column and number-columns-spanned (prepatch)| |38862|Inf|Nor|2006-03-06|No ImageReader for this type of image | |39034|New|Nor|2006-03-20|page-number-citation : the text after overlaps the| |39118|New|Nor|2006-03-27|[PA
[Bug 54196] [PATCH] Added an option to configure big / little endian support for TIFF images
https://issues.apache.org/bugzilla/show_bug.cgi?id=54196 Bug 54196 depends on bug 54195, which changed state. Bug 54195 Summary: [PATCH] Added little endian support for TIFF images https://issues.apache.org/bugzilla/show_bug.cgi?id=54195 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54196] New: [PATCH] Added an option to configure big / little endian support for TIFF images
https://issues.apache.org/bugzilla/show_bug.cgi?id=54196 Bug ID: 54196 Summary: [PATCH] Added an option to configure big / little endian support for TIFF images Product: Fop Version: all Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P2 Component: general Assignee: fop-dev@xmlgraphics.apache.org Reporter: rme...@hotmail.co.uk Depends on: 54195 Classification: Unclassified Created attachment 29628 --> https://issues.apache.org/bugzilla/attachment.cgi?id=29628&action=edit The patch with the changes to cofigure big / little endian support The option under the image/tiff section is called "Endianess" and supports both big_endian and little_endian options. This patch is to be used in conjunction with the changes to xml graphics (Bugzilla Bug 54195) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 49827] integration of barcode in fop 1.0
https://issues.apache.org/bugzilla/show_bug.cgi?id=49827 balza changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #9 from balza --- The problem still present FOP 1.1 BARCODE 2.1 JDK1.6.0_22 I don't understand if the problem is barcode4j 2.1, fop 1.1 or xmlgraphic-commons 1.5 Here the stacktrace. [LoggingEventListener.java:101] Image not available. URI: (instream-object). Reason: org.apache.xmlgraphics.image.loader.ImageException: The file format is not supported. No ImagePreloader found for null (No context info available) org.apache.xmlgraphics.image.loader.ImageException: The file format is not supported. No ImagePreloader found for null at org.apache.xmlgraphics.image.loader.ImageManager.preloadImage(ImageManager.java:180) at org.apache.fop.render.intermediate.AbstractIFPainter.drawImageUsingDocument(AbstractIFPainter.java:296) at org.apache.fop.render.pdf.PDFPainter.drawImage(PDFPainter.java:203) at org.apache.fop.render.intermediate.IFRenderer.renderForeignObject(IFRenderer.java:1290) at org.apache.fop.render.AbstractRenderer.renderInlineViewport(AbstractRenderer.java:820) at org.apache.fop.render.AbstractPathOrientedRenderer.renderInlineViewport(AbstractPathOrientedRenderer.java:785) at org.apache.fop.render.intermediate.IFRenderer.renderInlineViewport(IFRenderer.java:866) at org.apache.fop.render.AbstractRenderer.renderInlineArea(AbstractRenderer.java:678) at org.apache.fop.render.intermediate.IFRenderer.renderInlineArea(IFRenderer.java:913) at org.apache.fop.render.AbstractRenderer.renderLineArea(AbstractRenderer.java:643) at org.apache.fop.render.AbstractRenderer.renderBlocks(AbstractRenderer.java:561) at org.apache.fop.render.AbstractRenderer.renderBlock(AbstractRenderer.java:598) at org.apache.fop.render.intermediate.IFRenderer.renderBlock(IFRenderer.java:980) at org.apache.fop.render.AbstractRenderer.renderBlocks(AbstractRenderer.java:546) at org.apache.fop.render.AbstractRenderer.renderBlock(AbstractRenderer.java:598) at org.apache.fop.render.intermediate.IFRenderer.renderBlock(IFRenderer.java:980) at org.apache.fop.render.AbstractRenderer.renderBlocks(AbstractRenderer.java:546) at org.apache.fop.render.AbstractRenderer.renderRegion(AbstractRenderer.java:337) at org.apache.fop.render.AbstractRenderer.renderRegionViewport(AbstractRenderer.java:301) at org.apache.fop.render.intermediate.IFRenderer.renderRegionViewport(IFRenderer.java:748) at org.apache.fop.render.AbstractRenderer.renderPageAreas(AbstractRenderer.java:257) at org.apache.fop.render.AbstractRenderer.renderPage(AbstractRenderer.java:238) at org.apache.fop.render.intermediate.IFRenderer.renderPage(IFRenderer.java:597) at org.apache.fop.area.RenderPagesModel.renderPage(RenderPagesModel.java:193) at org.apache.fop.area.RenderPagesModel.checkPreparedPages(RenderPagesModel.java:174) at org.apache.fop.area.RenderPagesModel.endDocument(RenderPagesModel.java:258) at org.apache.fop.area.AreaTreeHandler.endDocument(AreaTreeHandler.java:342) at org.apache.fop.fo.FOTreeBuilder.endDocument(FOTreeBuilder.java:168) at org.apache.xml.serializer.ToXMLSAXHandler.endDocument(ToXMLSAXHandler.java:183) at org.apache.xalan.transformer.TransformerImpl.transformNode(TransformerImpl.java:1367) at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:709) at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1273) at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1251) at it.gesi.commons.pdf.impl.Obj2pdf.transform(Obj2pdf.java:102) at it.gesi.commons.pdf.impl.Obj2pdf.generatePFDOutputStream(Obj2pdf.java:63) at it.gesi.wba.gestionali.pdf.CreatePdf.createPDF(CreatePdf.java:69) at it.gesi.wba.gestionali.pdf.CreatePdf.createPDF(CreatePdf.java:62) at it.gesi.wba.gestionali.pdf.CreatePdf.creaPdf(CreatePdf.java:76) at it.gesi.commons.stampa.CreaPdfTest.testCreaPdf(CreaPdfTest.java:86) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at junit.framework.TestCase.runTest(TestCase.java:164) at junit.framework.TestCase.runBare(TestCase.java:130) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:120) at junit.framework.TestSuite.runTest(TestSuite.java:228)
[Bug 54169] [PATCH] Resolution for Acrobat Pro bug with FOP PDF's due to nums array size
https://issues.apache.org/bugzilla/show_bug.cgi?id=54169 Vincent Hennebert changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Vincent Hennebert --- Patch applied in rev. 1411352: http://svn.apache.org/viewvc?rev=1411352&view=rev I removed the re-definition of the getNums method in PDFPageLabels that had become identical to the original one (in PDFNumberTreeNode). This avoids a FindBugs warning. Thanks for your patch! Vincent -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54167] Overflow recovery doesn't play well with changing IPD
https://issues.apache.org/bugzilla/show_bug.cgi?id=54167 Vincent Hennebert changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Vincent Hennebert --- Fixed in rev. 1411306: http://svn.apache.org/viewvc?rev=1411306&view=rev -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54169] [PATCH] Resolution for Acrobat Pro bug with FOP PDF's due to nums array size
https://issues.apache.org/bugzilla/show_bug.cgi?id=54169 Robert Meyer changed: What|Removed |Added Attachment #29609|0 |1 is obsolete|| --- Comment #1 from Robert Meyer --- Created attachment 29610 --> https://issues.apache.org/bugzilla/attachment.cgi?id=29610&action=edit Forgot the test case -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54169] New: [PATCH] Resolution for Acrobat Pro bug with FOP PDF's due to nums array size
https://issues.apache.org/bugzilla/show_bug.cgi?id=54169 Bug ID: 54169 Summary: [PATCH] Resolution for Acrobat Pro bug with FOP PDF's due to nums array size Product: Fop Version: all Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P2 Component: pdf Assignee: fop-dev@xmlgraphics.apache.org Reporter: rme...@hotmail.co.uk Classification: Unclassified Created attachment 29609 --> https://issues.apache.org/bugzilla/attachment.cgi?id=29609&action=edit Patch to split the nums array to avoid issue with Acrobat Pro A bug exists in Acrobat Pro where if the nums array is deemed to be too large when saving, Acrobat will split the array. If however, the array is broken on an odd element the odd item is split where it's ID is kept in the first array and its value is placed on the second leading to a "Bad Parameter" error when checking compatibility. There is no maximum size of the nums array given in the PDF specification, so why Acrobat is doing this is unknown (performance benefits maybe). To ensure that anyone editing a FOP PDF in Acrobat Pro does not come across this problem, this patch addresses it by splitting the nums array if it exceeds a value (50). -- You are receiving this mail because: You are the assignee for the bug.
[Bug 48975] [PATCH] java.lang.NoClassDefFoundError: org/apache/batik/util/XMLResourceDescriptor
https://issues.apache.org/bugzilla/show_bug.cgi?id=48975 --- Comment #4 from Markus Gaugusch --- I have also run into this problem (using junitpdfreport.sourceforge.net), a fix would be nice! -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54167] New: Overflow recovery doesn't play well with changing IPD
https://issues.apache.org/bugzilla/show_bug.cgi?id=54167 Bug ID: 54167 Summary: Overflow recovery doesn't play well with changing IPD Product: Fop Version: all Hardware: All OS: All Status: NEW Severity: normal Priority: P2 Component: page-master/layout Assignee: fop-dev@xmlgraphics.apache.org Reporter: vhenneb...@gmail.com Classification: Unclassified Created attachment 29607 --> https://issues.apache.org/bugzilla/attachment.cgi?id=29607&action=edit FO file illustrating the issue The page overflow recovery mechanism consists in pushing the overflowing content to the next page in the hope that it will be bigger and able to accommodate the content. When the IPD of the next page changes, the page breaking algorithm returns early and AbstractBreaker (doLayout method) splits the content and re-lays out what follows the page break, according to the new IPD. Those two mechanisms are in conflict when the overflow occurs at the first legal break, leading to no too short node and no feasible break. AbstractBreaker is then asked to split before the content, which it is not designed for. When the flow IPD changes the overflow mechanism must be disabled, since anyway the line breaking has to be re-done according to the new IPD. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 53887] -awt command line option broken throwing HeadlessException
https://issues.apache.org/bugzilla/show_bug.cgi?id=53887 Glenn Adams changed: What|Removed |Added CC||kgalbre...@gmx.de --- Comment #6 from Glenn Adams --- *** Bug 54164 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54164] java.awt.HeadlessException
https://issues.apache.org/bugzilla/show_bug.cgi?id=54164 Glenn Adams changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE OS||All --- Comment #1 from Glenn Adams --- *** This bug has been marked as a duplicate of bug 53887 *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54164] New: java.awt.HeadlessException
https://issues.apache.org/bugzilla/show_bug.cgi?id=54164 Bug ID: 54164 Summary: java.awt.HeadlessException Product: Fop Version: 1.1 Hardware: PC Status: NEW Severity: normal Priority: P2 Component: general Assignee: fop-dev@xmlgraphics.apache.org Reporter: kgalbre...@gmx.de Classification: Unclassified fop -xml library.xml -xsl library.xsl -awt results in java.awt.HeadlessException at java.awt.GraphicsEnvironment at at org.apache.fop.cli.Main.main(Main.java 208) xml-file and xsl-file is perfectly correct. What's wrong? -- You are receiving this mail because: You are the assignee for the bug.
Bug report for Fop [2012/11/18]
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned| | | OPN=ReopenedVER=Verified(Skipped Closed/Resolved) | | | +-+ | | | Severity: BLK=Blocker CRI=Critical REG=Regression MAJ=Major | | | | MIN=Minor NOR=NormalENH=Enhancement TRV=Trivial | | | | +-+ | | | | Date Posted | | | | | +--+ | | | | | Description | | | | | | | |17369|New|Nor|2003-02-25|Footnote duplication | |17380|New|Nor|2003-02-25|Batik Component will not recognize fe SVG elem| |17921|New|Nor|2003-03-12|Kerning is broken for standard fonts | |18801|New|Nor|2003-04-08|[PATCH] "visibility" property is not implemented | |19228|New|Nor|2003-04-22|[PATCH] Child LayoutContext is null in certain cir| |19695|New|Enh|2003-05-06|[PATCH] Allow fox:destination as child of fox:outl| |20280|New|Enh|2003-05-27|text-align and text-align-last only partially impl| |20407|New|Enh|2003-06-02|[PATCH] Configure image caching using the configur| |21265|Inf|Nor|2003-07-02|referencing a custom font (TTF or Adobe Type 1) fo| |21905|New|Nor|2003-07-26|large list-item-label bleeds into following block | |21982|New|Nor|2003-07-30|NullPointer Exception in LazyFont with embedded fo| |22450|New|Nor|2003-08-15|Unterminated iteration in JPEGReader class| |24148|New|Nor|2003-10-27|Kerning upsets text-align="end" | |24378|New|Nor|2003-11-04|Minor problem in sample code for embedding| |24663|New|Nor|2003-11-12|fo:block space-after property needs fixing| |25022|New|Nor|2003-11-26|XSL-FO to PCL : images not included | |25341|New|Nor|2003-12-08|percentage resolution not being recalculated on di| |25432|New|Nor|2003-12-11|Cannot embed the User Defined Characters into the | |26047|New|Nor|2004-01-11|Space-after value remembered and used on second do| |26590|New|Nor|2004-02-02|last character width in winansi font is missed| |27107|New|Nor|2004-02-20|TTF Reader fails | |27727|New|Nor|2004-03-17|problem displaying Japanese fonts in PDF. | |27890|New|Min|2004-03-24|fop.sh doesn't set exit status| |29632|New|Nor|2004-06-17|Rendered reads fonts from disk everytime it render| |30006|New|Nor|2004-07-09|eps doesn't show up in recent GhostScript versions| |30214|New|Nor|2004-07-20|PSGraphics2D.drawImage incorrect matrix generated | |31039|New|Nor|2004-09-03|URL in basic-link is scrambled by encryption | |31225|New|Nor|2004-09-14|Need embedded page sequence functionality | |31301|New|Nor|2004-09-19|FOP limitation-Summary of columns value at Table F| |31674|New|Enh|2004-10-12|Allow Print Renderer to select Printer and Tray. | |32054|New|Enh|2004-11-04|Pluggable area creation: AreaFactory | |32970|New|Nor|2005-01-06|incorrect elision of word space in czech text | |33174|New|Nor|2005-01-20|An unrecognized token'NaN' was found when opening | |35500|New|Nor|2005-06-24|Missing .close() call on stream opened for JPEG im| |35939|New|Nor|2005-07-30|[PATCH] Port of 0.20.5 Driver.java class | |36011|New|Nor|2005-08-04|Setting word-spacing on justified blocks removes j| |36238|New|Nor|2005-08-18|text-align="justify" doesn't work on custom fonts | |36395|New|Nor|2005-08-27|Common Border and Background Properties not suppor| |36408|Inf|Min|2005-08-29|FOP hyphenation splits consecutive digits onto sep| |36533|Inf|Nor|2005-09-07|Incorrect ipd and twsadjust settings | |36977|New|Nor|2005-10-09|[PATCH] TextLayoutManager CJK line break | |37114|New|Min|2005-10-17|No error message on illegal/unknown values on a pr| |37136|Inf|Nor|2005-10-18|external-graphic dimensions and rendering | |37236|New|Nor|2005-10-25|[PATCH] Fix gradients and patterns| |37305|New|Nor|2005-10-30|Added deviceDPI to PDFDocumentGraphics2D | |37579|New|Nor|2005-11-21|footnotes within tables and listsl get lost | |38121|New|Nor|2006-01-04|border-separation disturbs table layout | |38244|New|Nor|2006-01-12|table-column and number-columns-spanned (prepatch)| |38862|Inf|Nor|2006-03-06|No ImageReader for this type of image | |39034|New|Nor|2006-03-20|page-number-citation : the text after overlaps the| |39118|New|Nor|2006-03-27|[PA
[Bug 54122] Wrong/missing libs filenames mentioned in "TrueType Font Metrics" section of docs
https://issues.apache.org/bugzilla/show_bug.cgi?id=54122 Chris Bowditch changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #6 from Chris Bowditch --- I've had a go at re-organizing and re-wording the font topic on the new website that you can see here: http://xmlgraphics.staging.apache.org/fop/1.1/fonts.html -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54122] Wrong/missing libs filenames mentioned in "TrueType Font Metrics" section of docs
https://issues.apache.org/bugzilla/show_bug.cgi?id=54122 --- Comment #5 from Chris Bowditch --- I am aware of those notes. I agree this page needs updating but we are about to switch to a new website, so I will probably update the page in the new website or wait until we switch before addressing this. Basically the special use cases are diminished in the latest versions of FOP. I believe the use case the author had in mind was related to single byte encoding but that too is now possible without creating the metrics files. The only other possible use case for metric files is as a means to modify the metrics extracted in case the original font contains errors, but that use case is very unlikely. I will bear that in mind when I come to rewrite the help topic. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54122] Wrong/missing libs filenames mentioned in "TrueType Font Metrics" section of docs
https://issues.apache.org/bugzilla/show_bug.cgi?id=54122 --- Comment #4 from Eduard Tibet --- (In reply to comment #3) > Hi Edward, > > Thanks for your response. You don't need to create metric files to register > the fonts manually in the fop.xconf file. The fonts topic definitely needs > work as it does appear to imply the metrics generation step is necessary, > but if you read [1] You will see the following note stating metrics files > are not needed: > > •The "metrics-url" attribute is generally not necessary except if you run > into problems with certain fonts. > > Thanks, > > Chris > > [1] http://xmlgraphics.apache.org/fop/1.1/fonts.html#register Yes, you are right, but I also talked about these notes: "Font registration via XML font metrics file is still supported and may still be necessary for _some very special cases_ as fallback variant while we stabilize font auto-detection." [1] and "The "metrics-url" attribute is generally not necessary _except if you run into problems_ with certain fonts." [2] Nobody knows where the problems appears. But, anyway, my opinion is only FOP user opinion. You, as a FOP dev, certainly know more about FOP architecture. [1] http://xmlgraphics.apache.org/fop/1.1/fonts.html#custom [2] http://xmlgraphics.apache.org/fop/1.1/fonts.html#register -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54122] Wrong/missing libs filenames mentioned in "TrueType Font Metrics" section of docs
https://issues.apache.org/bugzilla/show_bug.cgi?id=54122 --- Comment #3 from Chris Bowditch --- Hi Edward, Thanks for your response. You don't need to create metric files to register the fonts manually in the fop.xconf file. The fonts topic definitely needs work as it does appear to imply the metrics generation step is necessary, but if you read [1] You will see the following note stating metrics files are not needed: •The "metrics-url" attribute is generally not necessary except if you run into problems with certain fonts. Thanks, Chris [1] http://xmlgraphics.apache.org/fop/1.1/fonts.html#register -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54122] Wrong/missing libs filenames mentioned in "TrueType Font Metrics" section of docs
https://issues.apache.org/bugzilla/show_bug.cgi?id=54122 --- Comment #2 from Eduard Tibet --- (In reply to comment #1) > I think we should probably remove (instead of repairing as suggested) the > section that talks about metric generation as that was deprecated since > v0.95. 2Chris: Maybe I don't fully understand the metrics files generation feature. If I'm wrong in some point, let me know this point. IMHO removing this feature would be not a good solution. The fonts auto discover works well, but it really used in small desktop or special configured environments. If someone had very strict fonts requirement based on license agreements, external despondencies, etc., he really need this feature. I.e. in my own environment the fonts/metrics are hardly linked to glyphs (fonts files) and metrics using config file. I'll never be use autodiscover, because it leads to unpredictable results on final output. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54122] Wrong/missing libs filenames mentioned in "TrueType Font Metrics" section of docs
https://issues.apache.org/bugzilla/show_bug.cgi?id=54122 --- Comment #1 from Chris Bowditch --- I think we should probably remove (instead of repairing as suggested) the section that talks about metric generation as that was deprecated since v0.95. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54108] PNG and GIF image generation fails in RTF documents
https://issues.apache.org/bugzilla/show_bug.cgi?id=54108 Carl Zetterberg changed: What|Removed |Added Status|NEEDINFO|NEW --- Comment #2 from Carl Zetterberg --- Adding jai_imageio_windows-i586.jar to the Tomcat classpath does make it work. Sorry if I posted an unnecessary bug here. I was not aware that you needed to add jai_image when upgrading from fop 1.0 to fop 1.1 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54139] writing-mode="lr" an bidi-override etc
https://issues.apache.org/bugzilla/show_bug.cgi?id=54139 Pascal Sancho changed: What|Removed |Added OS|Mac OS X 10.4 |All -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54138] writing-mode="lr" causing null-pointer-exception
https://issues.apache.org/bugzilla/show_bug.cgi?id=54138 Pascal Sancho changed: What|Removed |Added OS|Mac OS X 10.4 |All -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54108] PNG and GIF image generation fails in RTF documents
https://issues.apache.org/bugzilla/show_bug.cgi?id=54108 Chris Bowditch changed: What|Removed |Added Status|NEW |NEEDINFO OS||All --- Comment #1 from Chris Bowditch --- Do you have jai-imageio.jar in the Tomcat classpath? If not can you try adding that to see if the issue is resolved? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54139] New: writing-mode="lr" an bidi-override etc
https://issues.apache.org/bugzilla/show_bug.cgi?id=54139 Priority: P2 Bug ID: 54139 Assignee: fop-dev@xmlgraphics.apache.org Summary: writing-mode="lr" an bidi-override etc Severity: normal Classification: Unclassified OS: Mac OS X 10.4 Reporter: quest.ja...@gmail.com Hardware: All Status: NEW Version: 1.1 Component: page-master/layout Product: Fop Created attachment 29590 --> https://issues.apache.org/bugzilla/attachment.cgi?id=29590&action=edit fo in left-to-right languages, we display 1 / 2 (i.e. page 1 of 2 pages). in right-to-left languages, it should also do 1 / 2, and it does if 1 / 2 however, if it is / , it displays (in right-to-left languages), 2 / 1 instead of 1 / 2 a summary of different variations of this is below. they should all be displayed the same for rl and rl, but in most cases it does not. (please find attached fo) 1/2 renders as 1/2 for rl, 1/2 for lr / renders as 2/1 for rl, 1/2 for lr / renders as 2/1 for rl, 1/2 for lr / renders as /21 for rl, 1/2 for lr / renders as /21 for rl, 1/2 for lr -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54138] New: writing-mode="lr" causing null-pointer-exception
https://issues.apache.org/bugzilla/show_bug.cgi?id=54138 Priority: P2 Bug ID: 54138 Assignee: fop-dev@xmlgraphics.apache.org Summary: writing-mode="lr" causing null-pointer-exception Severity: critical Classification: Unclassified OS: Mac OS X 10.4 Reporter: quest.ja...@gmail.com Hardware: All Status: NEW Version: 1.1 Component: page-master/layout Product: Fop Created attachment 29589 --> https://issues.apache.org/bugzilla/attachment.cgi?id=29589&action=edit stack trace i have seen that this fo causes a null-pointer-exception at fop1.1rc1. the same fo is perfectly fine if writing-mode="lr" or not specified http://www.w3.org/1999/XSL/Format"; font-family="Arial" writing-mode="rl"> وكلما More text attached is the stack trace. if you remove *any* of these 3 things, then there is no issue either 1. 2. 3. text-align-last="justify" -- You are receiving this mail because: You are the assignee for the bug.
[Bug 53447] [PATCH] possible start-align problem on table when writing-mode="rl"
https://issues.apache.org/bugzilla/show_bug.cgi?id=53447 Glenn Adams changed: What|Removed |Added Summary|possible start-align|[PATCH] possible |problem on table when |start-align problem on |writing-mode="rl" |table when ||writing-mode="rl" -- You are receiving this mail because: You are the assignee for the bug.
Bug report for Fop [2012/11/11]
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned| | | OPN=ReopenedVER=Verified(Skipped Closed/Resolved) | | | +-+ | | | Severity: BLK=Blocker CRI=Critical REG=Regression MAJ=Major | | | | MIN=Minor NOR=NormalENH=Enhancement TRV=Trivial | | | | +-+ | | | | Date Posted | | | | | +--+ | | | | | Description | | | | | | | |17369|New|Nor|2003-02-25|Footnote duplication | |17380|New|Nor|2003-02-25|Batik Component will not recognize fe SVG elem| |17921|New|Nor|2003-03-12|Kerning is broken for standard fonts | |18801|New|Nor|2003-04-08|[PATCH] "visibility" property is not implemented | |19228|New|Nor|2003-04-22|[PATCH] Child LayoutContext is null in certain cir| |19695|New|Enh|2003-05-06|[PATCH] Allow fox:destination as child of fox:outl| |20280|New|Enh|2003-05-27|text-align and text-align-last only partially impl| |20407|New|Enh|2003-06-02|[PATCH] Configure image caching using the configur| |21265|Inf|Nor|2003-07-02|referencing a custom font (TTF or Adobe Type 1) fo| |21905|New|Nor|2003-07-26|large list-item-label bleeds into following block | |21982|New|Nor|2003-07-30|NullPointer Exception in LazyFont with embedded fo| |22450|New|Nor|2003-08-15|Unterminated iteration in JPEGReader class| |24148|New|Nor|2003-10-27|Kerning upsets text-align="end" | |24378|New|Nor|2003-11-04|Minor problem in sample code for embedding| |24663|New|Nor|2003-11-12|fo:block space-after property needs fixing| |25022|New|Nor|2003-11-26|XSL-FO to PCL : images not included | |25341|New|Nor|2003-12-08|percentage resolution not being recalculated on di| |25432|New|Nor|2003-12-11|Cannot embed the User Defined Characters into the | |26047|New|Nor|2004-01-11|Space-after value remembered and used on second do| |26590|New|Nor|2004-02-02|last character width in winansi font is missed| |27107|New|Nor|2004-02-20|TTF Reader fails | |27727|New|Nor|2004-03-17|problem displaying Japanese fonts in PDF. | |27890|New|Min|2004-03-24|fop.sh doesn't set exit status| |29632|New|Nor|2004-06-17|Rendered reads fonts from disk everytime it render| |30006|New|Nor|2004-07-09|eps doesn't show up in recent GhostScript versions| |30214|New|Nor|2004-07-20|PSGraphics2D.drawImage incorrect matrix generated | |31039|New|Nor|2004-09-03|URL in basic-link is scrambled by encryption | |31225|New|Nor|2004-09-14|Need embedded page sequence functionality | |31301|New|Nor|2004-09-19|FOP limitation-Summary of columns value at Table F| |31674|New|Enh|2004-10-12|Allow Print Renderer to select Printer and Tray. | |32054|New|Enh|2004-11-04|Pluggable area creation: AreaFactory | |32970|New|Nor|2005-01-06|incorrect elision of word space in czech text | |33174|New|Nor|2005-01-20|An unrecognized token'NaN' was found when opening | |35500|New|Nor|2005-06-24|Missing .close() call on stream opened for JPEG im| |35939|New|Nor|2005-07-30|[PATCH] Port of 0.20.5 Driver.java class | |36011|New|Nor|2005-08-04|Setting word-spacing on justified blocks removes j| |36238|New|Nor|2005-08-18|text-align="justify" doesn't work on custom fonts | |36395|New|Nor|2005-08-27|Common Border and Background Properties not suppor| |36408|Inf|Min|2005-08-29|FOP hyphenation splits consecutive digits onto sep| |36533|Inf|Nor|2005-09-07|Incorrect ipd and twsadjust settings | |36977|New|Nor|2005-10-09|[PATCH] TextLayoutManager CJK line break | |37114|New|Min|2005-10-17|No error message on illegal/unknown values on a pr| |37136|Inf|Nor|2005-10-18|external-graphic dimensions and rendering | |37236|New|Nor|2005-10-25|[PATCH] Fix gradients and patterns| |37305|New|Nor|2005-10-30|Added deviceDPI to PDFDocumentGraphics2D | |37579|New|Nor|2005-11-21|footnotes within tables and listsl get lost | |38121|New|Nor|2006-01-04|border-separation disturbs table layout | |38244|New|Nor|2006-01-12|table-column and number-columns-spanned (prepatch)| |38862|Inf|Nor|2006-03-06|No ImageReader for this type of image | |39034|New|Nor|2006-03-20|page-number-citation : the text after overlaps the| |39118|New|Nor|2006-03-27|[PA
[Bug 54122] Wrong/missing libs filenames mentioned in "TrueType Font Metrics" section of docs
https://issues.apache.org/bugzilla/show_bug.cgi?id=54122 Eduard Tibet changed: What|Removed |Added CC||eduard.ti...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54122] New: Wrong/missing libs filenames mentioned in "TrueType Font Metrics" section of docs
https://issues.apache.org/bugzilla/show_bug.cgi?id=54122 Priority: P2 Bug ID: 54122 Assignee: fop-dev@xmlgraphics.apache.org Summary: Wrong/missing libs filenames mentioned in "TrueType Font Metrics" section of docs Severity: minor Classification: Unclassified OS: Windows XP Reporter: eduard.ti...@gmail.com Hardware: PC Status: NEW Version: 1.1 Component: documentation Product: Fop Source page/section: http://xmlgraphics.apache.org/fop/1.1/fonts.html#truetype-metrics . Bugs|errors: 1. Wrong libs filenames mentioned in the creating metrics files command (version of libs that are part of the libs filenames are missing). 2. One lib filename completely missing (xmlgraphics-commons-1.5.jar). Now available: java -cp build\fop.jar;lib\avalon-framework.jar;lib\commons-logging.jar;lib\commons-io.jar org.apache.fop.fonts.apps.TTFReader [options] C:\myfonts\cmr10.ttf ttfcm.xml How expected: java -cp build\fop.jar;lib\avalon-framework-4.2.0.jar;lib\commons-logging-1.0.4.jar;lib\commons-io-1.3.1.jar;lib\commons-logging-1.0.4.jar;lib\xmlgraphics-commons-1.5.jar org.apache.fop.fonts.apps.TTFReader [options] C:\myfonts\cmr10.ttf ttfcm.xml Notes: 1. Docs for other version fop may contain the same error - wasn't checked. 2. The same error seem to be in section http://xmlgraphics.apache.org/fop/1.1/fonts.html#type1-metrics but command wasn't checked because of absence of Type 1 fonts. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54120] AWT font creating an NPE when an SVG font isn't found for AFP output
https://issues.apache.org/bugzilla/show_bug.cgi?id=54120 Mehdi Houshmand changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Mehdi Houshmand --- Committed revision 1407393. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54120] New: AWT font creating an NPE when an SVG font isn't found for AFP output
https://issues.apache.org/bugzilla/show_bug.cgi?id=54120 Priority: P2 Bug ID: 54120 Assignee: fop-dev@xmlgraphics.apache.org Summary: AWT font creating an NPE when an SVG font isn't found for AFP output Severity: normal Classification: Unclassified OS: Linux Reporter: med1...@gmail.com Hardware: PC Status: NEW Version: trunk Component: fonts Product: Fop Created attachment 29572 --> https://issues.apache.org/bugzilla/attachment.cgi?id=29572&action=edit The fop conf The problem is that the font FOP is looking for a font called "sans-serif" and Batik has the font "SansSerif". This mismatch means that when FOP asks for "sans-serif", a "null" is returned, which then causes an NPE. While this doesn't fix the underlying issue; the disparity between "sans-serif" in FOP and "SansSerif" in Batik, either way, an NPE isn't acceptable behaviour. I've attached the relevant fop conf where you can see the triplet name "sans-serif" being assigned to Helvetica. I'll attach an FO when I reduce it down to its simplest form -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54113] Deadlock in CompareUtil class
https://issues.apache.org/bugzilla/show_bug.cgi?id=54113 Alex Giotis changed: What|Removed |Added Status|NEW |NEEDINFO OS||All --- Comment #1 from Alex Giotis --- Please attach an XSL-FO that any of Tomcat's "http-80-exec-*" were rendering so that this can be reproduced and then verify that it is resolved. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54113] New: Deadlock in CompareUtil class
https://issues.apache.org/bugzilla/show_bug.cgi?id=54113 Priority: P2 Bug ID: 54113 Assignee: fop-dev@xmlgraphics.apache.org Summary: Deadlock in CompareUtil class Severity: major Classification: Unclassified Reporter: matthias8...@gmx.at Hardware: PC Status: NEW Version: trunk Component: general Product: Fop Created attachment 29565 --> https://issues.apache.org/bugzilla/attachment.cgi?id=29565&action=edit Java Thread Dump I'm getting a dead lock in the CompareUtil class, see the attached thread dump. Here small fragment of the thread dump [2012-11-07 14:06:25] [info] Found one Java-level deadlock: [2012-11-07 14:06:25] [info] = [2012-11-07 14:06:25] [info] [2012-11-07 14:06:25] [info] "http-80-exec-58": [2012-11-07 14:06:25] [info] waiting to lock monitor 0x06ca9480 [2012-11-07 14:06:25] [info] (object 0x00071fe9bd00, a java.util.Vector) [2012-11-07 14:06:25] [info] , which is held by "http-80-exec-5" [2012-11-07 14:06:25] [info] [2012-11-07 14:06:25] [info] "http-80-exec-5": [2012-11-07 14:06:25] [info] waiting to lock monitor 0x116ecfc8 [2012-11-07 14:06:25] [info] (object 0x00071fe9a000, a java.util.Vector) [2012-11-07 14:06:25] [info] , which is held by "http-80-exec-18" [2012-11-07 14:06:25] [info] [2012-11-07 14:06:25] [info] "http-80-exec-18": [2012-11-07 14:06:25] [info] waiting to lock monitor 0x06ca9480 [2012-11-07 14:06:25] [info] (object 0x00071fe9bd00, a java.util.Vector) [2012-11-07 14:06:25] [info] , which is held by "http-80-exec-5" [2012-11-07 14:06:25] [info] [2012-11-07 14:06:25] [info] [2012-11-07 14:06:25] [info] Java stack information for the threads listed above: [2012-11-07 14:06:25] [info] === [2012-11-07 14:06:25] [info] "http-80-exec-58": [2012-11-07 14:06:25] [info] at java.util.Vector.equals(Vector.java:925) [2012-11-07 14:06:25] [info] - waiting to lock <0x00071fe9bd00> [2012-11-07 14:06:25] [info] (a java.util.Vector) [2012-11-07 14:06:25] [info] at org.apache.fop.util.CompareUtil.equal(CompareUtil.java:38) [2012-11-07 14:06:25] [info] at org.apache.fop.fo.properties.ListProperty.equals(ListProperty.java:123) [2012-11-07 14:06:25] [info] at org.apache.fop.fo.properties.PropertyCache.eq(PropertyCache.java:193) [2012-11-07 14:06:25] [info] at org.apache.fop.fo.properties.PropertyCache.fetch(PropertyCache.java:134) [2012-11-07 14:06:26] [info] at org.apache.fop.fo.properties.FontFamilyProperty$Maker.make(FontFamilyProperty.java:94) [2012-11-07 14:06:26] [info] at org.apache.fop.fo.PropertyList.convertAttributeToProperty(PropertyList.java:413) [2012-11-07 14:06:26] [info] at org.apache.fop.fo.PropertyList.addAttributesToList(PropertyList.java:321) [2012-11-07 14:06:26] [info] at org.apache.fop.fo.FObj.processNode(FObj.java:122) [2012-11-07 14:06:26] [info] at org.apache.fop.fo.FOTreeBuilder$MainFOHandler.startElement(FOTreeBuilder.java:280) [2012-11-07 14:06:26] [info] at org.apache.fop.fo.FOTreeBuilder.startElement(FOTreeBuilder.java:175) [2012-11-07 14:06:26] [info] at org.apache.xalan.transformer.TransformerIdentityImpl.startElement(TransformerIdentityImpl.java:1073) [2012-11-07 14:06:26] [info] at org.apache.xml.serializer.TreeWalker.startNode(TreeWalker.java:359) [2012-11-07 14:06:26] [info] at org.apache.xml.serializer.TreeWalker.traverse(TreeWalker.java:145) [2012-11-07 14:06:26] [info] at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:390) [2012-11-07 14:06:26] [info] at smc.fop.FopWrapper.transform(FopWrapper.java:150) [2012-11-07 14:06:26] [info] at smc.fop.FopWrapper.transform(FopWrapper.java:125) [2012-11-07 14:06:26] [info] at smc.plugin.Dom2PDF.process(Dom2PDF.java:179) [2012-11-07 14:06:26] [info] at sun.reflect.GeneratedMethodAccessor97.invoke(Unknown Source) [2012-11-07 14:06:26] [info] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [2012-11-07 14:06:26] [info] at java.lang.reflect.Method.invoke(Method.java:597) [2012-11-07 14:06:26] [info] at smc.transform.core.dynacode.DynaCode$MyInvocationHandler.invoke(DynaCode.java:374) [2012-11-07 14:06:26] [info] at $Proxy35.process(Unknown Source) [2012-11-07 14:06:26] [info] at smc.transform.core.TransformerStep.processDocument(TransformerStep.java:211) [2012-11-07 14:06:26] [info] at smc.transform.core.Transformer.process(Transformer.java:491) [2012-11-07 14:06:26] [info] at smc.transform.core.Transformer.process(Transformer.java:442) [2012-11-07 14:06:26] [info] at smc.transform.TransformServlet.doGet(TransformServlet.java:184) [2012-11-07 14:06:26] [info] at javax.se
[Bug 54098] FOP is too strict: URIs containting backslashes are not resolved in FOP 1.1
https://issues.apache.org/bugzilla/show_bug.cgi?id=54098 --- Comment #3 from Radu Coravu --- For more than 6 years Apache FOP has behaved in a certain way. This means that all projects which created XSL-FO as output could have produced references which are either local file references (like Docbook does when producing references to Note images) or URL paths which may contain "\" in them like the DITA Open Toolkit does. Such invalid references are still handled by commercial FO applications like RenderX XEP or Antenna House because they are more interested in generating the PDF than in breaking the XSL-FO transformation. Could you add in the FOP configuration file a special setting which would overpass this problem (show it as a warning) instead of signaling it as an error? This is what the producer of the Saxon XSLT processor did when he decided to no longer handle file references to XSLT files (instead of URI references). I understand that by default FOP could fail with a fatal error but you have to give the projects which produce XSL-FO (and there could be many) some time to upgrade their handling of image references and in the meantime to have users benefit of the latest bug fixes available in Apache FOP. We are the manufacturers on an XML Editor (Oxygen XML Editor), our editor comes bundled with a lot of open source software and is used to publish using a lot of open source software so upgrading the bundled FOP libraries to FOP 1.1 is a problem for us. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54108] New: PNG and GIF image generation fails in RTF documents
https://issues.apache.org/bugzilla/show_bug.cgi?id=54108 Priority: P2 Bug ID: 54108 Assignee: fop-dev@xmlgraphics.apache.org Summary: PNG and GIF image generation fails in RTF documents Severity: normal Classification: Unclassified Reporter: carl...@gmail.com Hardware: PC Status: NEW Version: 1.1 Component: rtf Product: Fop Tomcat 6 java 1.7 Fop 1.1 xmlgraphics-commons-1.5.jar will produce: org.apache.fop.render.rtf.rtflib.rtfdoc.RtfExternalGraphic$ExternalGraphicException: The tag does not support gif - image type both for PNG and GIF files when producing RTF documents The same environment and XSL produce PDF that are ok. Switching back to fop 1.0 and xmlgraphics-commons-1.4.jar resolves the problem. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54098] FOP is too strict: URIs containting backslashes are not resolved in FOP 1.1
https://issues.apache.org/bugzilla/show_bug.cgi?id=54098 --- Comment #2 from Dan Caprioara --- Thank you for the detailed answer. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54104] CPU hits 100% while rendering tiff image
https://issues.apache.org/bugzilla/show_bug.cgi?id=54104 --- Comment #1 from rajni.khur...@hcl.com --- We are using FOP and the transform() function of javax.xml.transform.Transformer to render tiff image from inputted XML and XSL-FO. Execution of transform() function is causing CPU to reach at 100% utilization during image rendering. So during continuous Image rendering requests, the CPU usage remains around 100% that stopped other applications to continue their work on that system. We also tried the same using FOP command line but get similar results. In fop.xconf we are using following settings: 1. tiff image compression type as CCITT T.6 2. DPI as 200dpi. 3. default-page-settings as height="3.625in" and width="8.5in"/> This problem is not specific to particular XML and XSL-FO. We are looking for a fix in FOP so that CPU utilization can be reduced during execution of transform() function. Do let me know in case other information is required. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54104] New: CPU hits 100% while rendering tiff image
https://issues.apache.org/bugzilla/show_bug.cgi?id=54104 Priority: P2 Bug ID: 54104 Assignee: fop-dev@xmlgraphics.apache.org Summary: CPU hits 100% while rendering tiff image Severity: major Classification: Unclassified OS: Windows XP Reporter: rajni.khur...@hcl.com Hardware: PC Status: NEW Version: 0.95 Component: images Product: Fop -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54103] column-gap doesn't work when specified as a percentage.
https://issues.apache.org/bugzilla/show_bug.cgi?id=54103 --- Comment #1 from Jonathan Levinson --- Created attachment 29554 --> https://issues.apache.org/bugzilla/attachment.cgi?id=29554&action=edit rendered PDF from shortened FO -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54103] New: column-gap doesn't work when specified as a percentage.
https://issues.apache.org/bugzilla/show_bug.cgi?id=54103 Priority: P2 Bug ID: 54103 Assignee: fop-dev@xmlgraphics.apache.org Summary: column-gap doesn't work when specified as a percentage. Severity: normal Classification: Unclassified Reporter: levin...@intersystems.com Hardware: PC Status: NEW Version: 1.0 Component: page-master/layout Product: Fop Created attachment 29553 --> https://issues.apache.org/bugzilla/attachment.cgi?id=29553&action=edit Shortened fo and rendered PDF column-gap doesn't work when specified as a percentage. Hi, according to XSL-FO REC 1.1 (§7.27.3 at [1]), percentage is a legal value for column-gap, regarding the i-p-d of the region (in your case: 20in*5% = 1in is expected, FOP giving 0). So, you should file in a bug entry on bugzilla, attaching a shortened test case. [1] http://www.w3.org/TR/xsl/#column-gap 2012/11/1 Jonathan Levinson : > I’ve run into the problem that column-gap is not working when I > express the column-gap as a percentage. > This is for multi-column (two column) output. > I attach the FO and the PDF. > Is this issue a known bug in FOP? -- pascal -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54098] FOP is too strict: URIs containting backslashes are not resolved in FOP 1.1
https://issues.apache.org/bugzilla/show_bug.cgi?id=54098 Glenn Adams changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WONTFIX OS||All --- Comment #1 from Glenn Adams --- As a user, you choose what XSLT stylesheets to use. If you use one that contains broken references, then you suffer the consequences. The correct way to handle this is get those broken XSLT stylesheets fixed, and not require FOP to accept invalid input to accommodate such brokenness. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54061] NullPointer Exception in org.apache.fop.fo.FObj
https://issues.apache.org/bugzilla/show_bug.cgi?id=54061 --- Comment #12 from spao --- (In reply to comment #10) > (In reply to comment #8) > > there is a FOP option to create a FO file indented, which indicates the > > position of errors based on the file indented? > > FOP does not produce FO, this is the matter of XSLT engine. > For convenience, FOP comes with xalan. > > See [1] to tweak your XSLT if you use xalan. > > [1] http://xml.apache.org/xalan-j/usagepatterns.html#outputprops Ok, thanks, solved. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54098] New: FOP is too strict: URIs containting backslashes are not resolved in FOP 1.1
https://issues.apache.org/bugzilla/show_bug.cgi?id=54098
Priority: P2
Bug ID: 54098
Assignee: fop-dev@xmlgraphics.apache.org
Summary: FOP is too strict: URIs containting backslashes are
not resolved in FOP 1.1
Severity: normal
Classification: Unclassified
Reporter: d...@sync.ro
Hardware: PC
Status: NEW
Version: 1.1
Component: general
Product: Fop
When publishing DITA or Docbook to PDF (on a Windows machine) there are created
FO files containing references to images. Some of the references are respecting
the URI syntax, others are using the backslash: "\". This is not under the
control of the end users. The XSLT stylesheets from these documentation
frameworks are generating these invalid URIs.
FOP 1.0 translated the back-slashses to forward slashes before attempting to
parse the URIs.
FOP 1.1 kept this translation in: org.apache.fop.apps.FOURIResolver but not in:
org.apache.fop.fo.properties.URIProperty
I propose adding the following code in:
org.apache.fop.fo.properties.URIProperty.Maker.make(PropertyList, String, FObj)
value = value.replace('\\', '/');
This will make FOP more compatible with the Docbook and DITA output.
--
You are receiving this mail because:
You are the assignee for the bug.
Bug report for Fop [2012/11/04]
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned| | | OPN=ReopenedVER=Verified(Skipped Closed/Resolved) | | | +-+ | | | Severity: BLK=Blocker CRI=Critical REG=Regression MAJ=Major | | | | MIN=Minor NOR=NormalENH=Enhancement TRV=Trivial | | | | +-+ | | | | Date Posted | | | | | +--+ | | | | | Description | | | | | | | |17369|New|Nor|2003-02-25|Footnote duplication | |17380|New|Nor|2003-02-25|Batik Component will not recognize fe SVG elem| |17921|New|Nor|2003-03-12|Kerning is broken for standard fonts | |18801|New|Nor|2003-04-08|[PATCH] "visibility" property is not implemented | |19228|New|Nor|2003-04-22|[PATCH] Child LayoutContext is null in certain cir| |19695|New|Enh|2003-05-06|[PATCH] Allow fox:destination as child of fox:outl| |20280|New|Enh|2003-05-27|text-align and text-align-last only partially impl| |20407|New|Enh|2003-06-02|[PATCH] Configure image caching using the configur| |21265|Inf|Nor|2003-07-02|referencing a custom font (TTF or Adobe Type 1) fo| |21905|New|Nor|2003-07-26|large list-item-label bleeds into following block | |21982|New|Nor|2003-07-30|NullPointer Exception in LazyFont with embedded fo| |22450|New|Nor|2003-08-15|Unterminated iteration in JPEGReader class| |24148|New|Nor|2003-10-27|Kerning upsets text-align="end" | |24378|New|Nor|2003-11-04|Minor problem in sample code for embedding| |24663|New|Nor|2003-11-12|fo:block space-after property needs fixing| |25022|New|Nor|2003-11-26|XSL-FO to PCL : images not included | |25341|New|Nor|2003-12-08|percentage resolution not being recalculated on di| |25432|New|Nor|2003-12-11|Cannot embed the User Defined Characters into the | |26047|New|Nor|2004-01-11|Space-after value remembered and used on second do| |26590|New|Nor|2004-02-02|last character width in winansi font is missed| |27107|New|Nor|2004-02-20|TTF Reader fails | |27727|New|Nor|2004-03-17|problem displaying Japanese fonts in PDF. | |27890|New|Min|2004-03-24|fop.sh doesn't set exit status| |29632|New|Nor|2004-06-17|Rendered reads fonts from disk everytime it render| |30006|New|Nor|2004-07-09|eps doesn't show up in recent GhostScript versions| |30214|New|Nor|2004-07-20|PSGraphics2D.drawImage incorrect matrix generated | |31039|New|Nor|2004-09-03|URL in basic-link is scrambled by encryption | |31225|New|Nor|2004-09-14|Need embedded page sequence functionality | |31301|New|Nor|2004-09-19|FOP limitation-Summary of columns value at Table F| |31674|New|Enh|2004-10-12|Allow Print Renderer to select Printer and Tray. | |32054|New|Enh|2004-11-04|Pluggable area creation: AreaFactory | |32970|New|Nor|2005-01-06|incorrect elision of word space in czech text | |33174|New|Nor|2005-01-20|An unrecognized token'NaN' was found when opening | |35500|New|Nor|2005-06-24|Missing .close() call on stream opened for JPEG im| |35939|New|Nor|2005-07-30|[PATCH] Port of 0.20.5 Driver.java class | |36011|New|Nor|2005-08-04|Setting word-spacing on justified blocks removes j| |36238|New|Nor|2005-08-18|text-align="justify" doesn't work on custom fonts | |36395|New|Nor|2005-08-27|Common Border and Background Properties not suppor| |36408|Inf|Min|2005-08-29|FOP hyphenation splits consecutive digits onto sep| |36533|Inf|Nor|2005-09-07|Incorrect ipd and twsadjust settings | |36977|New|Nor|2005-10-09|[PATCH] TextLayoutManager CJK line break | |37114|New|Min|2005-10-17|No error message on illegal/unknown values on a pr| |37136|Inf|Nor|2005-10-18|external-graphic dimensions and rendering | |37236|New|Nor|2005-10-25|[PATCH] Fix gradients and patterns| |37305|New|Nor|2005-10-30|Added deviceDPI to PDFDocumentGraphics2D | |37579|New|Nor|2005-11-21|footnotes within tables and listsl get lost | |38121|New|Nor|2006-01-04|border-separation disturbs table layout | |38244|New|Nor|2006-01-12|table-column and number-columns-spanned (prepatch)| |38862|Inf|Nor|2006-03-06|No ImageReader for this type of image | |39034|New|Nor|2006-03-20|page-number-citation : the text after overlaps the| |39118|New|Nor|2006-03-27|[PA
[Bug 53942] [PATCH] Contents of fo:flow aren't rendered
https://issues.apache.org/bugzilla/show_bug.cgi?id=53942 Luis Bernardo changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Luis Bernardo --- applied: http://svn.apache.org/viewvc?view=revision&revision=1405444 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54094] break-before="page" causes IllegalArgumentException
https://issues.apache.org/bugzilla/show_bug.cgi?id=54094 Luis Bernardo changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54094] break-before="page" causes IllegalArgumentException
https://issues.apache.org/bugzilla/show_bug.cgi?id=54094 Luis Bernardo changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED OS||All --- Comment #1 from Luis Bernardo --- this has been fixed in trunk back in July, after the RC for 1.1 was put forward. see also http://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-users/201207.mbox/%3C50171AE0.1070200%40gmail.com%3E for a workaround. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54094] New: break-before="page" causes IllegalArgumentException
https://issues.apache.org/bugzilla/show_bug.cgi?id=54094 Priority: P2 Bug ID: 54094 Assignee: fop-dev@xmlgraphics.apache.org Summary: break-before="page" causes IllegalArgumentException Severity: normal Classification: Unclassified Reporter: ja...@plutext.org Hardware: PC Status: NEW Version: 1.1 Component: fo tree Product: Fop @break-before="page" in the below fo causes: java.lang.IllegalArgumentException: Only non-null Positions with an index can be checked in both FOP 1.0 and 1.1. (see below for stack trace). Remove it and things work fine. http://www.w3.org/1999/XSL/Format";> http://www.w3.org/1999/XSL/Format";> http://www.w3.org/1999/XSL/Format"; font-family="Cambria" font-size="12.0pt"/> http://www.w3.org/1999/XSL/Format"/> 1. http://www.w3.org/1999/XSL/Format"; color="#345A8A" font-family="Calibri" font-size="16.0pt" font-weight="bold">I http://www.w3.org/1999/XSL/Format"; color="#345A8A" font-family="Calibri" font-size="16.0pt" font-weight="bold">ntroducción Caused by: java.lang.IllegalArgumentException: Only non-null Positions with an index can be checked at org.apache.fop.layoutmgr.AbstractLayoutManager.verifyNonNullPosition(AbstractLayoutManager.java:309) at org.apache.fop.layoutmgr.AbstractLayoutManager.isFirst(AbstractLayoutManager.java:321) at org.apache.fop.layoutmgr.list.ListItemContentLayoutManager.addAreas(ListItemContentLayoutManager.java:136) at org.apache.fop.layoutmgr.list.ListItemLayoutManager.addAreas(ListItemLayoutManager.java:542) at org.apache.fop.layoutmgr.list.ListBlockLayoutManager.addAreas(ListBlockLayoutManager.java:184) at org.apache.fop.layoutmgr.AreaAdditionUtil.addAreas(AreaAdditionUtil.java:113) at org.apache.fop.layoutmgr.FlowLayoutManager.addAreas(FlowLayoutManager.java:364) at org.apache.fop.layoutmgr.PageBreaker.addAreas(PageBreaker.java:285) at org.apache.fop.layoutmgr.AbstractBreaker.addAreas(AbstractBreaker.java:607) at org.apache.fop.layoutmgr.AbstractBreaker.addAreas(AbstractBreaker.java:481) at org.apache.fop.layoutmgr.PageBreaker.doPhase3(PageBreaker.java:313) at org.apache.fop.layoutmgr.AbstractBreaker.doLayout(AbstractBreaker.java:436) at org.apache.fop.layoutmgr.PageBreaker.doLayout(PageBreaker.java:90) at org.apache.fop.layoutmgr.PageSequenceLayoutManager.activateLayout(PageSequenceLayoutManager.java:113) at org.apache.fop.area.AreaTreeHandler.endPageSequence(AreaTreeHandler.java:267) at org.apache.fop.fo.pagination.PageSequence.endOfNode(PageSequence.java:128) at org.apache.fop.fo.FOTreeBuilder$MainFOHandler.endElement(FOTreeBuilder.java:347) at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:181) at org.apache.xalan.transformer.TransformerIdentityImpl.endElement(TransformerIdentityImpl.java:1102) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown Source) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54081] Properly tag hyphenated words
https://issues.apache.org/bugzilla/show_bug.cgi?id=54081 Vincent Hennebert changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Vincent Hennebert --- Fixed in rev. 1405158: http://svn.apache.org/viewvc?rev=1405158&view=rev -- You are receiving this mail because: You are the assignee for the bug.
[Bug 49097] [PATCH] update to AFP Image documentation
https://issues.apache.org/bugzilla/show_bug.cgi?id=49097 Chris Bowditch changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Chris Bowditch --- Thanks for the patch Peter. I have committed the changes to the CMS version of the website in revision 1404981 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 48955] [PATCH] Allow AFP font codepage names to be less than 8 chars
https://issues.apache.org/bugzilla/show_bug.cgi?id=48955 Chris Bowditch changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Chris Bowditch --- Thanks for the patch Peter. I've applied it with a minor alteration for checkstyle in revision 1404968 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54089] New: maven dependency has wrong avalon group id
https://issues.apache.org/bugzilla/show_bug.cgi?id=54089 Priority: P2 Bug ID: 54089 Assignee: fop-dev@xmlgraphics.apache.org Summary: maven dependency has wrong avalon group id Severity: major Classification: Unclassified Reporter: ll...@astute.biz Hardware: PC Status: NEW Version: 1.1 Component: general Product: Fop 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 org.apache.xmlgraphics fop 1.1 avalon-framework-api org.apache.avalon.framework avalon-framework-impl org.apache.avalon.framework avalon-framework avalon-framework-api 4.2.0 avalon-framework avalon-framework-impl 4.2.0 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54061] NullPointer Exception in org.apache.fop.fo.FObj
https://issues.apache.org/bugzilla/show_bug.cgi?id=54061 --- Comment #11 from Robert Meyer --- Created attachment 29539 --> https://issues.apache.org/bugzilla/attachment.cgi?id=29539&action=edit Smaller FO to reproduce the nullpointer I have attached a smaller example which reproduces the nullpointer reported in the original post when using the -r flag. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54081] New: Properly tag hyphenated words
https://issues.apache.org/bugzilla/show_bug.cgi?id=54081 Priority: P2 Bug ID: 54081 Assignee: fop-dev@xmlgraphics.apache.org Summary: Properly tag hyphenated words Severity: normal Classification: Unclassified OS: All Reporter: vhenneb...@gmail.com Hardware: All Status: NEW Version: all Component: pdf Product: Fop If a hyphenated word is stored as-is in the PDF output, a screen reader will read it differently to when it is not hyphenated. This can result into incomprehensible text. To fix that problem, a hyphenated word should properly be tagged as such. This can be done in 2 ways. The first possibility is to add an 'ActualText' entry to the property list of the corresponding marked-content sequence. Its value would basically be the whole text minus the last hyphen character. The second possibility is to replace the last hyphen with a soft hyphen character, which will be recognized by screen readers such that the split word will be read as one. This will work only if the font has a glyph for the soft hyphen character. The latter possibility is the recommended way to handle hyphenated words. The former can be implemented as a fallback for when there is no available glyph for the soft hyphen, or when the hyphenation character is not actually a hyphen (this can be customized through the hyphenation-character property). -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54061] NullPointer Exception in org.apache.fop.fo.FObj
https://issues.apache.org/bugzilla/show_bug.cgi?id=54061 --- Comment #10 from Pascal Sancho --- (In reply to comment #8) > there is a FOP option to create a FO file indented, which indicates the > position of errors based on the file indented? FOP does not produce FO, this is the matter of XSLT engine. For convenience, FOP comes with xalan. See [1] to tweak your XSLT if you use xalan. [1] http://xml.apache.org/xalan-j/usagepatterns.html#outputprops -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54061] NullPointer Exception in org.apache.fop.fo.FObj
https://issues.apache.org/bugzilla/show_bug.cgi?id=54061 --- Comment #9 from Robert Meyer --- Created attachment 29535 --> https://issues.apache.org/bugzilla/attachment.cgi?id=29535&action=edit Attached a version of the FO which has been formatted. I ran through the FO using xml_pp (pretty print) in Linux to create the attached output. This probably isn't helpful to you as you are using XSLT and is likely to change. The other alternative may be to use something like: ... This way you can check to see if the data exists before adding the table. With regard to outputting formatted FO, I am not sure on that but maybe someone else will know. Glen, with regard to adding a smaller example, i'll see if I can replicate the same behaviour by creating a table with an empty table-body. If so, i'll upload that when I get a chance. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54061] NullPointer Exception in org.apache.fop.fo.FObj
https://issues.apache.org/bugzilla/show_bug.cgi?id=54061 --- Comment #8 from spao --- (In reply to comment #6) > Hi, > > Initially I tried going through the code and implementing the fix you > suggested which does appear to be incorrect in the source, but unfortunately > it trips up later on with another null pointer exception. I then put in a > check for that to avoid it but I got a further NoSuchElement exception. It > was at this stage I looked at the FO and the validation warnings I tried to > circumvent by using the -r flag. It appears there is a lot wrong with the > file. The warnings / errors are all like the following: > > "fo:table-body" is missing child elements. Required content model: marker* > (table-row+|table-cell+) (See position 895:37) > > After looking through the FO there were numerous instances of tables with > table-body elements with no contents or similarly declared empty > table-headers. These are rules which both FOP and the FO must abide [1], so > I can see why FOP is falling over. I went through the FO removing all of the > blank tables with the problematic body and header's elements. After I had > done this I could successfully render the document. It may not be how it was > intended to look, but it did render. > > In order to get yours to render, I would recommend going through the FO file > and instead of removing the tables, add the necessary missing table-rows / > table-cells if these are used for formatting purposes. This should prevent > FOP from complaining whilst allowing you to render the document correctly. > > [1] http://www.w3.org/TR/xsl/#fo_table-body > > In the meantime, this bug can relate to the incorrect sublings usage you > specified in your original post. The fact is that I wanted to avoid to fix errors (example: fo: table-body missing childs) in the FO because I thought that strictValidation = false ignored them. But since FOP gave me NullPointer, so I proceeded as you said, that I corrected all errors as specified in http://www.w3.org/TR/xsl/, but this cost me a lot of trouble because the FO file is generated on a few lines, but very long, and therefore the error is of the type: "see position 3:56753"! But how do I find the column 56753? and after that I found it how do I compare it with my XSLT file that is indented? All this to say: there is a FOP option to create a FO file indented, which indicates the position of errors based on the file indented? Thanks a lot -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54061] NullPointer Exception in org.apache.fop.fo.FObj
https://issues.apache.org/bugzilla/show_bug.cgi?id=54061 --- Comment #7 from Glenn Adams --- in any case, no matter how broken the FO input, FOP shouldn't be throwing NPEs, so there is an FOP bug to fix... the reporter needs to find the minimal (reduced) test that produces the NPE -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54061] NullPointer Exception in org.apache.fop.fo.FObj
https://issues.apache.org/bugzilla/show_bug.cgi?id=54061 --- Comment #6 from Robert Meyer --- Hi, Initially I tried going through the code and implementing the fix you suggested which does appear to be incorrect in the source, but unfortunately it trips up later on with another null pointer exception. I then put in a check for that to avoid it but I got a further NoSuchElement exception. It was at this stage I looked at the FO and the validation warnings I tried to circumvent by using the -r flag. It appears there is a lot wrong with the file. The warnings / errors are all like the following: "fo:table-body" is missing child elements. Required content model: marker* (table-row+|table-cell+) (See position 895:37) After looking through the FO there were numerous instances of tables with table-body elements with no contents or similarly declared empty table-headers. These are rules which both FOP and the FO must abide [1], so I can see why FOP is falling over. I went through the FO removing all of the blank tables with the problematic body and header's elements. After I had done this I could successfully render the document. It may not be how it was intended to look, but it did render. In order to get yours to render, I would recommend going through the FO file and instead of removing the tables, add the necessary missing table-rows / table-cells if these are used for formatting purposes. This should prevent FOP from complaining whilst allowing you to render the document correctly. [1] http://www.w3.org/TR/xsl/#fo_table-body In the meantime, this bug can relate to the incorrect sublings usage you specified in your original post. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54061] NullPointer Exception in org.apache.fop.fo.FObj
https://issues.apache.org/bugzilla/show_bug.cgi?id=54061 spao changed: What|Removed |Added Status|NEEDINFO|NEW -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54061] NullPointer Exception in org.apache.fop.fo.FObj
https://issues.apache.org/bugzilla/show_bug.cgi?id=54061 --- Comment #5 from spao --- Created attachment 29534 --> https://issues.apache.org/bugzilla/attachment.cgi?id=29534&action=edit FO File that generates the error -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54061] NullPointer Exception in org.apache.fop.fo.FObj
https://issues.apache.org/bugzilla/show_bug.cgi?id=54061 --- Comment #4 from spao --- Created attachment 29533 --> https://issues.apache.org/bugzilla/attachment.cgi?id=29533&action=edit test class to reproduce the error Test Class with main method. Takes as input the FO file and a boolean strictValidation. If strictValidation = true gives a standard error of grammar, if it is false instead gives NullPointer on FObj.java -- You are receiving this mail because: You are the assignee for the bug.
[Bug 18801] [PATCH] "visibility" property is not implemented
https://issues.apache.org/bugzilla/show_bug.cgi?id=18801 carsten.pfeif...@gebit.de changed: What|Removed |Added CC||carsten.pfeif...@gebit.de -- You are receiving this mail because: You are the assignee for the bug.
[Bug 18801] [PATCH] "visibility" property is not implemented
https://issues.apache.org/bugzilla/show_bug.cgi?id=18801 --- Comment #3 from carsten.pfeif...@gebit.de --- Ping. Any update on this? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54061] NullPointer Exception in org.apache.fop.fo.FObj
https://issues.apache.org/bugzilla/show_bug.cgi?id=54061 Chris Bowditch changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #3 from Chris Bowditch --- Is that because of confidentially? If so, please replace the sensitive text with a string of XXX or similar. I'm updating this bug to Needs Info status -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54075] Regression introduced in 1401607
https://issues.apache.org/bugzilla/show_bug.cgi?id=54075 Peter Hancock changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Peter Hancock --- Fixed in 1403657 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54075] New: Regression introduced in 1401607
https://issues.apache.org/bugzilla/show_bug.cgi?id=54075 Priority: P2 Bug ID: 54075 Assignee: fop-dev@xmlgraphics.apache.org Summary: Regression introduced in 1401607 Severity: normal Classification: Unclassified OS: Linux Reporter: peter.hanc...@gmail.com Hardware: PC Status: NEW Version: trunk Component: general Product: Fop In AbstractPathOrientedRenderer org.apache.xmlgraphics.util.UnitConv has been replaced by org.apache.fop.util.UnitConv -- You are receiving this mail because: You are the assignee for the bug.
[Bug 54074] page-position="only" in conditional-page-master-reference does not work
https://issues.apache.org/bugzilla/show_bug.cgi?id=54074 --- Comment #4 from ffim...@gmail.com --- Created attachment 29530 --> https://issues.apache.org/bugzilla/attachment.cgi?id=29530&action=edit Last page pdf file -- You are receiving this mail because: You are the assignee for the bug.
