cvs commit: xml-fop/src/documentation/content/xdocs status.xml
vmote 2003/07/31 23:54:14 Modified:src/documentation/content/xdocs status.xml Log: update with current trunk statistics Revision ChangesPath 1.11 +52 -22xml-fop/src/documentation/content/xdocs/status.xml Index: status.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/status.xml,v retrieving revision 1.10 retrieving revision 1.11 diff -u -r1.10 -r1.11 --- status.xml1 Aug 2003 06:12:11 - 1.10 +++ status.xml1 Aug 2003 06:54:14 - 1.11 @@ -40,7 +40,7 @@ tr th#x00A0;/th th0.20.5/th - thDevelopment (aka trunk, redesign)/th + thDevelopment (aka trunk, redesign) as of August 1, 2003/th /tr tr td colspan=3#x00A0;/td @@ -51,22 +51,42 @@ tr tdfop jar/td td1,485 kb/td - td1,992 kb/td + td2,132 kb/td /tr tr tdhyphenation (in fop.jar)/td td348 kb/td - td746 kb/td + td1,358 kb/td +/tr +tr + tdant jar/td + td#x00A0;/td + td707 kb/td /tr tr tdavalon-framework jar/td td62 kb/td - td/td + td72 kb/td /tr tr tdbatik jar/td td2,063 kb/td - td2,119 kb/td + td2,213 kb/td +/tr +tr + tdcommons-io-dev jar/td + td#x00A0;/td + td71 kb/td +/tr +tr + tdcommons-lang jar/td + td#x00A0;/td + td190 kb/td +/tr +tr + tdservlet jar/td + td#x00A0;/td + td39 kb/td /tr tr tdxalan jar/td @@ -76,7 +96,7 @@ tr tdxerces jar/td td816 kb/td - td813 kb/td + td816 kb/td /tr tr tdxml-apis jar/td @@ -89,42 +109,47 @@ tr tdorg.apache.fop.fo.*/td td20,297/td - td14,660 (21%)/td + td22,306/td /tr tr tdorg.apache.fop.layout.*/td td9,444/td - td7,154 (10%)/td + td4,238/td /tr tr tdorg.apache.fop.layoutmgr.*/td td#x00A0;/td - td#x00A0;/td + td10,069/td /tr tr tdorg.apache.fop.area.*/td td#x00A0;/td - td#x00A0;/td + td5,791/td /tr tr tdorg.apache.fop.render.*/td td18,387/td - td16,260 (23%)/td + td11,527/td /tr tr tdorg.apache.fop.pdf.*/td td10,203/td - td7,938 (11%)/td + td15,669/td +/tr +tr + tdorg.apache.fop.rtf.*/td + td0/td + td12,747/td /tr tr tdOther/td td29,821/td - td#x00A0;/td + td32,543/td /tr tr tdTotal/td td88,152/td - td69,610/td + td114,890/td /tr tr th colspan=3Files, using find . -iname *.java | wc -l/th @@ -132,42 +157,47 @@ tr tdorg.apache.fop.fo.*/td td122/td - td122 (31%)/td + td127/td /tr tr tdorg.apache.fop.layout.*/td td49/td - td#x00A0;/td + td24/td /tr tr tdorg.apache.fop.layoutmgr.*/td td#x00A0;/td - td#x00A0;/td + td38/td /tr tr tdorg.apache.fop.area.*/td td#x00A0;/td - td#x00A0;/td + td39/td /tr tr tdorg.apache.fop.render.*/td td48/td - td48/td + td36/td /tr tr tdorg.apache.fop.pdf.*/td td51/td - td50 (13%)/td + td70/td +/tr +tr + tdorg.apache.fop.rtf.*/td + td#x00A0;/td + td80/td /tr tr tdOther/td td129/td - td394/td + td140/td /tr tr tdTotal/td td399/td - td394/td + td554/td /tr /table /section - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 22048] New: - PDF renderer and hyphenation break character order
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22048. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22048 PDF renderer and hyphenation break character order Summary: PDF renderer and hyphenation break character order Product: Fop Version: 0.20.4 Platform: PC URL: http://staff.csc.fi/aniemela/fopbug2.pdf OS/Version: Linux Status: NEW Severity: Major Priority: Other Component: page-master/layout AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The PDF renderer/page layout component/hyphenation break character order with inline elements: The following construct fo:block Otsakerivin vapaamuotoisuuden takia ainoat jarkevasti hyodynnettavat arvot ovat kentan nimi ( fo:inline font-family=monospacelt;melting.pointgt;/fo:inline ) ja DT-numero. /fo:block Is rendered as Otsakerivin [] hyodynnettavat arvot ovat kentan nimi ( mel- ting.point ) ja DT-numero. Below is a cleaned-up version of Docbook-XSLT-produced FO data, which explains the block-happiness. URL points to a FOP 0.20.4 rendered PDF which illustrates the bug. Full XSL-FO data follows: ?xml version=1.0 encoding=utf-8 ? fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; font-family=serif font-size=10pt text-align=left line-height=normal font-selection-strategy=character-by-character language=en fo:layout-master-set fo:simple-page-master master-name=blank page-width=210mm page-height=297mm margin-top=0.5in margin-bottom=0.5in margin-left=1in margin-right=1in fo:region-body display-align=center margin-bottom=0.5in margin-top=0.5in region-name=blank-body / /fo:simple-page-master fo:simple-page-master master-name=body-first page-width=210mm page-height=297mm margin-top=0.5in margin-bottom=0.5in margin-left=1in margin-right=1in fo:region-body margin-bottom=0.5in margin-top=0.5in column-count=1 / /fo:simple-page-master fo:simple-page-master master-name=body-odd page-width=210mm page-height=297mm margin-top=0.5in margin-bottom=0.5in margin-left=1in margin-right=1in fo:region-body margin-bottom=0.5in margin-top=0.5in column-count=1 / /fo:simple-page-master fo:simple-page-master master-name=body-even page-width=210mm page-height=297mm margin-top=0.5in margin-bottom=0.5in margin-right=1in margin-left=1in fo:region-body margin-bottom=0.5in margin-top=0.5in column-count=1 / /fo:simple-page-master fo:page-sequence-master master-name=body fo:repeatable-page-master-alternatives fo:conditional-page-master-reference master-reference=blank blank-or-not-blank=blank / fo:conditional-page-master-reference master-reference=body-first page-position=first / fo:conditional-page-master-reference master-reference=body-odd odd-or-even=odd / fo:conditional-page-master-reference master-reference=body-even odd-or-even=even / /fo:repeatable-page-master-alternatives /fo:page-sequence-master /fo:layout-master-set fo:page-sequence xmlns:axf=http://www.antennahouse.com/names/XSL/Extensions; hyphenate=true master-reference=body language=fi format=1 initial-page-number=1 hyphenation-character=- hyphenation-push-character-count=2 hyphenation-remain-character-count=2 fo:flow flow-name=xsl-region-body fo:block id=d0e14 fo:block fo:block fo:block keep-together=always margin-left=-4pc font-family=sans-serif fo:block keep-with-next.within-column=always fo:block font-family=sans-serif font-weight=bold keep-with-next.within-column=always space-before.minimum=0.8em space-before.optimum=1.0em space-before.maximum=1.2em fo:block font-size=14.399pt1.1.1. Datamerkinnan otsakerivi/fo:block /fo:block /fo:block /fo:block /fo:block fo:block / /fo:block fo:block space-before.optimum=1em space-before.minimum=0.8em space-before.maximum=1.2em Otsakerivin vapaamuotoisuuden takia ainoat jarkevasti hyodynnettavat arvot ovat kentan nimi ( fo:inline font-family=monospacelt;melting.pointgt;/fo:inline ) ja DT-numero. /fo:block /fo:block /fo:flow /fo:page-sequence /fo:root - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 22048] - PDF renderer and hyphenation break character order
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22048. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22048 PDF renderer and hyphenation break character order [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2003-08-01 12:40 --- This has been fixed already. Get the latest release. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 22053] New: - basic-link off by footer height in table
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22053. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22053 basic-link off by footer height in table Summary: basic-link off by footer height in table Product: Fop Version: 0.20.5 Platform: PC OS/Version: Windows XP Status: NEW Severity: Normal Priority: Other Component: pdf renderer AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] When adding a table-footer the hotspot for a basic-length appears to be offset toward the bottom by the height of the footer. Is the position incorrectly taking into account the table rows in the footer? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 22027] - FOP Status graphic needs update
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22027. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22027 FOP Status graphic needs update [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2003-08-01 15:16 --- Committed to CVS, along with updates to the statistics. Thanks, Clay. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
FOP logo (+ a graphics question)
What is the status of the FOP logo? If we need it tweaked, I can help. -- Clay Leeds - [EMAIL PROTECTED] Web Developer - Medata, Inc. - http://www.medata.com PGP Public Key: https://mail.medata.com/pgp/cleeds.asc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: FOP logo (+ a graphics question)
Clay Leeds wrote: What is the status of the FOP logo? If we need it tweaked, I can help. That would be great. The last word on the subject is here: http://marc.theaimsgroup.com/?l=fop-devm=105593071722327w=2 Here is what I suggest: 1. Find the SVG document for #30, which won the contest. It looks like Oleg doesn't have it. Would you please contact Scott Hofman directly (see the above link for a link to him) to obtain a copy of it, create a Bugzilla issue with it attached, and we'll get it into the repository. 2. We need to decide 1) whether additional tweaking is necessary, and 2) how to decide what tweaking needs to be done, 3) get the tweaking actually done (in addition to your offer, I think Scott made a similar offer), and committed to the repository. I propose that we take the logo as is, and revisit the issue in the future if we think its important. I don't think we can afford to spend any more bandwidth on it now. Here is my +1. 3. Research where the logo is needed. I can't think of any place other than our website. For each place it is needed, we need to consider making a jpg scaled properly. The existing jpg may be fine. 4. We'll need to get our Forrest web build to pick up the svg and/or the jpg. Probably the most efficient way to proceed is for me to see if it can be done easily. 5. When this is all done visible, we can remove the logocontest page. Thanks for helping get this done. I think it is useful to get some of this old stuff cleaned up, to clear the decks. Victor Mote - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: default value of force param for FOP
(c) include force in 0.20, default it to false, but have a message in the release notes warning about the change. Technically, even if most users forgot to read the warning in (c) they would still be OK, as they would be happy if no time was spent with unnecessary regnerations. However, due to internal links to other files that might have changed, etc.--which force does not capture, either here or in xslt--there could be a difference in functionality. In those cases, the Ant dependset task can be used to capture those dependencies. (I believe that is the best way to handle this in Ant.) Thoughts? Sorry for not responding sooner - I've been burning the midnight oil for a client this week and am behind on my email. Although the patch I submitted was for (b), my preference would be for (c) for the reasons you state (conformance with xslt task and the most sensible long-term solution) I would really like to see this in the 0.20 branch because I am using Ant + xslt + fop for a DocBook publishing toolchain which I would like to post to SourceForge or perhaps someday an Apache sub-project. The idea is that Ant buildfiles can be used to build a (potentially large) set of documents with common components. The Ant build would only rebuild the necessary pieces. Since xslt and fop processing of large documents is measured in minutes eliminating unnecessary processing is a huge win. The 1.0 release is at best several months away (right?) - so choice (c) provides a valuable feature to fop users in the meantime. I am willing to help out by testing or responding to questions on the lists to help make (c) a reality. Thanks, again, to the FOP group for this powerful tool. Regards, Sean -- --- M. Sean Gilligan: mailto:[EMAIL PROTECTED] Catalla Systems, Inc. : 831-439-9568 x11 --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
