Bug report for Fop [2004/11/07]
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned|
| | OPN=ReopenedVER=Verified(Skipped Closed/Resolved) |
| | +-+
| | | Severity: BLK=Blocker CRI=CriticalMAJ=Major |
| | | MIN=Minor NOR=Normal ENH=Enhancement |
| | | +-+
| | | | Date Posted |
| | | | +--+
| | | | | Description |
| | | | | |
| 635|Opn|Nor|2001-02-18|Doesn't support id= attribute in fo:page-sequence |
| 953|Opn|Nor|2001-03-12|Incorrect hyperlinks area rendering in justified t|
| 1063|New|Nor|2001-03-21|fop does not handle large fo files|
| 1180|New|Maj|2001-04-02|Problem with monospaced font |
| 1859|Opn|Min|2001-05-22|org.apache.fop.apps.Driver.reset() doesn't fully r|
| 1998|New|Nor|2001-06-05|linefeed-treatment not understood |
| 2150|Ass|Maj|2001-06-13|New page with a table-header but without any tabl|
| 2475|Ass|Nor|2001-07-06|Borders don't appear to work in fo:table-row|
| 2740|New|Maj|2001-07-23|multi-page tables sometimes render badly |
| 2909|New|Maj|2001-07-30|Gradient render error |
| 2964|Ass|Nor|2001-08-02|problems with height of cells in tables |
| 2988|New|Maj|2001-08-03|0.19: list-item-label does not stick to list-item-|
| 3044|Ass|Maj|2001-08-08|keep-together not functioning |
| 3280|New|Nor|2001-08-27|PCL Renderer doesn't work |
| 3305|Opn|Nor|2001-08-28|list-block overlapping footnote body |
| 3497|New|Maj|2001-09-07|id already exists error when using span=all attr|
| 3824|New|Blk|2001-09-25|MIF option with tables|
| 4030|New|Nor|2001-10-08|IOException creating Postscript with graphics on S|
| 4126|New|Nor|2001-10-12|FontState.width() returns pts instead of millipts |
| 4226|New|Nor|2001-10-17|The orphans property doesn't seem to work |
| 4388|New|Nor|2001-10-24|Nullpointer exception in the construction of new D|
| 4415|New|Nor|2001-10-25|scaling=uniform does not work on images... |
| 4510|New|Nor|2001-10-30|fo:inline common properties ignored? |
| 4535|New|Maj|2001-10-31|PCL renderer 1.13 not rendering SVG |
| 4767|New|Nor|2001-11-09|SVG text is distored in PDF output|
| 5001|New|Nor|2001-11-21|content-width and content-height ignored? |
| 5010|New|Enh|2001-11-21|Better error reporting needed |
| 5124|New|Maj|2001-11-27|fo:block-container is not rendered properly using |
| 5335|Opn|Min|2001-12-10|Text with embedded CID fonts not retrievable from |
| 5655|Ass|Nor|2002-01-02|text-decoration cannot take multiple values |
| 6094|Opn|Maj|2002-01-29|0.20.3rc hangs in endless loop|
| 6237|Opn|Nor|2002-02-05|#xFB01 (fi ligature) produces a sharp? |
| 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|
| 6437|New|Maj|2002-02-13|Tables without fo:table-column don't render |
| 6483|New|Nor|2002-02-15|Table, Loop, footer could not fit on page, moving|
| 6844|New|Nor|2002-03-04|No line breaks inserted in list-item-label|
| 6918|New|Enh|2002-03-06|reference-orientation has no effect |
| 6997|New|Nor|2002-03-09|[PATCH] Row-spanned row data breaks over a page wi|
| 7140|New|Enh|2002-03-15|page-position attribute set to last on condition|
| 7241|New|Nor|2002-03-19|keep-with-previous, keep-with-next only working on|
| 7283|New|Nor|2002-03-20|Table border misaligned when using margin-left in |
| 7337|New|Nor|2002-03-21|border around external image leaves empty space |
| 7487|New|Nor|2002-03-26|break-before=page for table inserts empty page |
| 7496|New|Nor|2002-03-26|The table header borders are not adjusted to the b|
| 7525|New|Cri|2002-03-27|table with spans inside a list-block |
| 7919|New|Cri|2002-04-10|problem to use attribute linefeed-treatment and li|
| 8003|Ass|Maj|2002-04-12|FopImageFactory never releases cached images |
| 8050|New|Nor|2002-04-13|Soft hyphen (shy;) is not handled properly |
| 8321|New|Nor|2002-04-19|from-parent('width') returns 0 for nested tables |
| 8463|New|Nor|2002-04-24|SVG clipping in external.fo example doc when rende|
|
RE: aXSL (Was: RE: Exceptions. (Was: AreaFactory patch))
-Original Message- From: Victor Mote [mailto:[EMAIL PROTECTED] Jeremias Maerki wrote: Hi guys, (Just catching up on the postings of the last few days, this one caught my eye...) although I'm still a bit concerned that you based your PDF part on the maintenance branch code (that's still the case, isn't it?). FOrayPDF is based on the maintenance branch code, but I am not sure I understand your point. Victor, IIC, Jeremias' concern is about the PDF lib in HEAD containing substantial improvements over the code in the maintenance branch. One aspect that springs to mind is WRT encryption support --as I recall, maintenance still had some problems with this, for instance, when using custom fonts... Jeremias once mentioned that, in order to make it work properly, he had to make significant changes to the PDF-related code. Greetz, Andreas
Re: FOP Web Site Update
On Nov 7, 2004, at 6:46 AM, Glen Mazza wrote: Clay Leeds wrote: On a related note, IIRC I wanted to change the color scheme to Red - Amber - Green (stop light analogy: No - Partial - Full compliance--I'm aware of the argument about something either being compliant or it's not ;-)) That's fine -- just keep in mind though that one limitation of this page, not reasonably fixable, is that compliance is ultimately a renderer-specific issue (i.e., the results of some properties and FO's may be implemented in some render-types but not yet in others.) So you may not want to go overboard on this page, as there is already an overall limitation to its accuracy. Still, this page has been a useful source of information for our users, possibly our most-viewed page. That 'sounds' like something that could be put in the Notes column. [BTW, If you can change to the bright red color for the mouse-hover like the Web Services TLP has that would be nice.] Try it now: http://homepage.mac.com/webmaestro/xml-fop/xml-graphics/ It's not 'bright' red (it's dark red - #66), but I think the contrast is subtle without being brash. Would you prefer #ff? Either are fine for me. I don't have much experience with web site design, so I'll defer to you on these matters. Glen Okey doke! Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
DO NOT REPLY [Bug 32107] New: - Move FOP wiki to secure
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=32107. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=32107 Move FOP wiki to secure Summary: Move FOP wiki to secure Product: Fop Version: all Platform: All URL: http://nagoya.apache.org/wiki/apachewiki.cgi?FOPProjectP ages OS/Version: Other Status: NEW Severity: Critical Priority: Other Component: documentation AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] FOP needs to move our wiki to the secure MoinMoin wiki server ASAP. I'm adding this to Bugzilla so it's 'here'... * Questions about the new wiki? http://wiki.apache.org/general/UseModMigration/FrequentlyAskedQuestions * Want to request a new wiki? With or without migrating old data. http://wiki.apache.org/general/HowToMakeWikiAdminRequests For more information see here: http://marc.theaimsgroup.com/?l=xml-apache-generalm=109854171031270w=2 and here: http://marc.theaimsgroup.com/?l=fop-devm=109726265919423w=2
RE: aXSL (Was: RE: Exceptions. (Was: AreaFactory patch))
Andreas L. Delmelle wrote: Victor, IIC, Jeremias' concern is about the PDF lib in HEAD containing substantial improvements over the code in the maintenance branch. One aspect that springs to mind is WRT encryption support --as I recall, maintenance still had some problems with this, for instance, when using custom fonts... Jeremias once mentioned that, in order to make it work properly, he had to make significant changes to the PDF-related code. Yes, I am well aware that there are improvements to HEAD in several places, and that FOray will be missing those for the moment. I fully intend to eventually integrate the HEAD improvements into FOray, but 1) it is non-trivial, 2) I have bigger issues ATM (still trying to get FOTree isolated), and 3) I don't want to do much until I either have to, or until FOP decides how it will proceed -- if FOP decides to start with FOray's isolation work and upgrade to HEAD, then it might be a joint effort. If FOP decides to isolate HEAD's PDF lib directly, and if they use a common interface (like aXSL), then I shouldn't duplicate that effort in FOray, I should just wait until FOP is done with that work and drop it into FOray. If FOP doesn't want PDF isolated, or has no interest in using a common interface, then I'm not part of the picture at all. My main point to Jeremias is that none of this has anything to do with building an interface that everyone can use, except that: 1) FOray already has the interface at least partially designed by virtue of isolating the PDF code, and 2) making an interface *before* starting isolation work is a big help in that work. Victor Mote
Re: cvs commit: xml-fop/src/documentation/content/xdocs/dev book.xml
Simon, Does the book.xml file in your DnI section serve any specific purpose (DnI-related), or is it to follow the common coding/forrest convention? I ask, because the use of book.xml is deprecated in Forrest-0.6 in favor of the site-wide src/documentation/content/xdocs/site.xml file. On Nov 7, 2004, at 8:26 PM, [EMAIL PROTECTED] wrote: clay2004/11/07 20:26:29 Removed: src/documentation/content/xdocs book.xml src/documentation/content/xdocs/design book.xml src/documentation/content/xdocs/design/alt.design book.xml src/documentation/content/xdocs/design/alt.design/properties book.xml src/documentation/content/xdocs/dev book.xml Log: removed all book.xml files (except DnI) Web Maestro Clay -- Clay Leeds - [EMAIL PROTECTED] Webmaster/Developer - Medata, Inc. - http://www.medata.com/ PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
