DO NOT REPLY [Bug 32671] - fo:text with no fo:block ancestor when using fo:title
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=32671. 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=32671 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2004-12-22 19:23 --- This is only a rough solution: leaders, external graphics, page numbers cause null pointer exceptions. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 32671] New: - fo:text with no fo:block ancestor when using fo:title
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=32671. 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=32671 Summary: fo:text with no fo:block ancestor when using fo:title Product: Fop Version: 1.0dev Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: general AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] When using fo:titlefoo/fo:title (which seems perfectly legal), FOP dies with a NullPointerException after giving the message Unexpected: fo:text with no fo:block ancestor. The exception is raised in org.apache.fop.fo.FOText.createBlockPointers(FOText.java:199), which tries to find a fo:block ancestor, gives the Unexpected message when it reaches Root, and then loops back and gets a NullPointerException. Inserting a break; after the Unexpected message instead gives a ClassCastException at org.apache.fop.layoutmgr.ContentLayoutManager.addChildLM(ContentLayoutManager.java:287), where it tries to add an org.apache.fop.layoutmgr.InlineStackingLayoutManager, which isn't an InlineLevelLayoutManager. I'll add an attachment with sample code. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 32671] - fo:text with no fo:block ancestor when using fo:title
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=32671. 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=32671 --- Additional Comments From [EMAIL PROTECTED] 2004-12-13 20:02 --- Created an attachment (id=13746) -- (http://issues.apache.org/bugzilla/attachment.cgi?id=13746action=view) Test file to trigger the bug Use: ./fop.sh frotz.fo frotz.pdf -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 26163] - margin-left in nested fo:block not used in PDF output
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=26163. 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=26163 margin-left in nested fo:block not used in PDF output --- Additional Comments From [EMAIL PROTECTED] 2004-10-05 06:48 --- Cf. bug 31537 : http://nagoya.apache.org/bugzilla/show_bug.cgi?id=31537
DO NOT REPLY [Bug 26163] - margin-left in nested fo:block not used in PDF output
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=26163. 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=26163 margin-left in nested fo:block not used in PDF output [EMAIL PROTECTED] changed: What|Removed |Added Priority|Other |Medium --- Additional Comments From [EMAIL PROTECTED] 2004-06-18 13:20 --- I am seeing a bug that is probably related to this one. It suggests to me that inheritance is not operating properly for list-blocks, at least for spacing and possibly in general. The scenario I am seeing is as follows: Given fo:list-item-body start-indent=body-start() fo:block ... /fo:block /fo:list-item-body The fo:block will indent as expected -- that is, it will appear at the indentation position that is expected of the list-item-body. If, however, a start-indent is specified for the fo:block: fo:list-item-body start-indent=body-start() fo:block start-indent=0.25in ... /fo:block /fo:list-item-body then the fo-block is indented **relative to the indentation of the containing fo:list-block I have not tried it, but it would be interesting to see what the effect would be of specifying fo:block indent=0. I haven't looked at the code, but my suspicion is that either (a) the start-indent inheritance processing within FOP has a bug of some sort, or (b) the XSL-FO specification got the inheritance specification wrong. At the moment, I'm leaning toward FOP as the culprit. BTW, this problem is not in any way docbook specific. It's purely a fop issue.
DO NOT REPLY [Bug 17999] - @border in fo:block : overwrites area page margin
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=17999. 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=17999 @border in fo:block : overwrites area page margin --- Additional Comments From [EMAIL PROTECTED] 2004-01-31 22:46 --- Created an attachment (id=10171) PDF illustraion
DO NOT REPLY [Bug 17999] - @border in fo:block : overwrites area page margin
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=17999. 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=17999 @border in fo:block : overwrites area page margin --- Additional Comments From [EMAIL PROTECTED] 2004-01-31 22:49 --- I've attached a illustrating PDF example There is a fix though. use padding and set margin to 0. Works for me, see illustration. So maybe there is a bug in the padding calculation routine if margin is not set. Though margin seems buggy too. I've tried to document as good as possible in the pdf. I ran across this when doing an envelope window + folding marker page as you can see. kindest regards, moritz angermann
DO NOT REPLY [Bug 26163] New: - margin-left in nested fo:block not used in PDF output
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=26163. 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=26163 margin-left in nested fo:block not used in PDF output Summary: margin-left in nested fo:block not used in PDF output Product: Fop Version: 0.20.5 Platform: PC OS/Version: Linux Status: NEW Severity: Normal Priority: Other Component: pdf renderer AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Attached to this bug report, is - A DocBook XML source file - An XSL:FO file generated from the DocBook XML source file, using the DocBook XSLT style sheets - A PDF file generated from the XSL:FO file using FOP 0.20.5 The DocBook XML source file uses nested variablelist elements, containing terms and their descriptions. In the generated PDF, the description is indented wrt. to the term in the top level variablelist, but not in the nested variablelist (the terms and their description have the same indentation). The reason is that FOP doesn't use the margin-left=0.25in value in the nested fo:block elements in the XSL:FO file. The value of this property should be taken as relative to the containing block, but it isn't.
DO NOT REPLY [Bug 26163] - margin-left in nested fo:block not used in PDF output
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=26163. 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=26163 margin-left in nested fo:block not used in PDF output --- Additional Comments From [EMAIL PROTECTED] 2004-01-15 12:14 --- Created an attachment (id=9960) DocBook XML source file containing nested variablelist elements.
DO NOT REPLY [Bug 26163] - margin-left in nested fo:block not used in PDF output
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=26163. 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=26163 margin-left in nested fo:block not used in PDF output --- Additional Comments From [EMAIL PROTECTED] 2004-01-15 12:17 --- Created an attachment (id=9961) XSL:FO file generated from DocBook XML example with nested variablelist elements.
DO NOT REPLY [Bug 26163] - margin-left in nested fo:block not used in PDF output
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=26163. 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=26163 margin-left in nested fo:block not used in PDF output --- Additional Comments From [EMAIL PROTECTED] 2004-01-15 12:18 --- Created an attachment (id=9962) PDF file showing missing description indentation in nested variablelists
DO NOT REPLY [Bug 24663] New: - fo:block space-after property needs fixing
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=24663. 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=24663 fo:block space-after property needs fixing Summary: fo:block space-after property needs fixing Product: Fop Version: 1.0dev Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: page-master/layout AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] As described in the below emails, some layout bugs are still present with the space-after property of fo:block: http://marc.theaimsgroup.com/?l=fop-devm=106858060129674w=2 http://marc.theaimsgroup.com/?l=fop-cvsm=106855860132454w=2
DO NOT REPLY [Bug 23765] - [PATCH] trailing spaces in fo:block loses last word.
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=23765. 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=23765 [PATCH] trailing spaces in fo:block loses last word. [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2003-10-16 23:58 --- Patch applied--thanks for reporting and solving the bug for us!
DO NOT REPLY [Bug 19268] - fo:block with padding = region-body overwrites region-after
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=19268. 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=19268 fo:block with padding = region-body overwrites region-after --- Additional Comments From [EMAIL PROTECTED] 2003-10-14 10:06 --- When writing a table into the body of a page depending on weather the content of a cell in the last row that fits on that page wraps or not, FOP may write an extra row of the table into the 'region after'. My Page layout is : fo:simple-page-master master-name=basic-statement page-height=297mm page-width=210mm margin-top=15mm margin-bottom=15mm margin-left=15mm margin-right=15mm fo:region-body margin-top=phd; margin-bottom=pft; margin-left=plft; margin-right=prgt;/ fo:region-before extent=phd;/ fo:region-afterextent=pft;/ fo:region-startextent=plft;/ fo:region-end extent=prgt;/ /fo:simple-page-master For what it's worth the entities are: !ENTITY prgt 5mm !ENTITY plft 5mm !ENTITY phd 60mm !ENTITY pft 20mm Also I am using a 10mm pad-after on each table cell in the table So as far as I can see there should be no way that rows written into the main body can leak into the region after. After some messing around I can correct the problem by chnaging the padding. I chnaged all the fo:table-cell padding-before =bcellpad; to fo:table-cell padding-after=bcellpad; and now it is OK. I assume this is the same bug manifesting itself in a slightly different way.
DO NOT REPLY [Bug 23765] New: - [PATCH] trailing spaces in fo:block loses last word.
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=23765. 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=23765 [PATCH] trailing spaces in fo:block loses last word. Summary: [PATCH] trailing spaces in fo:block loses last word. Product: Fop Version: 1.0dev Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: page-master/layout AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Trailing spaces in a fo:block causes the last word in the block to be lost if the word should be broken into a new line. It can be reproduced with the lastword.fo: ./fop.sh -fo lastword.fo -pdf lastword.pdf The last word 'word10' is missing from the pdffile.
DO NOT REPLY [Bug 23765] - [PATCH] trailing spaces in fo:block loses last word.
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=23765. 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=23765 [PATCH] trailing spaces in fo:block loses last word. --- Additional Comments From [EMAIL PROTECTED] 2003-10-13 10:57 --- Created an attachment (id=8550) A patch that fixes the issue.
DO NOT REPLY [Bug 18702] - fo:block with fo:inline: size calucation
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=18702. 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=18702 fo:block with fo:inline: size calucation --- Additional Comments From [EMAIL PROTECTED] 2003-04-04 12:49 --- Created an attachment (id=5645) Hardcopies correct / incorrect - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 17999] New: - @border in fo:block : overwrites area page margin
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=17999. 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=17999 @border in fo:block : overwrites area page margin Summary: @border in fo:block : overwrites area page margin Product: Fop Version: 0.20.5 Platform: PC OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: general AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I tried the following example code using 0.20.5rc2 for pdf-rendering: ?xml version=1.0 encoding=iso-8859-1? xsl:stylesheet version=1.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform; xmlns:fo=http://www.w3.org/1999/XSL/Format; xmlns:xalan=http://xml.apache.org/xslt; xsl:output method=xml encoding=iso-8859-1 omit-xml-declaration=no indent=yes/ xsl:template match=/ fo:root fo:layout-master-set fo:simple-page-master master-name=one margin-right=50pt margin-left=50pt margin-bottom=50pt margin-top=50pt page-width=8in page-height=12in fo:region-body/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence master-reference=one fo:flow flow-name=xsl-region-body fo:block fo:leader rule-style=ridge leader-length=100% leader-pattern=rule rule-thickness=1px color=black/ /fo:block fo:block border-after-color=red border-after-style=outset border-after-width=1em border-before-color=blue border-before-style=outset border-before-width=1.5em border-end-color=silver border-end-style=outset border-end-width=2em border-start-color=green border-start-style=outset border-start-width=2em padding=6pt width=4in A paragraph with a completely specified border. Style is shared as 'outset', color varies on each edge, as does width. /fo:block /fo:flow /fo:page-sequence /fo:root /xsl:template /xsl:stylesheet I expected an output like figure 7.10 as described in http://www.dpawson.co.uk/xsl/sect3/bk/ch08.html; but got a border that overwrites the block area. The border overpaints the page margins!? Regards, Joachim Unger - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 17584] New: - Using fo:block/ to force a line break creates multiple identical output lines
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=17584. 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=17584 Using fo:block/ to force a line break creates multiple identical output lines Summary: Using fo:block/ to force a line break creates multiple identical output lines Product: Fop Version: 0.20.5 Platform: PC OS/Version: Linux Status: NEW Severity: Normal Priority: Other Component: pdf renderer AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The FO code below attempts to render the words 'Here is a line break' with a forced newline after 'Here'. The HTML equivalent would be 'Here br/ is a line break' The newline is created with an empty fo:block/, which seems to be a common technique. This code works fine with 0.20.3 0.20.4... But under 0.20.5rc2 it repeats the whole line twice with no line break after 'Here' - ie Here is a line break Here is a line break. I have replicated this behaviour on two Red Hat systems using this and other (larger) test documents. fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set fo:simple-page-master master-name=only fo:region-body region-name=xsl-region-body margin=1in padding=6pt / fo:region-before region-name=xsl-region-before extent=1in / fo:region-after region-name=xsl-region-after extent=1in / /fo:simple-page-master /fo:layout-master-set fo:page-sequence master-reference=only fo:flow flow-name=xsl-region-body fo:blockHerefo:block/ is a line break/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 17584] - Using fo:block/ to force a line break creates multiple identical output lines
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=17584. 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=17584 Using fo:block/ to force a line break creates multiple identical output lines [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Additional Comments From [EMAIL PROTECTED] 2003-03-03 10:48 --- BTW inserfing fo:block/ as a br/ replacement is bad style. *** This bug has been marked as a duplicate of 17472 *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 8391] - padding-start/end not working on fo:block
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=8391. 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=8391 padding-start/end not working on fo:block [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2002-11-26 14:22 --- Fist of all you should use start-indent property to indent a block. Try fo:block start-indent=10mmtest/fo:block Using padding in xsl-fo is a little bit tricky due to a burden of CSS compatibility. See spec description and formulaes [1]. Shortly speaking one have to specify corresponding margin to get indentation with padding property. This one wont indent fo:block padding-start=10mmtest/fo:block This one will indent fo:block padding-start=10mm margin-left=0mmtest/fo:block I believe FOP is right in this behavior and btw antenna and XEP manifest the same. [1] http://www.w3.org/TR/xsl/slice5.html#section-N5987-Margin,-Space,-and-Indent-Properties - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 12164] - Strange Behaviour using letter-spacing and text-align on fo:block
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=12164. 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=12164 Strange Behaviour using letter-spacing and text-align on fo:block [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2002-11-26 15:20 --- Cannot reproduce the problem, works fine in fop 0.20.4. Your test case contains xml and html file hence doesn't help much. Verify it with fop 0.20.4 and if it still doesn't work, provide a small fo example, please. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 11783] - fo:block background-color=xtext/fo:block generates svg:rect with negative height
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=11783. 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=11783 fo:block background-color=xtext/fo:block generates svg:rect with negative height --- Additional Comments From [EMAIL PROTECTED] 2002-08-19 11:55 --- This problem appears even if the background-color attribute is not specified - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 8990] - background-color works when in fo:block but not fo:inline
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=8990. 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=8990 background-color works when in fo:block but not fo:inline [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Additional Comments From [EMAIL PROTECTED] 2002-06-03 11:02 --- *** This bug has been marked as a duplicate of 4510 *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 8990] New: - background-color works when in fo:block but not fo:inline
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=8990. 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=8990 background-color works when in fo:block but not fo:inline Summary: background-color works when in fo:block but not fo:inline Product: Fop Version: 0.20.3 Platform: All OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: pdf renderer AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Specification says that the background-color property should work within all elements; however, it doesn't work when within fo:inline. fo:block works but there may be cases where you only want specific words highlighted in the PDF file, not a whole paragraph. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 8391] - padding-start/end not working on fo:block
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=8391. 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=8391 padding-start/end not working on fo:block --- Additional Comments From [EMAIL PROTECTED] 2002-04-23 08:41 --- Another possible work-around: padding seems to work if there's a margin-?=0mm specified. Example: fo:block padding-left=1cm margin-left=0cm The problem seems to be in property evaluation. NIST tests clearly show that this is a bug. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 5805] - fo:block text-align=endfo:page-number-citation ref-id={generate-id(.)}//fo:block doesn't right align
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=5805.
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=5805
fo:block text-align=endfo:page-number-citation
ref-id={generate-id(.)}//fo:block doesn't right align
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution||DUPLICATE
--- Additional Comments From [EMAIL PROTECTED] 2002-04-22 11:38 ---
*** This bug has been marked as a duplicate of 1130 ***
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 8391] New: - padding-start/end not working on fo:block
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=8391. 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=8391 padding-start/end not working on fo:block Summary: padding-start/end not working on fo:block Product: Fop Version: 0.20.3 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: page-master/layout AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I wanted to create an indented block and started with using a fo:block element with padding-start/end and padding-before/after attributes. The padding-before/after worked fine but the padding-start/end seemed to be ignored. Possible workaround: Put the block into a table with a single cell and set the padding-start/end attributes on the table cell and not on the block. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 5124] - fo:block-container is not rendered properly using -pcl option
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=5124. 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=5124 fo:block-container is not rendered properly using -pcl option [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] Summary|fo:block-container is not |fo:block-container is not |rendered properly using -pcl|rendered properly using -pcl |option |option - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 4492] - text-decoration=underline on fo:block ignored
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=4492. 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=4492 text-decoration=underline on fo:block ignored [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2002-02-08 18:29 --- Done, see 0.20.3RC - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
center image in a fo:block ?
hi ! how can i center a table horizontally on a page and how can i center an image in a fo:block horizontally and vertically ? thanks Nick Winger (Software-Developer) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 5805] New: - fo:block text-align=endfo:page-number-citation ref-id={generate-id(.)}//fo:block doesn't right align
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=5805.
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=5805
fo:block text-align=endfo:page-number-citation
ref-id={generate-id(.)}//fo:block doesn't right align
Summary: fo:block text-align=endfo:page-number-citation ref-
id={generate-id(.)}//fo:block doesn't right align
Product: Fop
Version: all
Platform: PC
OS/Version: Windows 9x
Status: NEW
Severity: Normal
Priority: Other
Component: general
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
I've produced the following much simplified fo file. It produces a PDF with a
front page ToC. The ToC contains the title of the section, it's number in the
sequence of title elements and its page reference fo:page-number-citation ref-
id={generate-id(.)}/.
Both the sequence number and the page number are placed in fo:block text-
align=end elements. Whilst this works fine for the sequence number, the page
citation is not properly right aligned. More specifically, whilst the element
is right aligned in the table cell, the list it produces is dog-legged. The
xsl file i use is:
?xml version=1.0?
xsl:stylesheet version=1.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform;
xmlns:fo=http://www.w3.org/1999/XSL/Format;
!-- Turns on indenting --
xsl:output indent=yes/
!-- Executes the template --
xsl:template match=/
!-- Declares the root --
fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format;
!-- Defines the layout master set --
fo:layout-master-set
!-- Defines the simple page master --
fo:simple-page-master master-name=A4 page-
width=210mm page-height=297mm margin-top=10mm margin-bottom=10mm margin-
left=10mm
margin-right=10mm
!-- Defines the Page Body region --
fo:region-body/
/fo:simple-page-master
/fo:layout-master-set
fo:page-sequence master-name=A4 initial-page-
number=1 language=en country=uk
!-- Displays the Page Body --
fo:flow flow-name=xsl-region-body
!-- Displays the Table of Contents in
a 3 column table --
fo:table
fo:table-column column-
width=100mm/
fo:table-column column-
width=20mm/
fo:table-column column-
width=20mm/
fo:table-body
xsl:apply-templates
mode=toc/
/fo:table-body
/fo:table
/fo:flow
/fo:page-sequence
fo:page-sequence master-name=A4 language=en
country=uk
!-- Displays the Page Body --
fo:flow flow-name=xsl-region-body
xsl:apply-templates mode=title/
/fo:flow
/fo:page-sequence
/fo:root
/xsl:template
xsl:template match=text() mode=toc/
xsl:template match=title mode=toc
fo:table-row
fo:table-cell
fo:blockxsl:apply-templates
mode=display//fo:block
/fo:table-cell
fo:table-cell
fo:block text-align=endxsl:value-of
select=count(preceding::title)//fo:block
/fo:table-cell
fo:table-cell
fo:block text-align=endfo:page-number-
citation ref-id={generate-id(.)}//fo:block
/fo:table-cell
/fo:table-row
/xsl:template
xsl:template match=text() mode=title/
xsl:template match=title mode=title
fo:block break-after=page id={generate-id(.)}xsl:apply-
templates mode=display//fo:block
/xsl:template
xsl:template
fo:block-container to put graphic in the margin
Hi FOP experts, ,-, I'm trying to put an icon in the margin alongside some / paragraphs: you know the sort of thing; instruction books | often have symbols next to paragraphs with warnings, for * example. Like this grotty bit of ASCII art. I've tried something like this: xsl:template match=warning fo:block-container position=absolute left=-3em fo:block fo:external-graphic .../ /fo:block /fo:block-container fo:block xsl:apply-templates /fo:block /xsl:template So there are two issues: what is the right way to do this in FO, and is that supported in the current FOP? Should I be using position=absolute or absolute-position=absolute? I'm a bit out-of-my-depth with that kind of detail in the FO spec. Is my negative position to put it in the margin allowed? The FOP web page says that block-container has limited support, but as far as I can see there is no decription of what the limitations are (certainly nothing on the limitations page). Can someone explain? Everything that I've tried so far has failed with the mysterious message: [ERROR]: org.apache.fop.layout.BlockArea (This is with 0.20.2RC.) If anyone has got something like this to work, please get in touch! With many thanks in advance. --Phil. (p.s. the reply address IS valid!) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Please help me to solve strange space problem in fo:block
Hi I am generating a simple document with fixed font family. If the fo:block contains the new line( with the space collapsed), then the next line in PDF is shifted by one character length to the right. FO: fo:page-sequence master-name=simplePM fo:flow flow-name=xsl-region-body fo:block font-family=Courier white-space-collapse=falseThis is a simple fo block. Hello World/fo:block fo:block font-family=Courier wrap-option=no-wrap white-space-collapse=falseThis is a simple fo block. Hello World/fo:block /fo:flow Please look at the attachments for details of FO and PDF. Is it a bug? Or am I writing the invalid XSL FO? Please somebody can look at it. block.pdf block.fo Thanks Mahendar This message is confidential and may also be legally privileged. If you are not the intended recipient, please notify us immediately. You should not copy it or use it for any purpose, nor disclose it's contents to any other person. The views and opinions expressed in this e-mail message are the author's own and may not reflect the views and opinions of Wilco International. block.pdf Description: Binary data block.fo Description: Binary data - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 4492] - text-decoration=underline on fo:block ignored
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=4492. 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=4492 text-decoration=underline on fo:block ignored --- Additional Comments From [EMAIL PROTECTED] 2001-11-28 05:04 --- Christian Geisert [EMAIL PROTECTED] sent this to fop-dev: But to underline one must use fo:inline, right?? At the moment: yes! I have started coding support for underline in blocks some time ago, but it's not finished yet Christian, can you update this bug when you make some progress? Thanks! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 5124] New: - fo:block-container is not rendered properly using -pcl option
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=5124. 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=5124 fo:block-container is not rendered properly using -pcl option Summary: fo:block-container is not rendered properly using -pcl option Product: Fop Version: all Platform: All OS/Version: All Status: NEW Severity: Major Priority: Other Component: general AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The test file border.fo is not rendered properly while output in pcl format. It seems that 1. the xoffset is not needed, i think anymore -it generates out of bound warnings 2. height? is computed in reverse direction causing borders to be printed wrongly. should be +--+-+ | | | +--+-+ and is +--+-+ +--+-+ | | | I have added y=y+h nearby line 207 in addRect(..) and reset xoffset to 0 to quickly fix it but it still needs some more work. Thanks, k.j - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Strange space in fo:block
Hi I am generating a simple document with fixed font family. If the fo:block contains the new line( with the space collapsed), then the next line in PDF is shifted by one character length to the right. FO: fo:page-sequence master-name=simplePM fo:flow flow-name=xsl-region-body fo:block font-family=Courier white-space-collapse=falseThis is a simple fo block. Hello World/fo:block fo:block font-family=Courier wrap-option=no-wrap white-space-collapse=falseThis is a simple fo block. Hello World/fo:block /fo:flow Please look at the attachments for details of FO and PDF: block.pdf block.fo I have tested with the FOP0.15. Is it a bug? Or am I writing the invalid XSL FO File? Thanks Mahendar This message is confidential and may also be legally privileged. If you are not the intended recipient, please notify us immediately. You should not copy it or use it for any purpose, nor disclose it's contents to any other person. The views and opinions expressed in this e-mail message are the author's own and may not reflect the views and opinions of Wilco International. block.pdf Description: Binary data block.fo Description: Binary data - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 4492] New: - text-decoration=underline on fo:block ignored
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=4492. 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=4492 text-decoration=underline on fo:block ignored Summary: text-decoration=underline on fo:block ignored Product: Fop Version: 0.15 Platform: Sun OS/Version: Solaris Status: NEW Severity: Minor Priority: Other Component: general AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] If I set text-decoration=underline on an fo:block it is ignored; if I set it on an inline it works. The XSL 1.0 spec says text-decoration applies to all elements. It also says If the property is specified for a block-level element, it affects all inline-level descendants of the element. Am I missing something, or is FOP getting it wrong? (If I'm misunderstanding it, please explain why - thanks!) Here's an example: ?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 fo:inline text-decoration=underline This will be underlined because the text-decoration is set on the inline element. /fo:inline /fo:block fo:block text-decoration=underline This will not be underlined even though a text-decoration is set on the block element. It also fails when text-decoration is set on basic-link elements. /fo:block /fo:flow /fo:page-sequence /fo:root This is with version 0.20.2-RC (can someone update the list of versions in Bugzilla - it only goes as far as 0.17!). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: fo:block
I had not try this, but how about using a table?, then you can put each block in the same table. Greetings Carmelo - Original Message - From: Pablo Iaria [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, October 15, 2001 3:03 PM Subject: fo:block Hi all, How can I do to have several blocks in the same row ? Example: Suposse I have: fo:blockFirst text/fo:block fo:blockSecond text/fo:block And I want to get First text and second text in the same row. Thanks in advance, Pablo.- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: fo:block
Hi Pablo, I'm not sure what you mean by row. If you mean a line of text, the answer is no, at least not like that. You can try using a leader between the text, replacing the leader-length value with what you want. fo:blockFirst textfo:leader leader-pattern=space leader-length=6cm/Second text/fo:block Or using a table row with several cells and put each of your blocks in a cell. HTH, Karen Pablo Iaria wrote: Hi all, How can I do to have several blocks in the same row ? Example: Suposse I have: fo:blockFirst text/fo:block fo:blockSecond text/fo:block And I want to get First text and second text in the same row. Thanks in advance, Pablo.- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: fo:block
I'm not sure what you mean by row either, but you could use inline instead of block. fo:blockfo:inlineFirst text/fo:inlinefo:inlineSecond text/fo:inline/fo:block this way you don't start Second text on a new line (if new line is what you meant by row). JohnPT Karen Lease [EMAIL PROTECTED] Sent by: To: [EMAIL PROTECTED] fop-dev-return-10875-jthaemlitz=oreillyauto.com@XML. cc: APACHE.ORG Subject: Re: fo:block 10/15/01 03:58 PM Please respond to fop-dev Hi Pablo, I'm not sure what you mean by row. If you mean a line of text, the answer is no, at least not like that. You can try using a leader between the text, replacing the leader-length value with what you want. fo:blockFirst textfo:leader leader-pattern=space leader-length=6cm/Second text/fo:block Or using a table row with several cells and put each of your blocks in a cell. HTH, Karen Pablo Iaria wrote: Hi all, How can I do to have several blocks in the same row ? Example: Suposse I have: fo:blockFirst text/fo:block fo:blockSecond text/fo:block And I want to get First text and second text in the same row. Thanks in advance, Pablo.- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
fo:block-container and page breaks
I put a fo:block break-before=page/ inside a fo:block-container to get a page break but it doesn't work. When I put fo:block break-before=page/ outside the fo:block-container, it works. But I need to use a block-container (for a absolute positionning) Thanks for your help ! Bertrand Rougier - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: fo:block-container and page breaks
Bertrand, Are you trying to get the block-container itself on a new page? In that case I think the normal solution would be to put the break-before property on the block-container itself. However I see this isn't implemented yet in FOP. So what happens if you use fo:block break-before=page/ and then follow it directly with your absolutely positioned block-container? Or are you trying to do something else? Regards, Karen Lease ROUGIER Bertrand wrote: I put a fo:block break-before=page/ inside a fo:block-container to get a page break but it doesn't work. When I put fo:block break-before=page/ outside the fo:block-container, it works. But I need to use a block-container (for a absolute positionning) Thanks for your help ! Bertrand Rougier - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
different fonts in same fo:block ??????
hello, I want to add 2-3 different fonts in same fo:block. means in a paragraph there is serif,Richa,Arial. If i use fo:block it will be in different lines. I tried with fo:inline-sequence.but was in vain. can anyone help me? regards rajiv __ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail http://personal.mail.yahoo.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
