DO NOT REPLY [Bug 19465] - fo:leader leader-pattern=rule not working correctly within FO table cell
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=19465. 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=19465 fo:leader leader-pattern=rule not working correctly within FO table cell [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INVALID | --- Additional Comments From [EMAIL PROTECTED] 2003-09-24 16:38 --- This is most certainly a bug. As both forms of generating a line-spanning leader are offered in the spec as indded they are fop must support both methods if it want to conform to the spec. I think leaders are special case because most other inline area generating fo's have no attribute to specify an size that is not dependant on the content of the inline area like fo:leader does. Because of this change I have to stay with 0.20.4 as it would be too much work to change all leaders of my xsl-fo's to the new behaviour.
DO NOT REPLY [Bug 19465] - fo:leader leader-pattern=rule not working correctly within FO table cell
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=19465. 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=19465 fo:leader leader-pattern=rule not working correctly within FO table cell [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2003-09-24 17:54 --- A bug is behaviour not conforming to the spec. If the spec is somewhat loose, well, you still can't simply call something a bug which mets the spec but not your expectations. There is no way to guess what the user had in mind when he put fo:leader/ in the source. Therefore, give some hints. One possiblity is to tell the processor to justify the paragraph, another is the usual leader-length.optimum=100% or leader-length.optimum=10cm or whatever. I fear you'll have to go to the trouble to change your code. The new method for handling opens a lot of possiblities for using leaders and is also more compatible with the behaviour of other processors.
DO NOT REPLY [Bug 20879] - [PATCH] Leader is broken in PS Renderer
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=20879. 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=20879 [PATCH] Leader is broken in PS Renderer [EMAIL PROTECTED] changed: What|Removed |Added Summary|Leader is broken in PS |[PATCH] Leader is broken in |Renderer|PS Renderer - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 20879] - [PATCH] Leader is broken in PS Renderer
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=20879. 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=20879 [PATCH] Leader is broken in PS Renderer [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2003-06-20 13:44 --- Fixed in CVS. Thanks! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 20879] New: - Leader is broken in PS Renderer
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=20879. 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=20879 Leader is broken in PS Renderer Summary: Leader is broken in PS Renderer Product: Fop Version: 0.20.5 Platform: All OS/Version: All Status: NEW Severity: Major Priority: Other Component: general AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The postscript renderer produces broken output when trying to render a leader. I'm not a postscript expert but comparing 0.20.4 (where it works) to 0.20.5rc3a (where it's broken) it looks like a couple of moveto's are missing. The FO below will produce the bad postscript. PDF rendering works fine. ?xml version=1.0 encoding=UTF-8? fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set fo:simple-page-master margin-right=0.3in margin-left=0.3in margin-bottom=0.1in margin-top=0.1in page-width=8.5in page-height=11in master-name=fax fo:region-body margin-left=0.3mm margin-bottom=65mm margin-top=30mm/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence master-reference=fax fo:flow flow-name=xsl-region-body fo:block fo:leader rule-thickness=.5mm leader-pattern=rule leader-length=200mm/ /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 20879] - Leader is broken in PS Renderer
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=20879. 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=20879 Leader is broken in PS Renderer --- Additional Comments From [EMAIL PROTECTED] 2003-06-18 17:05 --- I am attaching a patch that seems to fix it. I'm not sure why though. Just reverting a previous change. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 20879] - Leader is broken in PS Renderer
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=20879. 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=20879 Leader is broken in PS Renderer --- Additional Comments From [EMAIL PROTECTED] 2003-06-18 17:06 --- Created an attachment (id=6875) Proposed patch - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 17194] - LineArea Leader fails in 0.20.5rc2
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=17194. 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=17194 LineArea Leader fails in 0.20.5rc2 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2003-03-02 16:57 --- Should be fixed for 0.20.5rc3. Long section lines may overflow the TOC line area, unless the leader permits shortening. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 17194] - LineArea Leader fails in 0.20.5rc2
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=17194. 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=17194 LineArea Leader fails in 0.20.5rc2 --- Additional Comments From [EMAIL PROTECTED] 2003-02-20 23:16 --- This happens if the line area overflows. The two longest section titles are too long. Shorten them until the problem is fixed. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 17194] - LineArea Leader fails in 0.20.5rc2
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=17194. 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=17194 LineArea Leader fails in 0.20.5rc2 --- Additional Comments From [EMAIL PROTECTED] 2003-02-21 06:55 --- Modifing the titles is one solution, but not really satisfing considering the long title was just continued on a second line - i.e. this was working in 0.20.1 - 0.20.5rc - and FOP will properly crash on a lot of documents with long titles. Anyway, sometimes one is not allowed to modify anything in a document, i.e. if a document is committee work.. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 17194] New: - LineArea Leader fails in 0.20.5rc2
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=17194. 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=17194 LineArea Leader fails in 0.20.5rc2 Summary: LineArea Leader fails in 0.20.5rc2 Product: Fop Version: 0.20.5 Platform: Other OS/Version: Other Status: NEW Severity: Blocker Priority: Other Component: page-master/layout AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] This bug did not exist in 0.20.5rc Making portrait pages on A4 paper (210mmx297mm) Transforming vol1.fo to PDF [DEBUG] Input mode: [DEBUG] FO [DEBUG] fo input file: vol1.fo [DEBUG] Output mode: [DEBUG] pdf [DEBUG] output file: NC3TA-Vol1-v4.pdf [DEBUG] OPTIONS [DEBUG] no user configuration file is used [default] [DEBUG] debug mode on [DEBUG] dump configuration [DEBUG] quiet mode on [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [INFO] base directory: file:/home/js/work/noswg/xml-nc3ta/tools/build/pdf/ [INFO] FOP 0.20.5rc2 [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [INFO] building formatting object tree [INFO] setting up fonts [INFO] [1] [INFO] [2 (blank)] [DEBUG] Last page-sequence produced 2 pages. [INFO] [3] [ERROR] org.apache.fop.layout.LineArea$Leader org.apache.fop.apps.FOPException: org.apache.fop.layout.LineArea$Leader at org.apache.fop.apps.CommandLineStarter.run(CommandLineStarter.java:74) at org.apache.fop.apps.Fop.main(Fop.java:19) - java.lang.ClassCastException: org.apache.fop.layout.LineArea$Leader at org.apache.fop.layout.LineArea.verticalAlign(LineArea.java:901) at org.apache.fop.layout.BlockArea.addLineArea(BlockArea.java:91) at org.apache.fop.layout.BlockArea.end(BlockArea.java:176) at org.apache.fop.fo.flow.Block.layout(Block.java:246) at org.apache.fop.fo.flow.Block.layout(Block.java:206) at org.apache.fop.fo.flow.Block.layout(Block.java:206) at org.apache.fop.fo.flow.Block.layout(Block.java:206) at org.apache.fop.fo.flow.AbstractFlow.layout(AbstractFlow.java:111) at org.apache.fop.fo.flow.AbstractFlow.layout(AbstractFlow.java:68) at org.apache.fop.fo.pagination.PageSequence.makePage(PageSequence.java:352) at org.apache.fop.fo.pagination.PageSequence.format(PageSequence.java:290) at org.apache.fop.apps.StreamRenderer.render(StreamRenderer.java:218) at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:177) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.fop.apps.Driver.render(Driver.java:457) at org.apache.fop.apps.CommandLineStarter.run(CommandLineStarter.java:69) at org.apache.fop.apps.Fop.main(Fop.java:19) Java Result: 2 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 17194] - LineArea Leader fails in 0.20.5rc2
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=17194. 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=17194 LineArea Leader fails in 0.20.5rc2 --- Additional Comments From [EMAIL PROTECTED] 2003-02-20 07:33 --- Created an attachment (id=4936) Fails when generating TOC (Maybe caused by Pietch fix from feb 2) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 4839] - leader gets start-indent at start and end
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=4839. 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=4839 leader gets start-indent at start and end [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-05-15 11:59 --- Works as expected with 0.20.3. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 3215] - fo:leader with a percentage as leader-length does not display
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=3215. 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=3215 fo:leader with a percentage as leader-length does not display [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-05-07 13:48 --- Fixed in 0.20.3 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 3258] - Fop-0.20.0 fo:leader leader-pattern=dots/ is broken
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=3258. 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=3258 Fop-0.20.0 fo:leader leader-pattern=dots/ is broken [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-05-07 13:56 --- Fixed in 0.20.3 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 4839] New: - leader gets start-indent at start and end
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=4839. 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=4839 leader gets start-indent at start and end Summary: leader gets start-indent at start and end Product: Fop Version: 0.15 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: general AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] With the code shown below, I expect to see the following: (you need to be viewing this in a fixed-width font for it to make any sense) Hello World. Hello World.. but what I actually see is this: Hello World. Hello World... Note that the second line's leader doesn't get to the right margin; it looks as if the start-indent that I have applied to the second line is affecting its right margin too. Here is the code: ?xml version=1.0 encoding=UTF-8? fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set fo:simple-page-master margin-right=25mm margin-left=25mm margin-bottom=20mm margin-top=15mm page-height=297mm page-width=210mm master-name=a4 fo:region-before extent=10mm/ fo:region-after extent=10mm/ fo:region-body margin-bottom=15mm margin-top=15mm/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence master-name=a4 fo:flow flow-name=xsl-region-body fo:block Hello World fo:leader leader-pattern=dots/ /fo:block fo:block start-indent=2em Hello World fo:leader leader-pattern=dots/ /fo:block /fo:flow /fo:page-sequence /fo:root - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Dynamic leader lengths
Dear Darren fellow FOPers, I also have mentioned this problem twice, but no response has been forthcoming. Could someone at least accept that there is domething wrong. Regards, Mick /\ \ / X ASCII Ribbon Campaign / \ Against HTML Mail - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Leader
The problem with the leader is that the default value for the maximum length (leader-length.maximum) is 100% and the code was reading that value as 0. This resulted in a 0 length leader. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Dynamic leader lengths
I've raised this myself about three times but so far but to no avail. It's
also been raised in at least two Bugzilla reports and been posted on this
mailing list by at least three other people (not including yourself). I
guess nobody is accepting responsibility for breaking it.
-Original Message-
From: Drew Hodge [mailto:[EMAIL PROTECTED]]
Sent: Thursday, 30 August 2001 3:16
To: [EMAIL PROTECTED]
Subject: Dynamic leader lengths
In FOP 0.19.0 I used the following to produce leaders of varying lengths in
a TOC.
fo:block font-family=sans-serif
font-size=12pt
font-weight=700
color=darkred
space-after=12pt
text-align=start
fo:basic-link internal-destination={generate-id(.)}
xsl:value-of select=sectionTitle/
/fo:basic-link
fo:leader leader-pattern=dots/
xsl:text /xsl:text
fo:basic-link internal-destination={generate-id(.)}
fo:page-number-citation ref-id={generate-id(.)}/
/fo:basic-link
/fo:block
In FOP 0.20.1 this code doesn't seem to work -- the leader dots don't appear
unless I explicitly specify a length.
Does anyone know how I can get back to the behaviour of leaders in FOP
0.19.0 using FOP 0.20.1?
Thanks,
Drew Hodge
Join 18 million Eudora users by signing up for a free Eudora Web-Mail
account at http://www.eudoramail.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
[DO NOT REPLY: Bug 3258] Fop-0.20.0 fo:leader leader-pattern=dots/ is broken
PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3258 *** shadow/3258 Fri Aug 24 07:44:46 2001 --- shadow/3258.tmp.7020Tue Aug 28 06:01:17 2001 *** *** 9,15 ++ | Assigned To: [EMAIL PROTECTED] | | Reported By: [EMAIL PROTECTED] | - | CC list: Cc: | ++ | URL: | ++ --- 9,14 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
[DO NOT REPLY: Bug 3258] New: Fop-0.20.0 fo:leader leader-pattern=dots/ is broken
PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3258 *** shadow/3258 Fri Aug 24 07:44:46 2001 --- shadow/3258.tmp.20868 Fri Aug 24 07:44:46 2001 *** *** 0 --- 1,28 + ++ + | Fop-0.20.0 fo:leader leader-pattern=dots/ is broken| + ++ + |Bug #: 3258Product: Fop | + | Status: NEW Version: all | + | Resolution:Platform: Sun | + | Severity: Normal OS/Version: Solaris | + | Priority: Other Component: page-master/layout | + ++ + | Assigned To: [EMAIL PROTECTED] | + | Reported By: [EMAIL PROTECTED] | + | CC list: Cc: | + ++ + | URL: | + ++ + | DESCRIPTION | + The dots are no longer rendered. + + Code segment: + + xsl:for-each select=abstract + fo:block + xsl:call-template name=display_abstract/ + fo:leader leader-pattern=dots/ + fo:page-number-citation ref-id=A1/ + /fo:block + + /xsl:for-each - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
[DO NOT REPLY: Bug 3215] New: fo:leader with a percentage as leader-length does not display
PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3215 *** shadow/3215 Tue Aug 21 18:17:26 2001 --- shadow/3215.tmp.6643Tue Aug 21 18:17:26 2001 *** *** 0 --- 1,30 + ++ + | fo:leader with a percentage as leader-length does not display | + ++ + |Bug #: 3215Product: Fop | + | Status: NEW Version: all | + | Resolution:Platform: PC | + | Severity: Normal OS/Version: Windows NT/2K | + | Priority: Other Component: general | + ++ + | Assigned To: [EMAIL PROTECTED] | + | Reported By: [EMAIL PROTECTED] | + | CC list: Cc: | + ++ + | URL: | + ++ + | DESCRIPTION | + If leader-length is set to a percentage, the leader is not visible in the + output. All examples in leader.fo that use a percentage for the leader-length + attribute are broken. + + These worked in version 0.19.0 + + Example: + fo:blockfo:leader leader-pattern=rule + rule-thickness=6.0pt + leader-length=100%/ + /fo:block + + Should put a 6.0pt thick rule across the page the full width of the container. + In v0.19.0 it does, in v0.20.0 it does not. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
More Leader Problems
The table of contents example on page 2 of leader.fo isn't working now either. It doesn't display the dots. I think this is related to the percentage problem, because according to the doco, the default for leader-length is 100%. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
fo:leader with leader-length set to a percentage
I'll try again. If you run leader.fo using version 0.20, none of the examples that use a percentage for leader-length work. Is there some formal process for raising bug reports? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
[Bug 2489] - leader CID font bug
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2489 *** shadow/2489 Fri Jul 6 17:15:29 2001 --- shadow/2489.tmp.29458 Tue Jul 17 13:24:52 2001 *** *** 2,9 | leader CID font bug| ++ |Bug #: 2489Product: Fop | ! | Status: NEW Version: all | ! | Resolution:Platform: All | | Severity: MajorOS/Version: Other | | Priority: Other Component: pdf renderer| ++ --- 2,9 | leader CID font bug| ++ |Bug #: 2489Product: Fop | ! | Status: RESOLVEDVersion: all | ! | Resolution: DUPLICATE Platform: All | | Severity: MajorOS/Version: Other | | Priority: Other Component: pdf renderer| ++ *** *** 82,85 } WordArea leaderPatternArea = new WordArea(currentFontState, this.red, this.green, ! == --- 82,90 } WordArea leaderPatternArea = new WordArea(currentFontState, this.red, this.green, ! == ! ! --- Additional Comments From [EMAIL PROTECTED] 2001-07-17 13:24 --- ! ! ! *** This bug has been marked as a duplicate of 2556 *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: leader bug and here is a patch
Sorry for not looking at your patch until now, but I've been on vacation
(a couple of weeks with the cellular turned off and no email access can
actually be quite satisfying!).
The mapping from char to glyph is moved to the PDFRenderer, so there
should be no need to map the chars again (only for calculating widths).
However, the leaders with space patterns was still rendered wrong. That's
because actual spaces was used, I changed it to use InlineSpace. Most
fonts doesn't contain an actual space glyph, but instead maps it to the
missing glyph which usually is just a square.
Tore
On Wed, 4 Jul 2001, Hin-Tak Leung wrote:
Apply this patch to:
xml-fop/src/org/apache/fop/layout/LineArea.java
A bug was introduced between version 1.42 and 1.43 of LineArea
which uses a lot of mapChar to cope with bug 1618 (CVS log has
a typo error instead to 1681), and forgot to change the
leader calculation.
This bug should have caused FOP to crash with any XSL:FO input
that has a leader with dots or space with non-pdf-standard
fonts. I wonder why nobody spotted it in release 0.19? My
last CVS build was May 16 and it worked fine - the fatal bug
was introduced on 12 June and went into release 0.19 and
went unreported for nearly a month...
Somebody please patch this into the CVS tree?
=
*** LineArea.java-bad Tue Jun 12 12:37:42 2001
--- LineArea.java Wed Jul 4 00:44:44 2001
***
*** 751,769
* creates a leader as String out of the given char and the leader
length
* and wraps it in an InlineArea which is returned
*/
! private InlineArea buildSimpleLeader(int charNumber, int leaderLength) {
! int width = this.currentFontState.width(charNumber);
if (width == 0) {
- char c = (char) charNumber;
MessageHandler.errorln(char + c + has width
0. Using width 100 instead.);
width = 100;
}
int factor = (int) Math.floor (leaderLength /
width);
char [] leaderChars = new char [factor];
- char fillChar = (char) charNumber;
for (int i = 0; i factor; i ++) {
! leaderChars[i] = fillChar;
}
WordArea leaderPatternArea =
new WordArea(currentFontState, this.red, this.green,
--- 751,767
* creates a leader as String out of the given char and the leader
length
* and wraps it in an InlineArea which is returned
*/
! private InlineArea buildSimpleLeader(char c, int leaderLength) {
! int width =
this.currentFontState.width(currentFontState.mapChar(c));
if (width == 0) {
MessageHandler.errorln(char + c + has width
0. Using width 100 instead.);
width = 100;
}
int factor = (int) Math.floor (leaderLength /
width);
char [] leaderChars = new char [factor];
for (int i = 0; i factor; i ++) {
! leaderChars[i] = c;
}
WordArea leaderPatternArea =
new WordArea(currentFontState, this.red, this.green,
==
_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
[Bug 2429] - Incorrect handeling of fo:leader attribute leader-pattern
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2429 *** shadow/2429 Tue Jul 3 00:26:23 2001 --- shadow/2429.tmp.21975 Fri Jul 6 17:10:12 2001 *** *** 2,9 | Incorrect handeling of fo:leader attribute leader-pattern | ++ |Bug #: 2429Product: Fop | ! | Status: NEW Version: all | ! | Resolution:Platform: All | | Severity: Normal OS/Version: Linux | | Priority: Other Component: pdf renderer| ++ --- 2,9 | Incorrect handeling of fo:leader attribute leader-pattern | ++ |Bug #: 2429Product: Fop | ! | Status: RESOLVEDVersion: all | ! | Resolution: FIXED Platform: All | | Severity: Normal OS/Version: Linux | | Priority: Other Component: pdf renderer| ++ *** *** 36,39 instead of !3.5 Graphics ... xx --- 36,43 instead of !3.5 Graphics ... xx ! ! --- Additional Comments From [EMAIL PROTECTED] 2001-07-06 17:10 --- ! This is probably the same bug as the one I reported and supplied a patch for ! in the fop-dev mailing list a few days ago - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
