http://blog.gmane.org/gmane.text.xml.fop.user hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.text.xml.fop.user/27034 Hi all, I have recently upgraded my computer to fedora 9 (was fedora core 4) and suddenly fop doesn't work anymore. The X server is running, but I also tried the -Djava.awt.headless=true trick, which didn't work either. Whenever I try to render a page, I am getting this in the logfile: building formatting object tree [1] [1] And then fop hangs. On other machines the output looks like this: building formatting object tree [1] table-layout=auto is not supported, using fixed! Last page-sequence produced 1 pages. Parsing of document complete, stopping renderer Initial heap size: 20749Kb (): Current heap size: 19121Kb Total memory used: -1627Kb Memory use is indicative; no GC was performed These figures should not be used comparatively (): Total time used: 388ms Pages rendered: 1 Avg render time: 388ms/page This applies to JDK 1.6 and fop 0.20.5, but I guess newer versions as well, since they also require X support via Batik, no? I am guessing that some X libraries weren't installed, is there any information which ones are actually needed? Many thanks in advance, Ulrich Ulrich Mayring 2008-10-06T17:58:20 http://permalink.gmane.org/gmane.text.xml.fop.user/27033 Hi, fopFactory.setUserConfig(new File(userConfigPath)); works for me !!! To generate a FOP font metrics file (.xml) and create a UserConfigFile, I have done what's explained here: http://www.sagehill.net/docbookxsl/AddFont.html http://xmlgraphics.apache.org/fop/0.94/fonts.html I use FOP 0.95beta1 but setUserConfig works only after I have excluded the default dependency and add one manually. That's from my pom.xml file : <dependency> <groupId>org.apache.xmlgraphics</groupId> <artifactId>fop</artifactId> <version>0.95beta-1</version> <exclusions> <exclusion> <groupId>org.apache.avalon.framework</groupId> <artifactId>avalon-framework-api</artifactId> </exclusion> </exclusions> </dependency> <dependency> <groupId>avalon</groupId> <artifactId>avalon-framework</artifactId> <version>4.1.4</version> </dependency> eborisow wrote: Frederic W 2008-10-06T16:00:25 http://permalink.gmane.org/gmane.text.xml.fop.user/27032 I am not quite sure what you are after but I do believe the current FOP behavior is correct with respect to the specification. And yes, you won't see any difference in glyph placing in your scenario and nor should you. In the default case line-height is determined by the 'em' box defined by the font (which is a fixed size box (at least in height) for a given font) plus a small margin for line spacing (the half-leading). The fonts 'em' box also defines the position of the default alignment baseline. This guarantees that in a paragraph written in the same font all lines are equally spaced independent of which sets of glyphs from the font appear on each line. It also guarantees if you have two paragraphs in adjacent cells in a table both using the same font that all lines are properly aligned across the cells (assuming identical settings). Both of these effects are highly desirable in common typesetting scenarios. You can manipulate this behavior by adjusting various properties, like line-height, line-stacking-strategy, alignment-baseline, .... Manuel Mall 2008-10-06T12:07:55 http://permalink.gmane.org/gmane.text.xml.fop.user/27031 Hi, I have a requirement to do the following: Text will be on the right-hand pages (even) with supporting illustration on the facing left-hand pages (odd). Is this possible using xsl-fo? I am generating the FO from xslt. Text and graphics can be just about any where in the markup, so I am having trouble trying to figure this out. Thanks in advance, Phil Philip V 2008-10-06T11:44:01 http://permalink.gmane.org/gmane.text.xml.fop.user/27030 Vincent Hennebert-2 wrote: I did some more testing and the result is, that the new FOP 0.95 always has the same result: <fo:block text-align="start" font-family="{$Font}" font-size="20pt" color="{$TitleFontColor}"> <xsl:text>geeeeeeeeeeeeeeeeee</xsl:text> </fo:block> No matter if I only set capital letters or only small caps, only "gjy" or with/without paranthesis, all examples have the same result, i.e. a letter is always placed at the same horizontal position - no matter if/what other letters are in the same line/block. In my example font, the text is always displayed that an "e" is exactly horizontal centered. As you might argue, that it's more "correct" to center the small letters like "e", it looks really awkward if a line/block only has a number, because the digits are also "shifted upwards". In addition, with the fo:inline "workaround", the whole line/block gets a bigger height. :-( j1997 2008-10-06T09:51:07 http://permalink.gmane.org/gmane.text.xml.fop.user/27029 what I am actually trying to do is the following: <!-- Setting chapter title to separate number and label --> <xsl:template name="chaptitle.title"> <xsl:param name="node" select="."/> <xsl:variable name="id"> <xsl:call-template name="object.id"> <xsl:with-param name="object" select="$node"/> </xsl:call-template> </xsl:variable> <fo:block xsl:use-attribute-sets="chap.label.properties"> <xsl:apply-templates select="$node" mode="label.markup"/> </fo:block> <fo:block xsl:use-attribute-sets="chap.title.properties"> <fo:list-block provisional-distance-between-starts="1cm + 8pt" provisional-label-separation="8pt"> <fo:list-item> <fo:list-item-label end-indent="label-end()"> <fo:block> <fo:external-graphic> <xsl:attribute name="src"> <xsl:call-template name="fo-external-image"> <xsl:with-param name="filename" select=concat('images', < at >icon, '.png'/> </xsl:call-template> </xsl:attribute> </fo:external-graphic> </fo:block> </fo:list-item-label> <fo:list-item-body start-indent="body-start()"> <fo:block> <xsl:apply-templates select="$node" mode="title.markup"/> </fo:block> </fo:list-item-body> </fo:list-item> </fo:list-block> </fo:block> </xsl:template> An then in the xml file itself I set: <chapter icon="advanced"> <title>Advanced Settings</title> .... where "advanced" is the name of the PNG file in the 'images' folder. The question is how I can pass the variable icon value (in this case "advanced") to my chapter template. Thanks in advance! Nancy nancy_b wrote: nancy_b 2008-10-06T08:30:08 http://permalink.gmane.org/gmane.text.xml.fop.user/27028 Hi Andreas, Thanks for your response! The problem with fo-external-graphic is that it does not work as a background for a text that is placed in the footer. ;-( So frustrating... Best wishes, Nancy Andreas Delmelle-2 wrote: nancy_b 2008-10-06T08:23:15 http://permalink.gmane.org/gmane.text.xml.fop.user/27027 Hi Since the image is used as a background, there is no way to scale it to fit the page-width during formatting. This is only possible with either fo:external-graphic or fo:instream-foreign-object (to which the content-height/content-width properties actually apply; not sure to which element they are being added in your code) The only two options I see are: - either pre-scale the 'footer.png' image, so it already has the right dimensions - or abandon the approach of using a background-image, and try to replace it by a fo:external-graphic, which allows you to use the combination of 'width="100%" content-width="scale-to-fit" HTH'! Andreas Andreas Delmelle 2008-10-05T18:17:59 http://permalink.gmane.org/gmane.text.xml.fop.user/27026 Hi This approach fails because the 'foreign' content is not XML. If I interpret correctly, what you are looking for is an fo:external- graphic with a 'data:' URL as its source. Depending on the actual format of the image file, something like: <fo:block> <fo:external-graphic> <xsl:attribute name="src"> <xsl:value-of select="concat('data:image/png;base64,', Immagini/FileBean/FileRawData)" /> </xsl:attribute> </fo:external-graphic> </fo:block> FOP offers support for the data URI scheme out-of-the-box. HTH! Cheers Andreas Andreas Delmelle 2008-10-05T18:04:54 http://permalink.gmane.org/gmane.text.xml.fop.user/27025 Hi guys, I am trying to put an image as a footer separator. But the problem is that it does not cover the whole page width (not including the margins of course). Could you please advise me what I do wrong? Here is the code: <xsl:param name="footer.path" select="'../scripts/images/footer.png'"/> <xsl:template name="foot.sep.rule"> <xsl:param name="pageclass"/> <xsl:param name="sequence"/> <xsl:param name="gentext-key"/> <xsl:if test="$footer.rule != 0"> <xsl:attribute name="background-image"> <xsl:call-template name="fo-external-image"> <xsl:with-param name="filename" select="$footer.path"/> </xsl:call-template> </xsl:attribute> <!--<xsl:attribute name="background-attachment">fixed</xsl:attribute>--> <xsl:attribute name="background-repeat">no-repeat</xsl:attribute> <xsl:attribute name="background-position-horizontal">left</xsl:attribute> <xsl:attribute name="background-position-vertical">center</xsl:attribute> <xsl:attribute name="content-width">80pt</xsl:attribute> <xsl:attribute name="content-height">1cm</xsl:attribute> </xsl:if> </xsl:template> Thanks in advance! nancy_b 2008-10-05T13:42:12 http://permalink.gmane.org/gmane.text.xml.fop.user/27024 Hi all I've this xml with an embedded image: <Immagini> <FileBean> <FileRawData>/9j/4AAQSkZJRgABAQEASABIAAD/2wBDA... I'm trying to display it with something like this without results: <fo:block> <fo:instream-foreign-object> <xsl:value-of select="Immagini/FileBean/FileRawData"/> </fo:instream-foreign-object> </fo:block> can u help me? Dox danyolgiax 2008-10-05T12:05:03 http://permalink.gmane.org/gmane.text.xml.fop.user/27023 Hi guys, Using Docbook XML/XSL and FOP 0.94 on Linux Debian. Has any of you tried to add an icon before a chapter/section title? Asked the same question on the Docbook forum, but no answer. Thank you all in advance! Nancy nancy_b 2008-10-04T22:27:33 http://permalink.gmane.org/gmane.text.xml.fop.user/27022 FWIW: I don't think this property will really solve anything. "line- stacking-strategy" tells the formatter how the lines in a given block are to be stacked, or IOW, which height will be used for each line- area. For a value of "max-height", the actual line-height can vary for each line, depending on the content. (in the Recommendation's terms: each line will use the 'maximum-line-rectangle') So, if an image appears in the line, and the image is larger than the largest glyph, then the line will be as high as that image (plus half-leading). For a value of "font-height", the lines for a given block will all have the same actual height, which depends on the font(-size) of the block in question (in the Recommendation's terms: each line will use the 'nominal-requested-line-rectangle'). Result is that the same image would now overflow the previous or next line(s), since it does not fit. Analogous reasoning for nested inlines or wrappers with a different font or simply a larger font-size than the block. FOP currently offers support for those two values: max-height and font-height. The value of line-height is not supported. I haven't checked yet whether FOP follows the Recommendation here, and does the same for line-height as it does for max-height. What you can do, by specifying "font-height", is make sure that the lines in cell 1.1 are always exactly the same height as in cell 1.2, with the described side-effect for embedded text in a larger font(- size) or larger images. Cheers Andreas Andreas Delmelle 2008-10-04T08:47:40 http://permalink.gmane.org/gmane.text.xml.fop.user/27021 Hi Jeff, For that purpose, you should use your background image with an fo:external-object in absolute position in a static content, using an fo:block-container. FYI, with FOP 0.9x, static content is drawn before (and then below) flow content. HTH, Pascal Pascal Sancho 2008-10-03T14:51:00 http://permalink.gmane.org/gmane.text.xml.fop.user/27020 Thanks for the reply.The exception is thrown when a page is addressed which does not exist. So I guess the exception is one way of dealing with that. I would find it easier to get a missing image warning in the log in such cases and see the rendering process continued. Similar to what happens with image references that do not exist. Peter org.apache.fop.render.pdf.PDFRenderer.renderImage(PDFRenderer.java:1679>>>>>>>> ) org.apache.fop.render.pdf.PDFRenderer.renderBlock(PDFRenderer.java:1329>>>>>>>> ) org.apache.fop.render.pdf.PDFRenderer.renderBlock(PDFRenderer.java:1329>>>>>>>> ) org.apache.fop.render.pdf.PDFRenderer.renderBlock(PDFRenderer.java:1329>>>>>>>> ) org.apache.fop.render.pdf.PDFRenderer.renderBlock(PDFRenderer.java:1329>>>>>>>> ) Peter Coppens 2008-10-03T14:28:09 http://permalink.gmane.org/gmane.text.xml.fop.user/27019 FOP-0.95 Redhat Linux I have a background image in the "region-body". It looks great and prints perfectly. However, I just noticed that I want the background image to occupy more space in the region-body (just make it bigger). I do not see where I am able to specify the size of the image. Do I have to manipulate the .png/.jpg outside of FOP or can I set the height/width inside FOP and then it will automatically resize the image? Jeff Steffanina, Jeff 2008-10-03T14:25:46 http://permalink.gmane.org/gmane.text.xml.fop.user/27018 Hi, Jeremias tells me that he is on holidays ! I have no solution for you but you can check that: - The pdf to include has a version lower or equal than 1.4 (Acrobat 5.x) because I think that FOP creates a pdf with a version equal to 1.4 - The pdf to include is not bigger that the available space. Don't forget that you have maybe margin in your fo:simple-page-master - If your pdf has several page, I have done a block for each page. for example : <fo:block break-before="page"> <fo:external-graphic src="Part21.pdf#page=3"/> </fo:block> It was the same problem with Antenna House. In fact, I have in the xml, the number of page and I have done a loop. Peter Coppens wrote: Frederic W 2008-10-03T14:04:22 http://permalink.gmane.org/gmane.text.xml.fop.user/27017 Hi, j1997 wrote: I guess FOP 0.20.5 was taking the height of the biggest letter for the line height, which is wrong; what’s supposed to happen if you put a word like ‘jaguar’ in one cell, and ‘ToDo’ in the next cell? Should the baselines be aligned or not? Details can be found in section 4.5 of the XSL-FO specification [1] (who said this section was scary?). In short, the line height is the sum of text-altitude and text-depth [2]. Those are taken from the font metrics and are general (i.e., apply to every glyph, even those that don’t hang below the baseline). So the effect is what you noticed: if a word doesn’t have any letter with a descender, it will look like it’s shifted, whereas technically speaking it’s not. [1] http://www.w3.org/TR/xsl11/#area-line [2] http://www.w3.org/TR/xsl11/#text-depth Not sure there is any other workaround, I’m afraid. If text-depth were implemented you could use that, although that would also require to tweak your stylesheet anyway. Maybe some particular value of the line-stacking-strategy property may do the job, but this property remains cryptic to me. If that doesn’t really help, I hope this clarified FOP’s behaviour. Vincent Vincent Hennebert 2008-10-03T10:23:12 http://permalink.gmane.org/gmane.text.xml.fop.user/27016 Lou, That did the trick..... THANK YOU for your help. Jeff ________________________________ From: Louis.Masters< at >log-net.com [mailto:Louis.Masters< at >log-net.com] Sent: Thursday, October 02, 2008 12:03 PM To: fop-users< at >xmlgraphics.apache.org Subject: Re: Trying to add a footer Did you forget to define your "footer" attribute set? If you don't need it, remove that from the block and you should be OK: A very simple example: <fo:static-content flow-name="region-after-first"> <xsl:call-template name="poFooter"/> </fo:static-content> <xsl:template name="poFooter"> <fo:block space-before="1mm" font-size="7pt" text-align="end"> Page <fo:page-number/> of <fo:page-number-citation ref-id="lastpage"/> </fo:block> <xsl:call-template name = "copyright"/> </xsl:template> OK? -Lou Steffanina, Jeff 2008-10-03T01:23:44 http://permalink.gmane.org/gmane.text.xml.fop.user/27015 ... Well, 'gunk' may not be the right word, but at the bottom of the help lines are shown these lines (after executing 'fop' with no arguments): Oct 2, 2008 7:19:47 PM org.apache.fop.cli.Main startFOP SEVERE: Exception org.apache.fop.apps.FOPException: No input file specified at org.apache.fop.cli.CommandLineOptions.checkSettings(CommandLineOptions.java:801) at org.apache.fop.cli.CommandLineOptions.parse(CommandLineOptions.java:153) at org.apache.fop.cli.Main.startFOP(Main.java:155) at org.apache.fop.cli.Main.main(Main.java:202) So, whatever you call it, it shouldn't be there. ... I think I confused the outputs and didn't report correctly. Sorry. Thanks, Vincent, I will. -Tom Tom Browder 2008-10-03T01:09:40 http://permalink.gmane.org/gmane.text.xml.fop.user/27014 FWIW: You could also eliminate the need to use another tool to do the indenting, and obtain a similar effect by adding <xsl:output ... indent="yes" /> to the main stylesheet. With Saxon you'll get indented XML as a result by default (3 spaces added for each level). The number of spaces can be controlled via the saxon:indent-spaces extension attribute (on xsl:output) Xalan offers xalan:indent-amount for control the amount of spaces to add for each level, which defaults to zero, so only adds linefeeds unless the extension attribute indicates otherwise. Andreas Andreas Delmelle 2008-10-02T21:40:56 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.text.xml.fop.user