From fop-dev-returnomiller@example.net Mon Sep 01 06:09:26 2008 Return-Path: <fop-dev-returnomiller@example.net> Delivered-To: omiller@example.net Received: (qmail 25421 invoked from network); 1 Sep 2008 06:09:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Sep 2008 06:09:25 -0000 Received: (qmail 69955 invoked by uid 500); 1 Sep 2008 06:09:14 -0000 Delivered-To: omiller@example.net Received: (qmail 69922 invoked by uid 500); 1 Sep 2008 06:09:14 -0000 Mailing-List: contact omiller@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:omiller@example.net> List-Unsubscribe: <mailto:omiller@example.net> List-Post: <mailto:omiller@example.net> List-Id: <fop-dev.xmlgraphics.apache.org> Reply-To: omiller@example.net Delivered-To: mailing list omiller@example.net Received: (qmail 69894 invoked by uid 500); 1 Sep 2008 06:09:14 -0000 Delivered-To: omiller@example.net Received: (qmail 69887 invoked by uid 99); 1 Sep 2008 06:09:14 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 31 Aug 2008 23:09:14 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Sep 2008 06:08:14 +0000 Received: by brutus.apache.org (Postfix, from userid 1007) id D9C34234C1C4; Sun, 31 Aug 2008 23:08:14 -0700 (PDT) From: omiller@example.net To: omiller@example.net Subject: Bug report for Fop [2008/08/31] Message-Id: <omiller@example.net> Date: Sun, 31 Aug 2008 23:08:12 -0700 (PDT) X-Virus-Checked: Checked by ClamAV on apache.org +---------------------------------------------------------------------------+ | Bugzilla Bug ID | | +---------------------------------------------------------------------+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned | | | OPN=Reopened VER=Verified (Skipped Closed/Resolved) | | | +-----------------------------------------------------------------+ | | | Severity: BLK=Blocker CRI=Critical REG=Regression MAJ=Major | | | | MIN=Minor NOR=Normal ENH=Enhancement TRV=Trivial | | | | +-------------------------------------------------------------+ | | | | Date Posted | | | | | +--------------------------------------------------+ | | | | | Description | | | | | | | | 1063|New|Nor|2001-03-21|fop does not handle large fo files | | 3280|New|Nor|2001-08-27|PCL Renderer doesn't work | | 3824|New|Blk|2001-09-25|MIF option with tables | | 4030|New|Nor|2001-10-08|IOException creating Postscript with graphics on S| | 4535|New|Maj|2001-10-31|PCL renderer 1.13 not rendering SVG | | 5010|New|Enh|2001-11-21|Better error reporting needed | | 5124|New|Maj|2001-11-27|fo:block-container is not rendered properly using | | 6305|New|Nor|2002-02-07|Using fo:table-and-caption results in empty output| | 6427|New|Enh|2002-02-13|Adding additional Type 1 fonts problem | | 6997|New|Nor|2002-03-09|[PATCH] Row-spanned row data breaks over a page wi| | 7241|New|Nor|2002-03-19|keep-with-previous, keep-with-next only working on| | 8003|Ass|Maj|2002-04-12|FopImageFactory never releases cached images | | 8463|New|Nor|2002-04-24|SVG clipping in external.fo example doc when rende| | 8767|Ass|Min|2002-05-03|Image and solid colour background rectangle sizes | | 9379|New|Nor|2002-05-24|MIF Renderer generates incorrect MIF code | |10379|New|Enh|2002-07-01|Improvement to FOP Classloader | |12494|New|Nor|2002-09-10|fop produces pdf file which Acrobat Reader refuses| |12610|New|Enh|2002-09-13|[PATCH] onLoad Action for PDF documents or how to | |13586|New|Blk|2002-10-13|fop will not work on linux alpha because jre is br| |13734|New|Nor|2002-10-17|Hyphenation does not work correctly on long string| |14248|New|Enh|2002-11-05|51-page FO example, could be added to the samples | |14352|New|Enh|2002-11-07|It would be nice if FOP could be plugged into popu| |14356|New|Nor|2002-11-07|*NOT* embedding TrueTypeFont in PDF causes Acrobat| |14419|New|Enh|2002-11-10|Implement SourceResolver, Image Resolver | |14529|New|Nor|2002-11-13|SVG url references do not work | |14679|New|Enh|2002-11-19|Pluggable renderers | |14924|New|Nor|2002-11-28|Table disappears when it ends when the page ends | |15020|New|Enh|2002-12-03|Reuse of fo-tree | |16017|Opn|Nor|2003-01-13|Jpeg's and the PDF Serializer | |16130|New|Nor|2003-01-15|PS-Renderer emits lots of redundant moveto's | |16156|New|Nor|2003-01-16|0.20.5rc SVG example does not work | |16713|New|Nor|2003-02-03|Hyphenation error in tables | |17369|New|Nor|2003-02-25|Footnote duplication | |17380|New|Nor|2003-02-25|Batik Component will not recognize feXXXX SVG elem| |17921|New|Nor|2003-03-12|Kerning is broken for standard fonts | |18292|New|Nor|2003-03-24|24 bit PNG not displayed correctly | |18801|New|Nor|2003-04-08|"visibility" property is not implemented | |19228|New|Blk|2003-04-22|[PATCH] Child LayoutContext is null in certain cir| |19341|Ver|Nor|2003-04-26|leader doesn't work since 0.20.5.rc2 | |19695|New|Enh|2003-05-06|[PATCH] Allow fox:destination as child of fox:outl| |19717|New|Enh|2003-05-07|Lets add support for JimiClassesPro.zip to build.x| |19769|Ass|Enh|2003-05-08|Indefinite page size is not implemented | |20280|Ass|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| |20827|New|Enh|2003-06-17|Derive other font styles and weights from normal T| |21265|Opn|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|Maj|2003-07-30|NullPointer Exception in LazyFont with embedded fo| |22450|New|Maj|2003-08-15|Unterminated iteration in JPEGReader class | |22627|Opn|Nor|2003-08-21|Update mirror/download page HEADER & README (was [| |24148|New|Nor|2003-10-27|Kerning upsets text-align="end" | |24171|New|Nor|2003-10-28|[PATCH] 1st Attempt at Whole Site PDF | |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 | |24804|New|Nor|2003-11-18|SVG Text to PS Output generates incorrect outlines| |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| |25411|New|Nor|2003-12-10|[WARNING] Error while constructing image from XML | |25432|Ass|Maj|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 | |26848|New|Nor|2004-02-11|PNG images using JIMI instead JAI | |27107|New|Maj|2004-02-20|TTF Reader fails | |27727|New|Maj|2004-03-17|problem displaying Japanese fonts in PDF. | |27890|New|Min|2004-03-24|fop.sh doesn't set exit status | |29632|New|Maj|2004-06-17|Rendered reads fonts from disk everytime it render| |29711|New|Maj|2004-06-21|[PATCH] LineArea.canBreakMidWord() RFC3066 fix | |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. | |31796|New|Cri|2004-10-20|Fop: Pdf generation dowsn`t work with j2sdk 1.5 | |32054|New|Enh|2004-11-04|Pluggable area creation: AreaFactory | |32100|Ass|Enh|2004-11-07|FOP "Starter Documents" | |32107|New|Cri|2004-11-07|Move FOP wiki to secure | |32201|Opn|Enh|2004-11-12|please, provide a manpage | |32789|New|Cri|2004-12-21|Arabic words are broken for rendering PDF from FOP| |32970|New|Cri|2005-01-06|Sticking words in generated PDF document | |33174|New|Nor|2005-01-20|An unrecognized token'NaN' was found when opening | |34355|New|Cri|2005-04-07|BufferOverflowException when running SVG2PDF on hu| |35184|New|Trv|2005-06-02|Error while loading image http://xxx.xx.x/yyyy.tif| |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 | |35948|New|Enh|2005-07-31|pre-patch for FOrayFont adaptation to Fop | |36000|Ver|Maj|2005-08-03|PDF page margins larger, different than PS renderi| |36011|New|Nor|2005-08-04|Setting word-spacing on justified blocks removes j| |36238|Ass|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|Opn|Min|2005-08-29|FOP hyphenation splits consecutive digits onto sep| |36533|Opn|Nor|2005-09-07|Incorrect ipd and twsadjust settings | |36935|New|Blk|2005-10-05|table-layout="fixed" and width="auto", but auto-la| |36977|New|Nor|2005-10-09|[PATCH]TextLayoutManager CJK line break | |37108|New|Nor|2005-10-16|Patch for 0.20.5 to work with jdk1.5 | |37114|New|Min|2005-10-17|No error message on illegal/unknown values on a pr| |37116|New|Enh|2005-10-17|ESC POS Renderer | |37136|Opn|Nor|2005-10-18|external-graphic dimensions and rendering | |37236|Ass|Nor|2005-10-25|[PATCH] Fix gradients and patterns | |37305|Ass|Nor|2005-10-30|Added deviceDPI to PDFDocumentGraphics2D | |37505|New|Cri|2005-11-15|SEVERE FOP Exceptions should be thrown! | |37579|Ass|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)| |38264|Ass|Nor|2006-01-13|Hyphenation does not play well with preserved line| |38639|Inf|Maj|2006-02-14|PDF not opening | |38821|Opn|Nor|2006-03-01|The manifest file no longer has a Class-Path entry| |38862|New|Maj|2006-03-06|No ImageReader for this type of image | |38880|Ass|Nor|2006-03-07|Right border on fo:inline missing when hyphenate=t| |39034|New|Nor|2006-03-20|page-number-citation : the text after overlaps the| |39118|Ass|Nor|2006-03-27|[PATCH] Handling of page-number-citation-last | |39184|New|Nor|2006-04-03|soft page break on new line | |39215|New|Nor|2006-04-05|[PATCH] To render GIF external images in RTF outpu| |39261|New|Min|2006-04-10|Rasterized paints upside down if coordinate system| |39293|New|Enh|2006-04-13|FOP can't support bold,italic for chinese/other mu| |39412|Ass|Nor|2006-04-26|wrong URL referred from FOP: Bugs and Other Tracka| |39422|New|Nor|2006-04-27|[PATCH] Fop fails to render non-ascii characters i| |39725|New|Maj|2006-06-05|page-position="last" and spans doesn't output all | |39777|Ass|Enh|2006-06-11|[PATCH] GSoC: floats implementation | |39840|Ass|Cri|2006-06-20|Multi page table fails with an endless loop error | |39927|Ass|Nor|2006-06-28|Building FOP with GCJ | |39968|New|Nor|2006-07-05|Absolutely positioned block-container affects the | |40112|New|Nor|2006-07-26|keep-with-previous.within-page not working | |40271|Ass|Nor|2006-08-17|[PATCH] auto table layout -- dirty draft | |40288|Opn|Nor|2006-08-18|<base> url requires "/", failes otherwise | |40464|New|Nor|2006-09-11|Improve handling of OpenType fonts | |40465|New|Nor|2006-09-11|Obtain some OpenType fonts for testing | |40468|New|Nor|2006-09-11|Use OpenType fonts from the STIX fonts project? | |40529|New|Nor|2006-09-17|[PATCH] Possible bug in PSTextRenderer | |40557|Ass|Nor|2006-09-20|PDF encryption and Acrobat 5 | |40676|Ass|Enh|2006-10-04|png graphics are expanded/uncompressed in pdf caus| |40699|New|Nor|2006-10-06|Invalid PDF for certain numerical values in SVG li| |40798|New|Maj|2006-10-19|page-position="last" doesn't work for 1 page docum| |40830|Inf|Nor|2006-10-27|Pb rendering SVG in fo:instream-foreign-object wit| |41062|New|Nor|2006-11-28|Defect reading hyphenation patterns | |41122|New|Nor|2006-12-07|[PATCH] flow-map 1.1 support | |41149|Ass|Nor|2006-12-11|PNG causes NPE for RTF output | |41251|Opn|Nor|2006-12-28|ArrayIndexOutOfBoundsException in multithreading e| |41272|Opn|Nor|2006-12-31|Memory problem in 0.93 | |41295|New|Min|2007-01-04|Examples cause fatals and excessive warnings | |41300|New|Min|2007-01-05|FATAL error raised for proportional-column-width()| |41377|Ver|Blk|2007-01-16|Alignment (end, right) does not work in table-cell| |41379|New|Maj|2007-01-16|VerifyError on FopFactory.newInstance() using Tomc| |41380|New|Min|2007-01-16|Content in tables affecting conditional spacing of| |41389|New|Maj|2007-01-17|Rtf numbered lists without numbers | |41440|Ass|Nor|2007-01-23|PDFSVGHandler causes missing resource bundle | |41443|New|Nor|2007-01-23|[PATCH] FOP can't handle mixed-case hyphenation ex| |41445|Inf|Nor|2007-01-23|no searchable text in pdf for <image xlink:href to| |41633|New|Nor|2007-02-16|*-progression-dimension on inlines not implemented| |41637|New|Nor|2007-02-16|in-line border-end does not always get rendered | |41649|New|Cri|2007-02-16|fop0.93 - Does not generate svg line or svg rectab| |41657|New|Nor|2007-02-19|No support for SVG 1.2 in instream-foreign-object | |41667|New|Nor|2007-02-21|ImageProvider should be overridable in ImageFactor| |41812|New|Trv|2007-03-11|fillRect writes wrong command | |41822|New|Nor|2007-03-12|Generated example from \examples\fo\basic\list.fo | |41894|New|Nor|2007-03-19|fo:block-container: percentage-lengths + width/hei| |41918|New|Nor|2007-03-21|Thin Lines in AWTRenderer are not drawn | |41942|New|Nor|2007-03-25|fo:leader elements are ignored when converted to R| |41951|New|Nor|2007-03-26|External graphic doesnt size properly with height | |41959|New|Nor|2007-03-27|External links are broken if pdf is encryped | |41978|New|Maj|2007-03-28|Rogue entries on a blank page | |41995|New|Enh|2007-03-30|[PATCH] Barcode Support for AFP Renderer | |41999|New|Nor|2007-03-30|Unassigned code points cause ArrayIndexOutOfBounds| |42028|New|Nor|2007-04-02|Incorrect rendering of GIF images | |42034|New|Nor|2007-04-03|basic-link doesn't cover all text inside | |42049|New|Nor|2007-04-04|RTF (and PDF) tables incorrectly handle margin-lef| |42136|New|Nor|2007-04-16|PDFDocumentGraphics2D.translate() does not work co| |42162|New|Nor|2007-04-18|hyphenation inside block in FOP works only for pur| |42306|New|Nor|2007-05-01|[PATCH] AWT Viewer does not track page numbers in | |42307|New|Cri|2007-05-01|[PATCH] Java2d renderers render arabic text incorr| |42330|New|Nor|2007-05-03|Tibetan characters not rendered correctly in PDF | |42352|New|Nor|2007-05-08|Problem with tiff gray render | |42374|New|Nor|2007-05-09|List label and bodyindentation incorrect in RTF | |42380|New|Nor|2007-05-10|FOP chokes on jar-embedded class path | |42501|New|Nor|2007-05-23|basic-link not sizing correctly for external-graph| |42577|Ass|Nor|2007-06-04|font-stretch [PATCH] | |42600|New|Nor|2007-06-06|can not create page break in RTF | |42601|New|Nor|2007-06-06|Image/text misalignment inside before-region table| |42616|Opn|Nor|2007-06-08|fop bash script still broken under cygwin when cur| |42617|New|Nor|2007-06-08|DOM tree cannot be built for a SVG graphic embedde| |42685|Ass|Nor|2007-06-17|Printer restarts after sucessfull printing Postscr| |42769|New|Nor|2007-06-28|Wrong border resolution in a table when there are | |42779|Ass|Nor|2007-06-29|page-position and force-page-count with different | |42808|New|Nor|2007-07-04|table footer overflows region-body area without wa| |42845|Inf|Nor|2007-07-10|Printing error. Prints charater+1. | |42861|Ass|Nor|2007-07-11|[PATCH] Font detection only works for first docume| |42868|New|Nor|2007-07-12|font-weight on custom fonts | |43166|New|Nor|2007-08-20|unclosed border on nested inlines | |43226|Inf|Maj|2007-08-28|images in pdf are not displayed correctly with 0.9| |43237|New|Nor|2007-08-29|IndexOutOfBoundsException | |43357|New|Min|2007-09-11|PDFGraphics2D addImage method: image in PDF look a| |43416|New|Nor|2007-09-18|content not rendered after a break-before="column"| |43474|Ass|Nor|2007-09-25|wrap-option="wrap" doesn't work | |43506|New|Nor|2007-09-28|NPE using a Tiff Image | |43525|New|Nor|2007-10-01|"background-position" shorthand is not processed p| |43570|New|Cri|2007-10-08|field ATTRIB_ROW_PADDING not found | |43651|New|Nor|2007-10-18|NPE without manually clearing image cache | |43722|New|Nor|2007-10-29|arabic character isssue | |43739|New|Nor|2007-10-30|PDF table of contents generated with incorrect pag| |43808|New|Cri|2007-11-07|Apache FOP in a Servlet fails to work after upgrad| |43844|New|Maj|2007-11-12|Extra blank lines added upon weird combinations of| |43940|New|Min|2007-11-22|Faster method for double formatting | |43962|New|Nor|2007-11-26|OutOfMemoryError while auto-detecting fonts | |44023|New|Nor|2007-12-05|An empty fo:block artificially breaks a block-stac| |44024|Ass|Nor|2007-12-05|About AFP renderer Issues when i try to using Aria| |44160|Ass|Cri|2008-01-02|IndexOutOfBoundsException when creating pdf | |44190|New|Cri|2008-01-09|<fo:block span="none"> : textblock is missing on l| |44320|New|Nor|2008-01-29|Missing before/after border when break set on a ta| |44324|New|Nor|2008-01-29|vertical-align or baseline-shift In table-cells ca| |44328|New|Nor|2008-01-30|widows not respected when linefeed-treatment="pres| |44358|New|Maj|2008-02-05|OufOfMem | |44393|Opn|Nor|2008-02-11|Wrong fo.Constant values used for break class | |44412|Inf|Nor|2008-02-13|Missing border-after when break-after set on a blo| |44434|New|Cri|2008-02-15|FO java Memory Error | |44452|New|Cri|2008-02-19|last upgrades don't render older fop xml files | |44460|Ass|Enh|2008-02-21|[PATCH] PDF Embedded files implementation | |44489|Ass|Enh|2008-02-26|AFP Renderer: Implement break-out mechanism to sup| |44490|Ass|Nor|2008-02-26|AFP Renderer: Support for clipping is missing | |44507|New|Nor|2008-02-29|PCL Renderer doesn't clip background images | |44545|Inf|Nor|2008-03-06|Keep together do not work correctly on spanning ta| |44616|New|Nor|2008-03-17|Merging algorithm for tables properly works only f| |44634|Ass|Enh|2008-03-19|implement show-destination for fo:basic-link | |44744|New|Nor|2008-04-03|PDFGraphics2D.drawString(AttributedCharacterIterat| |44826|New|Nor|2008-04-15|last-page master reference interfered with span al| |44885|Ass|Enh|2008-04-27|fo:inline-container implementation | |44920|Ass|Nor|2008-05-02|nested, multi-page tables and keep-with-previous | |45027|Inf|Nor|2008-05-18|Color 'blue' does not render correctly when 'fo:ex| |45047|Ass|Nor|2008-05-20|Fixed row height not taken into account if the row| |45070|Ass|Nor|2008-05-23|Spurious WARNING on span="inherit" | |45079|Ass|Nor|2008-05-27|multi page table with marker | |45097|Ass|Nor|2008-05-29|Questionable white-space-treatment behavior | |45104|New|Nor|2008-05-30|Possible Thread Safety Problem in FOP 0.93 | |45113|Ass|Enh|2008-06-01|[PATCH] Adding PDF Launch Action | |45134|Ass|Nor|2008-06-05|FOP unwarranted page split on table with numbre-ro| |45159|New|Nor|2008-06-07|fop buzzed on footnotes near page break | |45237|Ass|Nor|2008-06-19|Call order of FOEventHandler method is incorrect | |45306|Ass|Nor|2008-06-29|fo:instream-foreign-object in fo:marker does not w| |45307|New|Nor|2008-06-29|fo:block-container height issue | |45342|New|Nor|2008-07-04|AFP Renderer does not properly handle AFP fonts wi| |45351|Ass|Nor|2008-07-07|Unnecessary hyphenation, swallowed characters | |45366|New|Enh|2008-07-08|Unable to create column break in RTF using FOP | |45390|New|Nor|2008-07-13|PDF Extensions - Prototype | |45454|New|Nor|2008-07-22|Investigate the adoption of Apache Commons CLI | |45503|New|Maj|2008-07-30|Cannot find font if font family name contains spac| |45604|Inf|Nor|2008-08-08|Duplicate prints | |45616|New|Nor|2008-08-11|OpenOffice.org display table incorrectly | |45702|Ass|Nor|2008-08-28|Forced break-after and/or space-after causes unres| |45715|New|Nor|2008-08-30|break-before not respected on blocks nested in inl| +-----+---+---+----------+--------------------------------------------------+ | Total 248 bugs | +---------------------------------------------------------------------------+ From fop-dev-returnomiller@example.net Mon Sep 01 08:10:58 2008 Return-Path: <fop-dev-returnomiller@example.net> Delivered-To: omiller@example.net Received: (qmail 95239 invoked from network); 1 Sep 2008 08:10:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Sep 2008 08:10:58 -0000 Received: (qmail 94621 invoked by uid 500); 1 Sep 2008 08:10:55 -0000 Delivered-To: omiller@example.net Received: (qmail 94597 invoked by uid 500); 1 Sep 2008 08:10:55 -0000 Mailing-List: contact omiller@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:omiller@example.net> List-Unsubscribe: <mailto:omiller@example.net> List-Post: <mailto:omiller@example.net> List-Id: <fop-dev.xmlgraphics.apache.org> Reply-To: omiller@example.net Delivered-To: mailing list omiller@example.net Received: (qmail 94586 invoked by uid 99); 1 Sep 2008 08:10:55 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Sep 2008 01:10:55 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Sep 2008 08:10:06 +0000 Received: by brutus.apache.org (Postfix, from userid 33) id 9BA74234C1C3; Mon, 1 Sep 2008 01:10:36 -0700 (PDT) From: omiller@example.net To: omiller@example.net Subject: DO NOT REPLY [Bug 45702] Forced break-after and/or space-after causes unresolved page-number-citations X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: newchanged X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Fop X-Bugzilla-Component: page-master/layout X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: omiller@example.net X-Bugzilla-Status: ASSIGNED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: omiller@example.net X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: In-Reply-To: <omiller@example.net/bugzilla/> References: <omiller@example.net/bugzilla/> Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Message-Id: <omiller@example.net> Date: Mon, 1 Sep 2008 01:10:36 -0700 (PDT) X-Virus-Checked: Checked by ClamAV on apache.org https://issues.apache.org/bugzilla/show_bug.cgi?id=45702 --- Comment #10 from Patrice ROSNET <omiller@example.net> 2008-09-01 01:10:36 PST --- (In reply to comment #3) > Even stranger, in my local sandbox, there is one set of IDs correctly resolved: > those of the page-sequences. All the others still remain unresolved. If that > doesn't happen in your case, I guess I'll also have to look to add that change > for page-sequences to FOP Trunk. > No problem with ID of page-sequences, IDs are correctly resolved -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From fop-dev-returnomiller@example.net Mon Sep 01 21:10:38 2008 Return-Path: <fop-dev-returnomiller@example.net> Delivered-To: omiller@example.net Received: (qmail 6531 invoked from network); 1 Sep 2008 21:10:38 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Sep 2008 21:10:38 -0000 Received: (qmail 32630 invoked by uid 500); 1 Sep 2008 21:10:35 -0000 Delivered-To: omiller@example.net Received: (qmail 32617 invoked by uid 500); 1 Sep 2008 21:10:35 -0000 Mailing-List: contact omiller@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:omiller@example.net> List-Unsubscribe: <mailto:omiller@example.net> List-Post: <mailto:omiller@example.net> List-Id: <fop-dev.xmlgraphics.apache.org> Reply-To: omiller@example.net Delivered-To: mailing list omiller@example.net Received: (qmail 32606 invoked by uid 99); 1 Sep 2008 21:10:35 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Sep 2008 14:10:35 -0700 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of omiller@example.net designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO kuber.nabble.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Sep 2008 21:09:37 +0000 Received: from isper.nabble.com ([83.161.120.155]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from <omiller@example.net>) id 1KaGf1-00038K-Or for omiller@example.net; Mon, 01 Sep 2008 14:10:07 -0700 Message-ID: <omiller@example.net> Date: Mon, 1 Sep 2008 14:10:07 -0700 (PDT) From: Philip V <omiller@example.net> To: omiller@example.net Subject: [trunk] - Build Fail MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: omiller@example.net X-Virus-Checked: Checked by ClamAV on apache.org Hi, I just updated my version of trunk and was unable to do a build... BUILD FAILED java.lang.UnsupportedOperationException: Saxon cannot write a DOMResult unless s axon9-dom.jar is on the omiller@example.net(SerializerFactory.ja va:200) at net.sf.saxon.expr.XPathContextMinor.changeOutputDestination(XPathCont extMinor.java:402) at net.sf.saxon.Controller.transformDocument(Controller.java:1720) at net.sf.saxon.Controller.transform(Controller.java:1559) at org.apache.fop.tools.EventProducerCollectorTask.updateTranslationFile (EventProducerCollectorTask.java:113) at org.apache.fop.tools.EventProducerCollectorTask.execute(EventProducer CollectorTask.java:79) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.jav a:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:357) at org.apache.tools.ant.Target.performTasks(Target.java:385) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337) at org.apache.tools.ant.Project.executeTarget(Project.java:1306) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExe cutor.java:41) at org.apache.tools.ant.Project.executeTargets(Project.java:1189) at org.apache.tools.ant.Main.runBuild(Main.java:758) at org.apache.tools.ant.Main.startAnt(Main.java:217) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104) -- View this message in context: http://www.nabble.com/-trunk----Build-Fail-tp19260761p19260761.html Sent from the FOP - Dev mailing list omiller@example.net. From fop-dev-returnomiller@example.net Mon Sep 01 21:21:14 2008 Return-Path: <fop-dev-returnomiller@example.net> Delivered-To: omiller@example.net Received: (qmail 8936 invoked from network); 1 Sep 2008 21:21:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Sep 2008 21:21:14 -0000 Received: (qmail 40829 invoked by uid 500); 1 Sep 2008 21:21:11 -0000 Delivered-To: omiller@example.net Received: (qmail 40812 invoked by uid 500); 1 Sep 2008 21:21:11 -0000 Mailing-List: contact omiller@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:omiller@example.net> List-Unsubscribe: <mailto:omiller@example.net> List-Post: <mailto:omiller@example.net> List-Id: <fop-dev.xmlgraphics.apache.org> Reply-To: omiller@example.net Delivered-To: mailing list omiller@example.net Received: (qmail 40801 invoked by uid 99); 1 Sep 2008 21:21:11 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Sep 2008 14:21:11 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [83.161.120.155] (HELO harold.telenet-ops.be) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Sep 2008 21:20:12 +0000 Received: from localhost (localhost.localdomain [83.161.120.155]) by harold.telenet-ops.be (Postfix) with SMTP id BFE3030011 for <omiller@example.net>; Mon, 1 Sep 2008 23:20:40 +0200 (CEST) Received: from [83.161.120.155] (78-20-245-8.access.telenet.be [83.161.120.155]) by harold.telenet-ops.be (Postfix) with ESMTP id AFA7E30014 for <omiller@example.net>; Mon, 1 Sep 2008 23:20:40 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v753.1) In-Reply-To: <omiller@example.net> References: <omiller@example.net> <omiller@example.net> <omiller@example.net> <omiller@example.net> Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Message-Id: <omiller@example.net> Content-Transfer-Encoding: quoted-printable From: Andreas Delmelle <omiller@example.net> Subject: Re: I need fo:retrieve-table-marker example or how to implement continued label in FOP-95? Date: Mon, 1 Sep 2008 23:20:29 +0200 To: omiller@example.net X-Mailer: Apple Mail (2.753.1) X-Virus-Checked: Checked by ClamAV on apache.org On Sep 1, 2008, at 23:02, Andreas Delmelle wrote: (Moving this to fop-dev@) > On Sep 1, 2008, at 22:42, Jean-Fran=E7ois El Fouly wrote: >> Hhmm... I've been quickly through the code and my first impression =20= >> is that it IS implemented. > > Not really, I'm afraid. I have prepared the implementation a while =20 > ago. That much is true. FOP simply does nothing with a retrieve-=20 > table-marker node, but the node is created and the properties =20 > parsed. Only in layoutmgr.LayoutManagerMapping, you will notice =20 > that the RetrieveTableMarker generates no LayoutManager yet. > >> I've set up a simple test case and, going through the stack trace, =20= >> I guess it could be a simple bug fix, something like a bad or =20 >> insufficient test in TablePart.java > > Oh, rest assured, it's going to take a bit more thought and =20 > effort... ;-) To spare some time looking, I see one issue that may turn out to be =20 quite a challenge. One significant benefit is that it operates on the same fo:markers, =20 so little work there, and it may even give you some ideas on how to =20 solve it for the table-case, however... If you follow what happens during regular marker-retrieval, you'll =20 notice that the resolution depends on the markers having been added =20 to the page-viewport. This happens in the addAreas() phase. Later, when the page is =20 finalized, the static-content is added, and at that point the markers =20= are readily available. For a table-header (or -footer), there will be an additional =20 difficulty, because at the point where we generate the base element =20 list, the markers will not have been processed, so we cannot really =20 depend on that same mechanism... Strictly speaking, we might also end =20= up with borderline cases, where the table-header's height varies from =20= page to page, depending on the content retrieved in the marker. Not =20 sure, but the table-code may need some work to cater for this. Just so you know what you're getting yourself into. ;-) Then again, we're here for you, if you get stuck. Cheers Andreas From fop-dev-returnomiller@example.net Mon Sep 01 21:29:45 2008 Return-Path: <fop-dev-returnomiller@example.net> Delivered-To: omiller@example.net Received: (qmail 13847 invoked from network); 1 Sep 2008 21:29:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Sep 2008 21:29:45 -0000 Received: (qmail 49031 invoked by uid 500); 1 Sep 2008 21:29:43 -0000 Delivered-To: omiller@example.net Received: (qmail 49002 invoked by uid 500); 1 Sep 2008 21:29:43 -0000 Mailing-List: contact omiller@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:omiller@example.net> List-Unsubscribe: <mailto:omiller@example.net> List-Post: <mailto:omiller@example.net> List-Id: <fop-dev.xmlgraphics.apache.org> Reply-To: omiller@example.net Delivered-To: mailing list omiller@example.net Received: (qmail 48990 invoked by uid 99); 1 Sep 2008 21:29:43 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Sep 2008 14:29:43 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [83.161.120.155] (HELO winston.telenet-ops.be) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Sep 2008 21:28:44 +0000 Received: from localhost (localhost.localdomain [83.161.120.155]) by winston.telenet-ops.be (Postfix) with SMTP id BC5D6A002E for <omiller@example.net>; Mon, 1 Sep 2008 23:29:03 +0200 (CEST) Received: from [83.161.120.155] (78-20-245-8.access.telenet.be [83.161.120.155]) by winston.telenet-ops.be (Postfix) with ESMTP id B1A47A0029 for <omiller@example.net>; Mon, 1 Sep 2008 23:29:03 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v753.1) In-Reply-To: <omiller@example.net> References: <omiller@example.net> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <omiller@example.net> Content-Transfer-Encoding: 7bit From: Andreas Delmelle <omiller@example.net> Subject: Re: [trunk] - Build Fail Date: Mon, 1 Sep 2008 23:28:52 +0200 To: omiller@example.net X-Mailer: Apple Mail (2.753.1) X-Virus-Checked: Checked by ClamAV on apache.org On Sep 1, 2008, at 23:10, Philip V wrote: > > Hi, I just updated my version of trunk and was unable to do a build... > > BUILD FAILED > java.lang.UnsupportedOperationException: Saxon cannot write a > DOMResult > unless saxon9-dom.jar is on the classpath This is due to the new event-handling framework that has been added after 0.95. The step in the build process that generates the resource files for the various messages, seems to require a writable DOM implementation. As the message indicates, Saxon offers such an implementation in a separate JAR, which needs to be added to the classpath when building FOP Trunk. Andreas From fop-dev-returnomiller@example.net Mon Sep 01 21:59:35 2008 Return-Path: <fop-dev-returnomiller@example.net> Delivered-To: omiller@example.net Received: (qmail 35126 invoked from network); 1 Sep 2008 21:59:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Sep 2008 21:59:35 -0000 Received: (qmail 70505 invoked by uid 500); 1 Sep 2008 21:59:33 -0000 Delivered-To: omiller@example.net Received: (qmail 70476 invoked by uid 500); 1 Sep 2008 21:59:32 -0000 Mailing-List: contact omiller@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:omiller@example.net> List-Unsubscribe: <mailto:omiller@example.net> List-Post: <mailto:omiller@example.net> List-Id: <fop-dev.xmlgraphics.apache.org> Reply-To: omiller@example.net Delivered-To: mailing list omiller@example.net Received: (qmail 70465 invoked by uid 99); 1 Sep 2008 21:59:32 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Sep 2008 14:59:32 -0700 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of omiller@example.net designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO kuber.nabble.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Sep 2008 21:58:34 +0000 Received: from isper.nabble.com ([83.161.120.155]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from <omiller@example.net>) id 1KaHQN-0004Tq-GH for omiller@example.net; Mon, 01 Sep 2008 14:59:03 -0700 Message-ID: <omiller@example.net> Date: Mon, 1 Sep 2008 14:59:03 -0700 (PDT) From: Philip V <omiller@example.net> To: omiller@example.net Subject: Re: [trunk] - Build Fail In-Reply-To: <omiller@example.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: omiller@example.net References: <omiller@example.net> <omiller@example.net> X-Virus-Checked: Checked by ClamAV on apache.org Thank Andreas, Wasn't sure if the class was supposed to be referenced in the ant build file. I am all set now. Thanks, Phil Andreas Delmelle-2 wrote: > > On Sep 1, 2008, at 23:10, Philip V wrote: > >> >> Hi, I just updated my version of trunk and was unable to do a build... >> >> BUILD FAILED >> java.lang.UnsupportedOperationException: Saxon cannot write a >> DOMResult >> unless saxon9-dom.jar is on the classpath > > This is due to the new event-handling framework that has been added > after 0.95. > The step in the build process that generates the resource files for > the various messages, seems to require a writable DOM implementation. > > As the message indicates, Saxon offers such an implementation in a > separate JAR, which needs to be added to the classpath when building > FOP Trunk. > > > Andreas > > -- View this message in context: http://www.nabble.com/-trunk----Build-Fail-tp19260761p19261273.html Sent from the FOP - Dev mailing list omiller@example.net. From fop-dev-returnomiller@example.net Tue Sep 02 07:41:15 2008 Return-Path: <fop-dev-returnomiller@example.net> Delivered-To: omiller@example.net Received: (qmail 39243 invoked from network); 2 Sep 2008 07:41:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Sep 2008 07:41:15 -0000 Received: (qmail 77851 invoked by uid 500); 2 Sep 2008 07:41:12 -0000 Delivered-To: omiller@example.net Received: (qmail 77838 invoked by uid 500); 2 Sep 2008 07:41:12 -0000 Mailing-List: contact omiller@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:omiller@example.net> List-Unsubscribe: <mailto:omiller@example.net> List-Post: <mailto:omiller@example.net> List-Id: <fop-dev.xmlgraphics.apache.org> Reply-To: omiller@example.net Delivered-To: mailing list omiller@example.net Received: (qmail 77827 invoked by uid 99); 2 Sep 2008 07:41:12 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Sep 2008 00:41:12 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [83.161.120.155] (HELO tux17.hoststar.ch) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Sep 2008 07:40:14 +0000 Received: from [83.161.120.155] (adsl-84-227-53-115.adslplus.ch [83.161.120.155]) (authenticated bits=0) by tux17.hoststar.ch (8.13.6/8.12.11) with ESMTP id m827bYRW002675 for <omiller@example.net>; Tue, 2 Sep 2008 09:37:34 +0200 Date: Tue, 02 Sep 2008 09:37:34 +0200 From: Jeremias Maerki <omiller@example.net> To: omiller@example.net Subject: Re: I need fo:retrieve-table-marker example or how to implement continued label in FOP-95? In-Reply-To: <omiller@example.net> References: <omiller@example.net> <omiller@example.net> Message-Id: <omiller@example.net> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Becky! ver. 2.47.01 [en] X-Antivirus: avast! (VPS 080901-0, 01.09.2008), Outbound message X-Antivirus-Status: Clean X-Virus-Checked: Checked by ClamAV on apache.org On 01.09.2008 23:20:29 Andreas Delmelle wrote: > On Sep 1, 2008, at 23:02, Andreas Delmelle wrote: >=20 > (Moving this to fop-dev@) >=20 > > On Sep 1, 2008, at 22:42, Jean-Fran=E7ois El Fouly wrote: > >> Hhmm... I've been quickly through the code and my first impression =20 > >> is that it IS implemented. > > > > Not really, I'm afraid. I have prepared the implementation a while =20 > > ago. That much is true. FOP simply does nothing with a retrieve-=20 > > table-marker node, but the node is created and the properties =20 > > parsed. Only in layoutmgr.LayoutManagerMapping, you will notice =20 > > that the RetrieveTableMarker generates no LayoutManager yet. > > > >> I've set up a simple test case and, going through the stack trace, =20 > >> I guess it could be a simple bug fix, something like a bad or =20 > >> insufficient test in TablePart.java > > > > Oh, rest assured, it's going to take a bit more thought and =20 > > effort... ;-) >=20 > To spare some time looking, I see one issue that may turn out to be =20 > quite a challenge. > One significant benefit is that it operates on the same fo:markers, =20 > so little work there, and it may even give you some ideas on how to =20 > solve it for the table-case, however... >=20 > If you follow what happens during regular marker-retrieval, you'll =20 > notice that the resolution depends on the markers having been added =20 > to the page-viewport. > This happens in the addAreas() phase. Later, when the page is =20 > finalized, the static-content is added, and at that point the markers =20 > are readily available. >=20 > For a table-header (or -footer), there will be an additional =20 > difficulty, because at the point where we generate the base element =20 > list, the markers will not have been processed, so we cannot really =20 > depend on that same mechanism... Strictly speaking, we might also end =20 > up with borderline cases, where the table-header's height varies from =20 > page to page, depending on the content retrieved in the marker. Not =20 > sure, but the table-code may need some work to cater for this. Absolutely. At the moment the element list for headers and footers is calculated once (in TableContentLayoutManager) and then used for every break possibility (see TableHFPenaltyPosition). When retrieve-table-markers are used you basically have to recalculate the header and footer element lists for each break position in case the markers change. That's quite a bit of processing effort that is even mostly done in vain since most break positions won't even be used. But since we're still on a total-fit approach, that is necessary. That should improve when Vincent is finished with his revamping of the page breaking process. > Just so you know what you're getting yourself into. ;-) >=20 > Then again, we're here for you, if you get stuck. >=20 > Cheers >=20 > Andreas >=20 Jeremias Maerki From fop-dev-returnomiller@example.net Tue Sep 02 09:21:41 2008 Return-Path: <fop-dev-returnomiller@example.net> Delivered-To: omiller@example.net Received: (qmail 80591 invoked from network); 2 Sep 2008 09:21:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Sep 2008 09:21:41 -0000 Received: (qmail 59548 invoked by uid 500); 2 Sep 2008 09:21:39 -0000 Delivered-To: omiller@example.net Received: (qmail 59535 invoked by uid 500); 2 Sep 2008 09:21:39 -0000 Mailing-List: contact omiller@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:omiller@example.net> List-Unsubscribe: <mailto:omiller@example.net> List-Post: <mailto:omiller@example.net> List-Id: <fop-dev.xmlgraphics.apache.org> Reply-To: omiller@example.net Delivered-To: mailing list omiller@example.net Received: (qmail 59524 invoked by uid 99); 2 Sep 2008 09:21:39 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Sep 2008 02:21:39 -0700 X-ASF-Spam-Status: No, hits=3.8 required=10.0 tests=SPF_PASS,TVD_STOCK1 X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [83.161.120.155] (HELO ns26141.ovh.net) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Sep 2008 09:20:40 +0000 Received: (qmail 16656 invoked from network); 2 Sep 2008 10:49:18 +0200 Received: from unknown (HELO ?83.161.120.155?) (83.161.120.155) by ns26141.ovh.net with SMTP; 2 Sep 2008 10:49:18 +0200 Message-ID: <omiller@example.net> Date: Tue, 02 Sep 2008 11:21:09 +0200 From: =?ISO-8859-1?Q?Jean-Fran=E7ois_El_Fouly?= <omiller@example.net> Reply-To: omiller@example.net MIME-Version: 1.0 To: omiller@example.net Subject: A (long) question on implementing fo:retrieve-table-marker Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org I take as reference: http://www.w3.org/TR/xsl/ To begin with, I've built a simple example / test case related to my customer's needs but fairly based on the one in 83.161.120.155.2: http://www.w3.org/TR/xsl/#d0e14681 This example looks good and though not trivial to understand at first sight, it is a common-sense use of fo:retrieve-table-marker. It has a sort of "conditional row" that is displayed (or not) in the table footer and is defined just after table-body: * <fo:marker marker-class-name="continued"> <fo:table-row> <fo:table-cell> <fo:block>Table continued...</fo:block> </fo:table-cell> </fo:table-row> </fo:marker> * Now if I run my test case against the trunk of FOP I get this error message: *GRAVE: Exception javax.xml.transform.TransformerException: org.apache.fop.fo.ValidationException: file:/D:/Java/fop-0.95beta/test-rtm.fo:533:112: Error(533/112): fo:retrieve-tab le-marker is not a valid child element of fo:table-header. * For the sake of clarity only let's call this a "bug" since *fo-retrieve-table-marker* /is/ a valid child element of *fo:table-header:* http://www.w3.org/TR/xsl/#fo_retrieve-table-marker So let's read the full stack trace and "fix" this by adding one more condition in *org.apache.fop.fo.flow.table.TablePart.validateChildNode()*. The next step is where I'm puzzled and don't know how to proceed since the W3C recommendation and the example they give seem inconsistent with each other, while the error message FOP returns seems consistent with the recommendation: *GRAVE: Exception javax.xml.transform.TransformerException: org.apache.fop.fo.ValidationException: "{http://www.w3.org/1999/XSL/Format}table-row" is not a valid child of "fo:mark er"! (See position 557:21) * This error is consistent with the W3C TR: http://www.w3.org/TR/xsl/#fo_marker that says that the fo:marker contents is: (#PCDATA|%inline; <http://www.w3.org/TR/xsl/#inline.fo.list>|%block; <http://www.w3.org/TR/xsl/#block.fo.list>)* but it makes the example they give useless (indeed, neither inline nor block allow directly or indirectly table-row). And so I don't quite know where I'm allowed to go from here. (If I change a behaviour in *org.apache.fop.fo.flow.Marker.validateChildNode()* I may end up with something that works and fits the bill but is inconsistent with the TR). Any comment appreciated ! Jean-Francois El Fouly From fop-dev-returnomiller@example.net Tue Sep 02 09:56:20 2008 Return-Path: <fop-dev-returnomiller@example.net> Delivered-To: omiller@example.net Received: (qmail 98632 invoked from network); 2 Sep 2008 09:56:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Sep 2008 09:56:20 -0000 Received: (qmail 91150 invoked by uid 500); 2 Sep 2008 09:56:17 -0000 Delivered-To: omiller@example.net Received: (qmail 91126 invoked by uid 500); 2 Sep 2008 09:56:17 -0000 Mailing-List: contact omiller@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:omiller@example.net> List-Unsubscribe: <mailto:omiller@example.net> List-Post: <mailto:omiller@example.net> List-Id: <fop-dev.xmlgraphics.apache.org> Reply-To: omiller@example.net Delivered-To: mailing list omiller@example.net Received: (qmail 91115 invoked by uid 99); 2 Sep 2008 09:56:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Sep 2008 02:56:17 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of omiller@example.net designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO yx-out-2324.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Sep 2008 09:55:18 +0000 Received: by yx-out-2324.google.com with SMTP id 3so1266132yxj.21 for <omiller@example.net>; Tue, 02 Sep 2008 02:55:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=9WZmRSGDVJuB3gUs2YTfSLWldQnKdwcmydaQavdQzuc=; b=evd0ridj1P/74ghRr8mwAQdXbcwpGiXAMHJ8fS9jZSgJHBzhzlnXtA73B+2Y1xDUOL HBaxTBgTQ+Nc4wvRUQ+QbfBPhYUNedKYzGIZwiKDzcTtG/WfNMi1HKtThiMSlseCQM+d cu8nY9BVt05QYXNi50PR2Qtq55cfPxtjZV758= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=LTT8hPRB8jCkPP8rybIcpmh5ZpY1aps/bKsWE6MW2fughRFnvQzzKgmFTw3eI6mNYS b56X5BOiLgxmzKn6W8KuiI3BUG3RA30tCZIShlQkLEPdkd7/Y+4Mr1ZHiT6L3RxQGAOB MttoEWRKlVX3lyh53uXvvNIZYhs6JzjHw2b6M= Received: by 83.161.120.155 with SMTP id n17mr753089ybg.131.1220349348589; Tue, 02 Sep 2008 02:55:48 -0700 (PDT) Received: from ?83.161.120.155? ( [83.161.120.155]) by mx.google.com with ESMTPS id 9sm7765544yxs.5.283.161.120.155.55.47 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 02 Sep 2008 02:55:47 -0700 (PDT) Message-ID: <omiller@example.net> Date: Tue, 02 Sep 2008 10:55:45 +0100 From: Vincent Hennebert <omiller@example.net> User-Agent: Thunderbird 83.161.120.155 (X11/20080724) MIME-Version: 1.0 To: omiller@example.net Subject: Re: I need fo:retrieve-table-marker example or how to implement continued label in FOP-95? References: <omiller@example.net> <omiller@example.net> <omiller@example.net> In-Reply-To: <omiller@example.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org For the sake of completeness, see this message and the following ones in the same thread: http://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-dev/200805.mbox/<omiller@example.net> Some non-trivial changes are indeed necessary in the table layout code... and might be further invalidated by the new page layout approach. Vincent Jeremias Maerki wrote: > On 01.09.2008 23:20:29 Andreas Delmelle wrote: >> On Sep 1, 2008, at 23:02, Andreas Delmelle wrote: >> >> (Moving this to fop-dev@) >> >>> On Sep 1, 2008, at 22:42, Jean-François El Fouly wrote: >>>> Hhmm... I've been quickly through the code and my first impression >>>> is that it IS implemented. >>> Not really, I'm afraid. I have prepared the implementation a while >>> ago. That much is true. FOP simply does nothing with a retrieve- >>> table-marker node, but the node is created and the properties >>> parsed. Only in layoutmgr.LayoutManagerMapping, you will notice >>> that the RetrieveTableMarker generates no LayoutManager yet. >>> >>>> I've set up a simple test case and, going through the stack trace, >>>> I guess it could be a simple bug fix, something like a bad or >>>> insufficient test in TablePart.java >>> Oh, rest assured, it's going to take a bit more thought and >>> effort... ;-) >> To spare some time looking, I see one issue that may turn out to be >> quite a challenge. >> One significant benefit is that it operates on the same fo:markers, >> so little work there, and it may even give you some ideas on how to >> solve it for the table-case, however... >> >> If you follow what happens during regular marker-retrieval, you'll >> notice that the resolution depends on the markers having been added >> to the page-viewport. >> This happens in the addAreas() phase. Later, when the page is >> finalized, the static-content is added, and at that point the markers >> are readily available. >> >> For a table-header (or -footer), there will be an additional >> difficulty, because at the point where we generate the base element >> list, the markers will not have been processed, so we cannot really >> depend on that same mechanism... Strictly speaking, we might also end >> up with borderline cases, where the table-header's height varies from >> page to page, depending on the content retrieved in the marker. Not >> sure, but the table-code may need some work to cater for this. > > Absolutely. At the moment the element list for headers and footers is > calculated once (in TableContentLayoutManager) and then used for every > break possibility (see TableHFPenaltyPosition). When > retrieve-table-markers are used you basically have to recalculate the > header and footer element lists for each break position in case the > markers change. > > That's quite a bit of processing effort that is even mostly done in vain > since most break positions won't even be used. But since we're still on > a total-fit approach, that is necessary. That should improve when > Vincent is finished with his revamping of the page breaking process. > >> Just so you know what you're getting yourself into. ;-) >> >> Then again, we're here for you, if you get stuck. >> >> Cheers >> >> Andreas >> > > > > > Jeremias Maerki From fop-dev-returnomiller@example.net Tue Sep 02 10:22:02 2008 Return-Path: <fop-dev-returnomiller@example.net> Delivered-To: omiller@example.net Received: (qmail 8527 invoked from network); 2 Sep 2008 10:22:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Sep 2008 10:22:02 -0000 Received: (qmail 26394 invoked by uid 500); 2 Sep 2008 10:22:00 -0000 Delivered-To: omiller@example.net Received: (qmail 26035 invoked by uid 500); 2 Sep 2008 10:21:58 -0000 Mailing-List: contact omiller@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:omiller@example.net> List-Unsubscribe: <mailto:omiller@example.net> List-Post: <mailto:omiller@example.net> List-Id: <fop-dev.xmlgraphics.apache.org> Reply-To: omiller@example.net Delivered-To: mailing list omiller@example.net Received: (qmail 26024 invoked by uid 99); 2 Sep 2008 10:21:58 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Sep 2008 03:21:58 -0700 X-ASF-Spam-Status: No, hits=3.8 required=10.0 tests=SPF_PASS,TVD_STOCK1 X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of omiller@example.net designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO yw-out-2324.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Sep 2008 10:20:59 +0000 Received: by yw-out-2324.google.com with SMTP id 2so303124ywt.21 for <omiller@example.net>; Tue, 02 Sep 2008 03:21:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=DrzqRUMue9WrsgKkvJcjAq3rPg2XnOe3uacWQZjMWxY=; b=UYRKJipAStXdlVYloIsvaFlXMWcCgEti/nGGriYBc0f4JM65cu/Qh5r23eAyUWKJ9I Ezw/XCFr/WMVhEqeBCziffoDtrbAF1MCDsvad6tJDSwXokzr9Ra48O16o8EKDAc8hfN1 ajro9t8t5S9j7B8NsTof17ussCnLym6TR/MBE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=wuH/j6YR7dBJX6lSIBtqcS9SGjMME/X6oo5KoQ1W7+qgtYZ50tkdaArl2B3h/DXPI7 FbiQZ3ctUXTrQPCn/KhNDAraPLNYtQR/wTm1yzx1LIUzNDBeqMu774WTqek55zncI0RD 5m44fyaM32yJ+WxPxPw5GqgIsWxAx+LRXqA/U= Received: by 83.161.120.155 with SMTP id q7mr10236627ybi.52.1220350878966; Tue, 02 Sep 2008 03:21:18 -0700 (PDT) Received: from ?83.161.120.155? ( [83.161.120.155]) by mx.google.com with ESMTPS id 6sm8233378yxg.6.283.161.120.155.21.17 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 02 Sep 2008 03:21:18 -0700 (PDT) Message-ID: <omiller@example.net> Date: Tue, 02 Sep 2008 11:21:16 +0100 From: Vincent Hennebert <omiller@example.net> User-Agent: Thunderbird 83.161.120.155 (X11/20080724) MIME-Version: 1.0 To: omiller@example.net Subject: Re: A (long) question on implementing fo:retrieve-table-marker References: <omiller@example.net> In-Reply-To: <omiller@example.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org Hi Jean-François, Jean-François El Fouly wrote: > I take as reference: http://www.w3.org/TR/xsl/ <snip/> > *GRAVE: Exception > javax.xml.transform.TransformerException: > org.apache.fop.fo.ValidationException: > file:/D:/Java/fop-0.95beta/test-rtm.fo:533:112: Error(533/112): > fo:retrieve-tab > le-marker is not a valid child element of fo:table-header. > * > For the sake of clarity only let's call this a "bug" since > *fo-retrieve-table-marker* /is/ a valid child element of > *fo:table-header:* http://www.w3.org/TR/xsl/#fo_retrieve-table-marker That's right. > So let's read the full stack trace and "fix" this by adding one more > condition in *org.apache.fop.fo.flow.table.TablePart.validateChildNode()*. > The next step is where I'm puzzled and don't know how to proceed since > the W3C recommendation and the example they give seem inconsistent with > each other, while the error message FOP returns seems consistent with > the recommendation: > > *GRAVE: Exception > javax.xml.transform.TransformerException: > org.apache.fop.fo.ValidationException: > "{http://www.w3.org/1999/XSL/Format}table-row" is not a valid child of > "fo:mark > er"! (See position 557:21) > * > This error is consistent with the W3C TR: > http://www.w3.org/TR/xsl/#fo_marker > that says that the fo:marker contents is: > > (#PCDATA|%inline; <http://www.w3.org/TR/xsl/#inline.fo.list>|%block; > <http://www.w3.org/TR/xsl/#block.fo.list>)* Actually, just below the content model you have the following sentence: "An fo:marker may contain any formatting objects that are permitted as a replacement of any fo:retrieve-marker or fo:retrieve-table-marker that retrieves the fo:marker's children." Which actually is a bit inconsistent with the content model just above. If you ever feel like mentioning this inconsistency to xsl-editors@... I think the behaviour you get by following that sentence is sensible, so go for it. > but it makes the example they give useless (indeed, neither inline nor > block allow directly or indirectly table-row). > And so I don't quite know where I'm allowed to go from here. (If I > change a behaviour in > *org.apache.fop.fo.flow.Marker.validateChildNode()* I may end up with > something that works and fits the bill but is inconsistent with the TR). Unless I'm missing something, Marker.validateChildNode should do nothing else than passing the call to its parent element. HTH, Vincetn From fop-dev-returnomiller@example.net Tue Sep 02 11:52:03 2008 Return-Path: <fop-dev-returnomiller@example.net> Delivered-To: omiller@example.net Received: (qmail 52773 invoked from network); 2 Sep 2008 11:52:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Sep 2008 11:52:03 -0000 Received: (qmail 42232 invoked by uid 500); 2 Sep 2008 11:52:01 -0000 Delivered-To: omiller@example.net Received: (qmail 42212 invoked by uid 500); 2 Sep 2008 11:52:01 -0000 Mailing-List: contact omiller@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:omiller@example.net> List-Unsubscribe: <mailto:omiller@example.net> List-Post: <mailto:omiller@example.net> List-Id: <fop-dev.xmlgraphics.apache.org> Reply-To: omiller@example.net Delivered-To: mailing list omiller@example.net Received: (qmail 42201 invoked by uid 99); 2 Sep 2008 11:52:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Sep 2008 04:52:01 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Sep 2008 11:51:11 +0000 Received: by brutus.apache.org (Postfix, from userid 33) id D904D234C1C6; Tue, 2 Sep 2008 04:51:11 -0700 (PDT) From: omiller@example.net To: omiller@example.net Subject: DO NOT REPLY [Bug 45727] New: RTF generated document has only empty pages in Word X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: newchanged X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Fop X-Bugzilla-Component: rtf X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: omiller@example.net X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: omiller@example.net X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: <omiller@example.net/bugzilla/> Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Date: Tue, 2 Sep 2008 04:51:11 -0700 (PDT) X-Virus-Checked: Checked by ClamAV on apache.org https://issues.apache.org/bugzilla/show_bug.cgi?id=45727 Summary: RTF generated document has only empty pages in Word Product: Fop Version: 0.95 Platform: PC OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component: rtf AssignedTo: omiller@example.net ReportedBy: omiller@example.net Hi The attached FO file which generates a good PDF file does not generate a good RTF file. When opening in Word 2003/2007 it produces only empty pages. Well not really empty, it seems that the text is there, but invissible. The PDF generated is 4 pages, but when openign in word it produces lots more pages. Peter -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From fop-dev-returnomiller@example.net Tue Sep 02 11:55:51 2008 Return-Path: <fop-dev-returnomiller@example.net> Delivered-To: omiller@example.net Received: (qmail 56153 invoked from network); 2 Sep 2008 11:55:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Sep 2008 11:55:51 -0000 Received: (qmail 46059 invoked by uid 500); 2 Sep 2008 11:55:48 -0000 Delivered-To: omiller@example.net Received: (qmail 45909 invoked by uid 500); 2 Sep 2008 11:55:48 -0000 Mailing-List: contact omiller@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:omiller@example.net> List-Unsubscribe: <mailto:omiller@example.net> List-Post: <mailto:omiller@example.net> List-Id: <fop-dev.xmlgraphics.apache.org> Reply-To: omiller@example.net Delivered-To: mailing list omiller@example.net Received: (qmail 45898 invoked by uid 99); 2 Sep 2008 11:55:47 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Sep 2008 04:55:47 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [83.161.120.155] (HELO brutus.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Sep 2008 11:54:56 +0000 Received: by brutus.apache.org (Postfix, from userid 33) id 5F15D234C1C6; Tue, 2 Sep 2008 04:55:27 -0700 (PDT) From: omiller@example.net To: omiller@example.net Subject: DO NOT REPLY [Bug 45727] RTF generated document has only empty pages in Word X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: newchanged X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Fop X-Bugzilla-Component: rtf X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: omiller@example.net X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: omiller@example.net X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: In-Reply-To: <omiller@example.net/bugzilla/> References: <omiller@example.net/bugzilla/> Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Message-Id: <omiller@example.net> Date: Tue, 2 Sep 2008 04:55:27 -0700 (PDT) X-Virus-Checked: Checked by ClamAV on apache.org https://issues.apache.org/bugzilla/show_bug.cgi?id=45727 --- Comment #1 from Peter van der Veen <omiller@example.net> 2008-09-02 04:55:27 PST --- Created an attachment (id=22511) --> (https://issues.apache.org/bugzilla/attachment.cgi?id=22511) test file -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. From fop-dev-returnomiller@example.net Tue Sep 02 18:25:02 2008 Return-Path: <fop-dev-returnomiller@example.net> Delivered-To: omiller@example.net Received: (qmail 38986 invoked from network); 2 Sep 2008 18:25:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Sep 2008 18:25:02 -0000 Received: (qmail 29859 invoked by uid 500); 2 Sep 2008 18:25:00 -0000 Delivered-To: omiller@example.net Received: (qmail 29844 invoked by uid 500); 2 Sep 2008 18:25:00 -0000 Mailing-List: contact omiller@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:omiller@example.net> List-Unsubscribe: <mailto:omiller@example.net> List-Post: <mailto:omiller@example.net> List-Id: <fop-dev.xmlgraphics.apache.org> Reply-To: omiller@example.net Delivered-To: mailing list omiller@example.net Received: (qmail 29830 invoked by uid 99); 2 Sep 2008 18:25:00 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Sep 2008 11:24:59 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [83.161.120.155] (HELO winston.telenet-ops.be) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Sep 2008 18:24:00 +0000 Received: from localhost (localhost.localdomain [83.161.120.155]) by winston.telenet-ops.be (Postfix) with SMTP id D3063A003A for <omiller@example.net>; Tue, 2 Sep 2008 20:24:28 +0200 (CEST) Received: from [83.161.120.155] (78-20-241-246.access.telenet.be [83.161.120.155]) by winston.telenet-ops.be (Postfix) with ESMTP id C2700A0026 for <omiller@example.net>; Tue, 2 Sep 2008 20:24:28 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v753.1) In-Reply-To: <omiller@example.net> References: <omiller@example.net> Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Message-Id: <omiller@example.net> Content-Transfer-Encoding: quoted-printable From: Andreas Delmelle <omiller@example.net> Subject: Re: A (long) question on implementing fo:retrieve-table-marker Date: Tue, 2 Sep 2008 20:24:15 +0200 To: omiller@example.net X-Mailer: Apple Mail (2.753.1) X-Virus-Checked: Checked by ClamAV on apache.org On Sep 2, 2008, at 11:21, Jean-Fran=E7ois El Fouly wrote: > <snip /> > Now if I run my test case against the trunk of FOP I get this error =20= > message: > > *GRAVE: Exception > javax.xml.transform.TransformerException: =20 > org.apache.fop.fo.ValidationException: > file:/D:/Java/fop-0.95beta/test-rtm.fo:533:112: Error(533/112): =20 > fo:retrieve-tab > le-marker is not a valid child element of fo:table-header. > * Indeed, a shortcoming. There is one other case: the entire header/=20 footer can be contained within an fo:marker. This will currently also =20= throw a ValidationException. <snip /> > The next step is where I'm puzzled and don't know how to proceed =20 > since the W3C recommendation and the example they give seem =20 > inconsistent with each other, while the error message FOP returns =20 > seems consistent with the recommendation: > > *GRAVE: Exception > javax.xml.transform.TransformerException: =20 > org.apache.fop.fo.ValidationException: > "{http://www.w3.org/1999/XSL/Format}table-row" is not a valid child =20= > of "fo:mark > er"! (See position 557:21) > * > This error is consistent with the W3C TR: http://www.w3.org/TR/xsl/=20 > #fo_marker > that says that the fo:marker contents is: > > (#PCDATA|%inline; <http://www.w3.org/TR/xsl/#inline.fo.list>|%=20 > block; <http://www.w3.org/TR/xsl/#block.fo.list>)* > > but it makes the example they give useless (indeed, neither inline =20 > nor block allow directly or indirectly table-row). > And so I don't quite know where I'm allowed to go from here. (If I =20 > change a behaviour in =20 > *org.apache.fop.fo.flow.Marker.validateChildNode()* I may end up =20 > with something that works and fits the bill but is inconsistent =20 > with the TR). The best way to go about it is probably to check the ancestry of the =20 fo:marker before validating the child node. If the marker appears as =20 a descendant of an arbitrary fo:table, then fo:table-row is allowed. =20 However, we need to watch out because the same fo:marker could be =20 retrieved into a static-content, in which case the fo:table-row would =20= not be valid. So, on the one hand, the validation rule needs to be relaxed. On the =20 other, the regular marker-retrieval may not be disturbed... What Vincent pointed out earlier does not seem entirely correct to =20 me. The validation is independent from the parent fo, and so should =20 not be delegated, but rather /deferred/ until the marker is retrieved/=20= reparented ... and even then, if a marker with a table-row ends up =20 being retrieved by a normal retrieve-marker, I think this deserves =20 only a serious warning about content being ignored/skipped. (The =20 author of the stylesheet should probably take care to assign these =20 markers to a special marker-class, which only gets retrieved by =20 retrieve-table-marker.) HTH! Cheers Andreas From fop-dev-returnomiller@example.net Tue Sep 02 19:39:46 2008 Return-Path: <fop-dev-returnomiller@example.net> Delivered-To: omiller@example.net Received: (qmail 86755 invoked from network); 2 Sep 2008 19:39:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Sep 2008 19:39:46 -0000 Received: (qmail 12809 invoked by uid 500); 2 Sep 2008 19:39:44 -0000 Delivered-To: omiller@example.net Received: (qmail 12792 invoked by uid 500); 2 Sep 2008 19:39:44 -0000 Mailing-List: contact omiller@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:omiller@example.net> List-Unsubscribe: <mailto:omiller@example.net> List-Post: <mailto:omiller@example.net> List-Id: <fop-dev.xmlgraphics.apache.org> Reply-To: omiller@example.net Delivered-To: mailing list omiller@example.net Received: (qmail 12781 invoked by uid 99); 2 Sep 2008 19:39:43 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Sep 2008 12:39:43 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [83.161.120.155] (HELO winston.telenet-ops.be) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Sep 2008 19:38:45 +0000 Received: from localhost (localhost.localdomain [83.161.120.155]) by winston.telenet-ops.be (Postfix) with SMTP id 44EDAA0054 for <omiller@example.net>; Tue, 2 Sep 2008 21:39:05 +0200 (CEST) Received: from [83.161.120.155] (78-20-241-246.access.telenet.be [83.161.120.155]) by winston.telenet-ops.be (Postfix) with ESMTP id 2F620A003D for <omiller@example.net>; Tue, 2 Sep 2008 21:39:05 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v753.1) In-Reply-To: <omiller@example.net> References: <omiller@example.net> Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Message-Id: <omiller@example.net> Content-Transfer-Encoding: quoted-printable From: Andreas Delmelle <omiller@example.net> Subject: Re: A (long) question on implementing fo:retrieve-table-marker Date: Tue, 2 Sep 2008 21:38:52 +0200 To: omiller@example.net X-Mailer: Apple Mail (2.753.1) X-Virus-Checked: Checked by ClamAV on apache.org On Sep 2, 2008, at 11:21, Jean-Fran=E7ois El Fouly wrote: Just another hint I thought of: > To begin with, I've built a simple example / test case related to =20 > my customer's needs but fairly based on the one in 83.161.120.155.2: =20 > http://www.w3.org/TR/xsl/#d0e14681 > This example looks good and though not trivial to understand at =20 > first sight, it is a common-sense use of fo:retrieve-table-marker. > It has a sort of "conditional row" that is displayed (or not) in =20 > the table footer and is defined just after table-body: > > * <fo:marker marker-class-name=3D"continued"> > <fo:table-row> > <fo:table-cell> > <fo:block>Table continued...</fo:block> > </fo:table-cell> > </fo:table-row> >
{'source': 'Apache Software Foundation Public Mail Archives'}