not yet implemented properties
Hi, I am just strating to use Apache FOP. The first test looked quite nice! But now, I have a XSL-FO tutorial that uses some properties, that FOP has not implemented yet. I guess FOP *is* XSL-FO 1.0 conform ? Some of these properties are - font - word-spacing - text-transform Is there a known workaround for these issue? Thanks, Matthias - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: not yet implemented properties
FOP is not FULLY compliant to the W3C XSL-FO 1.0 standard. Here the URL you can check to see what has been or has not been implemented http://xml.apache.org/fop/compliance.html If you want some know issues with Fop go there, you may find some workaround: http://xml.apache.org/fop/fo.html Jack -Message d'origine- De : Matthias Wessendorf [mailto:[EMAIL PROTECTED] Envoyé : mercredi 20 avril 2005 10:41 À : fop-users@xmlgraphics.apache.org Objet : not yet implemented properties Hi, I am just strating to use Apache FOP. The first test looked quite nice! But now, I have a XSL-FO tutorial that uses some properties, that FOP has not implemented yet. I guess FOP *is* XSL-FO 1.0 conform ? Some of these properties are - font - word-spacing - text-transform Is there a known workaround for these issue? Thanks, Matthias - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: FOP - external-graphic in absolutely positioned block container - increase the width and the image vanishes!
J.Pietschmann wrote: Roland Neilands wrote: I have also seen logos disappear when the logo itself was much bigger than the block-container and it spat the dummy rather than scale the image down. I think that was only on certain image types (jpg?). IIRC the image scaling code uses the available space in the page body as the maximum heigth of the image, regardless whether the image is actually placed in static content. The static content is processed after the flow in the body, and if the current page has been completely filled, images in static content may be scaled down to zero or nearly zero height. That's why it is always a good idea From my recent experiments, using absolutely positioned block-containers, I think the image is scaled so that the width is the maximum width of the image but the height is not constrained (though uniformly scaled). So - if your width allows an image size whose height is bigger than the container then the image is not displayed. to provide width and height for images explicitly. I think this is a FOP specific fix (which works in FOP - but not in other XSLFO processors). Unfortunately the height and width attributes are to specify the size of the external-graphic area which the image is allowed to exceed - which is where content-height and content-width come into play? J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.9.18 - Release Date: 19/04/2005 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: LINKS
This page will help: http://www.renderx.com/tutorial.html#Links - Original Message - From: Matthias Wessendorf [EMAIL PROTECTED] To: fop-users@xmlgraphics.apache.org Sent: Wednesday, April 20, 2005 9:59 AM Subject: LINKS Hi, I have currently no idea howto create a *external* hyperlink with XSL-FO In my document I'd like to see something similar to this: a href=http://www.foo.com;bar/a Thx, MW - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: LINKS
And a simple example: fo:basic-link color='teal' external-destination='url(http://www.google.com)' Google /fo:basic-link Matthias Wessendorf wrote: Hi, I have currently no idea howto create a *external* hyperlink with XSL-FO In my document I'd like to see something similar to this: a href=http://www.foo.com;bar/a Thx, MW - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Datalucid Limited 8 Eileen Road South Norwood London SE25 5EJ / tel :0208-239-6810 mob: 0794-725-9760 email: [EMAIL PROTECTED] / UK Co. Reg: 4383635 VAT Reg.: 798 7531 60 -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.9.18 - Release Date: 19/04/2005 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
LINKS
Hi, I have currently no idea howto create a *external* hyperlink with XSL-FO In my document I'd like to see something similar to this: a href=http://www.foo.com;bar/a Thx, MW - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to help producing version 1.0 (was: Re: FOP - -noannotations)
--On Montag, 18. April 2005 21:02 Uhr +0200 Jeremias Maerki [EMAIL PROTECTED] wrote: There are many ways you can help without the need for Java knowledge: - Helping other people on fop-users - Writing test cases - Writing documentation (Wiki or Forrest sources) - Updating the compliance page with additional columns for the new code (thus showing the progress in relation to FOP 0.20.5) - Cleaning up Bugzilla - Consolidating and updating TODO lists - Testing the new code and providing feedback (when the major obstacles are out of the way, probably in one or two months) I did a lot of evaluation FO processor evaluation work over the last weeks. The company I am working for want to produce PDF and RTF from HTML (converted to FO through csstoxslfo). I did also some testing with the current development version of FOP and saw that the PDF still has some problems with tables (the RTF converter seems not to be usable at this time) and larger documents (I get OutOfMemory errors). My customer is a publisher and has a lots of documents for testing. Since we are looking for open-source solution over commercial processors I would be interested in performing further tests...what's the best way to contribute? Andreas pgpmij4j41pGu.pgp Description: PGP signature
Re: Generating table of contents using FO and FOP?
Hi, Mike, I decided to give a non-mode method a go. I also decided to use XSLT 1.0. Here's the result: Given this toy XML source file: book front id=1 !-- Title, copyright, etc. -- chapter title=Known and Suspected Contributors id=11 !-- Content here somewhere! -- /chapter /front body id=2 chapter title=Using Frombotzers id=21 topic title=Using a Deteronic Frombotzer id=211 heading title=Warming up a Deteronic Frombotzer id=2111 !-- and so on -- /heading heading title=Applying a Deteronic Frombotzer id=2112 !-- and so on -- /heading /topic topic title=Using a Widgetizing Frombotzer id=212 heading title=Warming up a Widgetizing Frombotzer id=2121 !-- and so on -- /heading heading title=Applying a Widgetizing Frombotzer id=2122 !-- and so on -- /heading /topic /chapter chapter title=Using Natwoozers id=22 topic title=Using a Deteronic Natwoozer id=221 heading title=Warming up a Deteronic Natwoozer id=2211 !-- and so on -- /heading heading title=Applying a Deteronic Natwoozer id=2212 !-- and so on -- /heading /topic topic title=Using a Widgetizing Natwoozer id=222 heading title=Warming up a Widgetizing Natwoozer id=2221 !-- and so on -- /heading heading title=Applying a Widgetizing Natwoozer id= !-- and so on -- /heading /topic /chapter /body back id=3 !-- appendices, glossary, index -- chapter title=Attorneys with Frombotzer and Natwoozer Experience id=31 !-- The list of attorneys -- /chapter glossary id=glossary !-- glossary entries -- /glossary index id=index !-- index entries -- /index /back /book And applying this XSL file: ?xml version=1.0 encoding=UTF-8? xsl:stylesheet version=1.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform; xmlns:fo=http://www.w3.org/1999/XSL/Format; exclude-result-prefixes=fo xsl:include href=contentsstyles.xsl/ xsl:template match=book !-- All the usual stuff to build a document omitted to focus on the table of contents -- xsl:for-each select=front/chapter fo:block xsl:use-attribute-sets=contents1 fo:basic-link internal-destination=[EMAIL PROTECTED] color=#ffxsl:value-of select=@title//fo:basic-link fo:leader leader-pattern=dots leader-length.maximum=100%/ fo:page-number-citation ref-id=[EMAIL PROTECTED]/ /fo:block /xsl:for-each xsl:for-each select=body/chapter fo:block xsl:use-attribute-sets=contents1 fo:basic-link internal-destination=[EMAIL PROTECTED] color=#ffxsl:value-of select=@title//fo:basic-link fo:leader leader-pattern=dots leader-length.maximum=100%/ fo:page-number-citation ref-id=[EMAIL PROTECTED]/ /fo:block xsl:for-each select=topic fo:block xsl:use-attribute-sets=contents2 fo:basic-link internal-destination=[EMAIL PROTECTED] color=#ffxsl:value-of select=@title//fo:basic-link fo:leader leader-pattern=dots leader-length.maximum=100%/ fo:page-number-citation ref-id=[EMAIL PROTECTED]/ /fo:block xsl:for-each select=heading fo:block xsl:use-attribute-sets=contents3 fo:basic-link internal-destination=[EMAIL PROTECTED] color=#ffxsl:value-of select=@title//fo:basic-link fo:leader leader-pattern=dots leader-length.maximum=100%/ fo:page-number-citation ref-id=[EMAIL PROTECTED]/ /fo:block /xsl:for-each /xsl:for-each /xsl:for-each xsl:for-each select=back/chapter fo:block xsl:use-attribute-sets=contents1 fo:basic-link internal-destination=[EMAIL PROTECTED] color=#ffxsl:value-of select=@title//fo:basic-link fo:leader leader-pattern=dots leader-length.maximum=100%/ fo:page-number-citation ref-id=[EMAIL PROTECTED]/ /fo:block /xsl:for-each fo:block xsl:use-attribute-sets=contents1 fo:basic-link internal-destination=glossary color=#ffGlossary/fo:basic-link fo:leader leader-pattern=dots leader-length.maximum=100%/ fo:page-number-citation ref-id=glossary/ /fo:block fo:block xsl:use-attribute-sets=contents1 fo:basic-link internal-destination=index color=#ffIndex/fo:basic-link fo:leader leader-pattern=dots leader-length.maximum=100%/ fo:page-number-citation ref-id=index/ /fo:block /xsl:template /xsl:stylesheet Produces this FO fragment: fo:block xmlns:fo=http://www.w3.org/1999/XSL/Format; font-size=12pt font-family=sans-serif line-height=16pt space-before.optimum=6pt space-after.optimum=3pt text-align-last=justify fo:basic-link internal-destination=11 color=#ffKnown and Suspected Contributors/fo:basic-link fo:leader leader-pattern=dots
Re: FOP - external-graphic in absolutely positioned block container - increase the width and the image vanishes!
J.Pietschmann wrote: Mike Trotman wrote: From my recent experiments, using absolutely positioned block-containers, I think the image is scaled so that the width is the maximum width of the image but the height is not constrained (though uniformly scaled). I don't think so. Have a look at the code in /fo/flow/ExternalGraphic.java I'm afraid I've only got a binary version of FOP installed - so no source to look at - and my Java is very elementary. I'm referring to the width / height of the containing block-container and may not have phrased it clearly. But the behaviour in FOP seems to be that containing width (not the external-graphic @width) restricts image display size, but height doesn't. (If this isn't what the previous message was about then I've got hold of the wrong idea and you can ignore the rest of this message.) I'm basing my comments on the behaviour of this piece of XSL:FO. 37 fo:static-content flow-name=xsl-region-before 38 fo:block-container position=absolute top=0cm left=0.0cm height=20.5cm width=28cm border=1px solid silver/ 39 fo:block-container position='absolute' top='3cm' left='3cm' height='3in' width='2in' border='3px solid blue' 40 fo:blockfo:external-graphic src='url(images/img_2.jpg)' content-height='0.5in' content-width='0.5in'/ /fo:block 41 fo:block text-align='right' color='red' background-color='yellow'XbeforeX/fo:block 42 /fo:block-container 43 /fo:static-content This displays the image inside the block-container while the width on line 39 is 2.3in (for this particular image). And as I increase the width upwards to 2.3in the image gets larger and larger filling the full width of the bock-container but with an ever decreasing gap at the bottom As soon as the displayed image height exceeds the height of the block-container the image is suppressed. Unfortunately the height and width attributes are to specify the size of the external-graphic area which the image is allowed to exceed Not in the FOP implementation. It may overflow the parent area though. As you say - in FOP the @height and @width on external-graphic do control the size of the image - and this may exceed the parent area. But as I read the spec the external-graphic @height sets the height of the box - but the content may exceed this area(?). I may have got my interpretation of which areas the spec is talking about wrong - although XEP seems to implement them this way. I've only completely read the spec once or twice and usually only refer back when something is not behaving as I expect (which happens quite often!) e.g. when I run the above code through XEP the @content-height/width control the size of the image. If I change these external-graphic attributes to plain @height/width (with no @content-height/width) then the image (which is large) expands well outside the block and block-container but the text in line 41 is positioned under a block which has the specified @height of the external-graphic (and across the front of the image). - which is where content-height and content-width come into play? I always thought the use case for the content-width|height properties is for specifying percentages, e.g. content-width=50% will scale a 4cm wide image down to a 2 cm wide. This is still tricky for bitmap images without an embedded resolution. I'm basing my comments partly on reading the spec. (but not being clear what are the relevant containing areas) and also on the behaviour of the output in XEP. @Content-height/width can have % or length values. % = scale from the image dimensions length= calculate scale to achieve absolute size (?) J.Pietschmann Again - apologies if we're talking at cross-purposes. I'm no expert at XSLFO - particulalry vague on the behaviour of areas and inherited traits and have spent quite a bit of time getting myself confused, unconfused and then confused again by the W3C spec. and the behaviour of various formatters. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.9.18 - Release Date: 19/04/2005 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
