break-after
Hi, Just a question: is the break-after=page attribute on block level implemented in fop 0.90alpha? We had problems with this attribute but when rearranging the things and turning it into break-before=page everything worked well... Regards Dominic - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: break-after
It is supposed to work. We have tests in our test suite that test for the functionality but maybe you hit a bug. Please send an example that shows the problem. On 21.12.2005 09:43:08 Dominic Brügger wrote: Hi, Just a question: is the break-after=page attribute on block level implemented in fop 0.90alpha? We had problems with this attribute but when rearranging the things and turning it into break-before=page everything worked well... Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: break-after
I will send it to your personal email address... Dominic It is supposed to work. We have tests in our test suite that test for the functionality but maybe you hit a bug. Please send an example that shows the problem. On 21.12.2005 09:43:08 Dominic Brügger wrote: Hi, Just a question: is the break-after=page attribute on block level implemented in fop 0.90alpha? We had problems with this attribute but when rearranging the things and turning it into break-before=page everything worked well... Jeremias Maerki - 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]
Bookmark Support in fop-0.90alpha1
Hello List I'm just experimenting with fop-0.90alpha1 and the new Bookmark functionality FOP render these Code without errors : ?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 xsl:output indent=yes/ xsl:template match=/ fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format !--xsl:call-template name=Index/-- !-- Beschreibt, wie eine Seite auszusehen hat -- fo:layout-master-set fo:simple-page-master master-name=mainLayout page-width=297mm page-height=210mm margin-top=0.5cm margin-bottom=0.5cm margin-left=0.5cm margin-right=0.5cm fo:region-body margin-top=0.5cm margin-bottom=0.5cm/ fo:region-before extent=0.5cm/ fo:region-after extent=0.5cm/ /fo:simple-page-master !-- ## -- fo:page-sequence-master master-name=contents fo:repeatable-page-master-reference master-reference=mainLayout/ /fo:page-sequence-master /fo:layout-master-set fo:bookmark-tree fo:bookmark internal-destination=headDest3 fo:bookmark-titleBookmarks Example/fo:bookmark-title fo:bookmark internal-destination=headDest3 fo:bookmark-titleHello World/fo:bookmark-title /fo:bookmark fo:bookmark internal-destination=chapter2 fo:bookmark-titleParagraphs/fo:bookmark-title /fo:bookmark /fo:bookmark /fo:bookmark-tree !-- Inhalt von mainLayout -- fo:page-sequence master-reference=mainLayout initial-page-number=1 !-- Kopfzeile -- fo:static-content flow-name=xsl-region-before fo:block font-size=22 text-align=center background-color=greyKAMPF - Fehlteilliste V2/fo:block /fo:static-content !-- Hauptbereich -- fo:flow flow-name=xsl-region-body xsl:apply-templates select=//STUECKLISTE/ fo:block id=last-page/ /fo:flow /fo:page-sequence /fo:root /xsl:template ... But in the resulting PDF are no Bookmarks. Can somebody give me a example or tell whats wrong. Thanks : Joern Karthaus
Re: Bookmark Support in fop-0.90alpha1
Please check the log output from FOP. If the bookmark code cannot find an id in the document that you refer to using internal-destination then the bookmarks seem to be skipped at the moment. On 21.12.2005 12:10:59 Joern.Karthaus wrote: Hello List I'm just experimenting with fop-0.90alpha1 and the new Bookmark functionality FOP render these Code without errors : ?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; xsl:output indent=yes/ xsl:template match=/ fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; !--xsl:call-template name=Index/-- !-- Beschreibt, wie eine Seite auszusehen hat -- fo:layout-master-set fo:simple-page-master master-name=mainLayout page-width=297mm page-height=210mm margin-top=0.5cm margin-bottom=0.5cm margin-left=0.5cm margin-right=0.5cm fo:region-body margin-top=0.5cm margin-bottom=0.5cm/ fo:region-before extent=0.5cm/ fo:region-after extent=0.5cm/ /fo:simple-page-master !-- ## -- fo:page-sequence-master master-name=contents fo:repeatable-page-master-reference master-reference=mainLayout/ /fo:page-sequence-master /fo:layout-master-set fo:bookmark-tree fo:bookmark internal-destination=headDest3 fo:bookmark-titleBookmarks Example/fo:bookmark-title fo:bookmark internal-destination=headDest3 fo:bookmark-titleHello World/fo:bookmark-title /fo:bookmark fo:bookmark internal-destination=chapter2 fo:bookmark-titleParagraphs/fo:bookmark-title /fo:bookmark /fo:bookmark /fo:bookmark-tree !-- Inhalt von mainLayout -- fo:page-sequence master-reference=mainLayout initial-page-number=1 !-- Kopfzeile -- fo:static-content flow-name=xsl-region-before fo:block font-size=22 text-align=center background-color=greyKAMPF - Fehlteilliste V2/fo:block /fo:static-content !-- Hauptbereich -- fo:flow flow-name=xsl-region-body xsl:apply-templates select=//STUECKLISTE/ fo:block id=last-page/ /fo:flow /fo:page-sequence /fo:root /xsl:template ... But in the resulting PDF are no Bookmarks. Can somebody give me a example or tell whats wrong. Thanks : Joern Karthaus Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re:Re: Bookmark Support in fop-0.90alpha1
Thanks Jeremias for your Quick Answer I found the Reason : When you use the internal-destination=headDest3 twice (with the same ID [I do so for testing]) then the complete Bookmark is skipped ! Is this a bug ? Joern Karthaus Please check the log output from FOP. If the bookmark code cannot find an id in the document that you refer to using internal-destination then the bookmarks seem to be skipped at the moment. On 21.12.2005 12:10:59 Joern.Karthaus wrote: Hello List I'm just experimenting with fop-0.90alpha1 and the new Bookmark functionality FOP render these Code without errors : ?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 xsl:output indent=yes/ xsl:template match=/ fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format !--xsl:call-template name=Index/-- !-- Beschreibt, wie eine Seite auszusehen hat -- fo:layout-master-set fo:simple-page-master master-name=mainLayout page-width=297mm page-height=210mm margin-top=0.5cm margin-bottom=0.5cm margin-left=0.5cm margin-right=0.5cm fo:region-body margin-top=0.5cm margin-bottom=0.5cm/ fo:region-before extent=0.5cm/ fo:region-after extent=0.5cm/ /fo:simple-page-master !-- ## -- fo:page-sequence-master master-name=contents fo:repeatable-page-master-reference master-reference=mainLayout/ /fo:page-sequence-master /fo:layout-master-set fo:bookmark-tree fo:bookmark internal-destination=headDest3 fo:bookmark-titleBookmarks Example/fo:bookmark-title fo:bookmark internal-destination=headDest3 fo:bookmark-titleHello World/fo:bookmark-title /fo:bookmark fo:bookmark internal-destination=chapter2 fo:bookmark-titleParagraphs/fo:bookmark-title /fo:bookmark /fo:bookmark /fo:bookmark-tree !-- Inhalt von mainLayout -- fo:page-sequence master-reference=mainLayout initial-page-number=1 !-- Kopfzeile -- fo:static-content flow-name=xsl-region-before fo:block font-size=22 text-align=center background-color=greyKAMPF - Fehlteilliste V2/fo:block /fo:static-content !-- Hauptbereich -- fo:flow flow-name=xsl-region-body xsl:apply-templates select=//STUECKLISTE/ fo:block id=last-page/ /fo:flow /fo:page-sequence /fo:root /xsl:template ... But in the resulting PDF are no Bookmarks. Can somebody give me a example or tell whats wrong. Thanks : Joern Karthaus Jeremias Maerki
Re: Bookmark Support in fop-0.90alpha1
Yes, this seems to be a bug. Only the first bookmark receives the resolved target. The second one is skipped. I've filed a bug in Bugzilla. http://issues.apache.org/bugzilla/show_bug.cgi?id=37993 On 21.12.2005 15:03:26 Joern.Karthaus wrote: Thanks Jeremias for your Quick Answer I found the Reason : When you use the internal-destination=headDest3 twice (with the same ID [I do so for testing]) then the complete Bookmark is skipped ! Is this a bug ? Joern Karthaus Please check the log output from FOP. If the bookmark code cannot find an id in the document that you refer to using internal-destination then the bookmarks seem to be skipped at the moment. On 21.12.2005 12:10:59 Joern.Karthaus wrote: Hello List I'm just experimenting with fop-0.90alpha1 and the new Bookmark functionality FOP render these Code without errors : ?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; xsl:output indent=yes/ xsl:template match=/ fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; !--xsl:call-template name=Index/-- !-- Beschreibt, wie eine Seite auszusehen hat -- fo:layout-master-set fo:simple-page-master master-name=mainLayout page-width=297mm page-height=210mm margin-top=0.5cm margin-bottom=0.5cm margin-left=0.5cm margin-right=0.5cm fo:region-body margin-top=0.5cm margin-bottom=0.5cm/ fo:region-before extent=0.5cm/ fo:region-after extent=0.5cm/ /fo:simple-page-master !-- ## -- fo:page-sequence-master master-name=contents fo:repeatable-page-master-reference master-reference=mainLayout/ /fo:page-sequence-master /fo:layout-master-set fo:bookmark-tree fo:bookmark internal-destination=headDest3 fo:bookmark-titleBookmarks Example/fo:bookmark-title fo:bookmark internal-destination=headDest3 fo:bookmark-titleHello World/fo:bookmark-title /fo:bookmark fo:bookmark internal-destination=chapter2 fo:bookmark-titleParagraphs/fo:bookmark-title /fo:bookmark /fo:bookmark /fo:bookmark-tree !-- Inhalt von mainLayout -- fo:page-sequence master-reference=mainLayout initial-page-number=1 !-- Kopfzeile -- fo:static-content flow-name=xsl-region-before fo:block font-size=22 text-align=center background-color=greyKAMPF - Fehlteilliste V2/fo:block /fo:static-content !-- Hauptbereich -- fo:flow flow-name=xsl-region-body xsl:apply-templates select=//STUECKLISTE/ fo:block id=last-page/ /fo:flow /fo:page-sequence /fo:root /xsl:template ... But in the resulting PDF are no Bookmarks. Can somebody give me a example or tell whats wrong. Thanks : Joern Karthaus Jeremias Maerki Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
baseline-shift problem
Hi, is der any known issue using the basline-shift attribute in fop 20.0.5? Ofo:character character=2 baseline-shift=sub/ Doesn't show any effect on the 2. It's shown in the PDF like O2. Can anybody figure out what went wrong here? I'm looking forward to hearing from you, Christian Loock ___ Phone +49 (0) 28 21 / 9 78 56-16 Fax +49 (0) 28 21 / 9 78 56-77 E-Mail [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Headquarter db-central gmbh Dienstleistungszentrum am Weißen Tor Gocher Landstrasse 2 D-47551 Bedburg-Hau Subsidiary db-central gmbh Film- und Medienzentrum Königsallee 43 D-71638 Ludwigsburg (Stuttgart) __ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: baseline-shift problem
Under 0.20.5 you need to use vertical-align=sub instead. And you need to use fo:inline instead of fo:character for vertical-align to work. Of course, none of these restrictions apply to FOP 0.90alpha1. ;-) On 21.12.2005 16:15:03 Christian Loock wrote: Hi, is der any known issue using the basline-shift attribute in fop 20.0.5? Ofo:character character=2 baseline-shift=sub/ Doesn't show any effect on the 2. It's shown in the PDF like O2. Can anybody figure out what went wrong here? Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: baseline-shift problem
Ah ok. But what if the letter is pushed down to far? Afaik baseline-shift allows values like -120% wich allow you to specify how far the text ist shifted. How can i do so with vertical-align? Christian Loock -Original Message- From: Jeremias Maerki [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 21, 2005 4:38 PM To: fop-users@xmlgraphics.apache.org Subject: Re: baseline-shift problem Under 0.20.5 you need to use vertical-align=sub instead. And you need to use fo:inline instead of fo:character for vertical-align to work. Of course, none of these restrictions apply to FOP 0.90alpha1. ;-) On 21.12.2005 16:15:03 Christian Loock wrote: Hi, is der any known issue using the basline-shift attribute in fop 20.0.5? Ofo:character character=2 baseline-shift=sub/ Doesn't show any effect on the 2. It's shown in the PDF like O2. Can anybody figure out what went wrong here? Jeremias Maerki - 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: baseline-shift problem
You can't with 0.20.5. You'll have to upgrade to FOP 0.90alpha1 to have better control over baseline displacement. On 21.12.2005 16:55:06 Christian Loock wrote: Ah ok. But what if the letter is pushed down to far? Afaik baseline-shift allows values like -120% wich allow you to specify how far the text ist shifted. How can i do so with vertical-align? Christian Loock -Original Message- From: Jeremias Maerki [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 21, 2005 4:38 PM To: fop-users@xmlgraphics.apache.org Subject: Re: baseline-shift problem Under 0.20.5 you need to use vertical-align=sub instead. And you need to use fo:inline instead of fo:character for vertical-align to work. Of course, none of these restrictions apply to FOP 0.90alpha1. ;-) On 21.12.2005 16:15:03 Christian Loock wrote: Hi, is der any known issue using the basline-shift attribute in fop 20.0.5? Ofo:character character=2 baseline-shift=sub/ Doesn't show any effect on the 2. It's shown in the PDF like O2. Can anybody figure out what went wrong here? Jeremias Maerki - 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] Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Either keeps in table rows in 0.20.5 or non-collapsing paragraphs in .90alpha
Hi, all, I'm creating reports for a new client. The reports consist entirely of tables (not blind tables used for layout but actual tabular content). In 0.20.5, I can't get keep-together or keep-with-next to work on a table row. I get page breaks within table-cells. In .90alpha, I don't get page breaks in table-cells, but it causes another problem. .90alpha collapses (renders with 0 height, it seems) blocks that contain just a non-breaking space (that is, character # 1 6 0 ; with extra spaces). I need those blocks to be full height, as I am using them to position things within table cells. Collapsing fo:block/ would be fine (I'm using empty blocks for page breaks between tables, in fact, and it's good there), but it seems to me that blocks with content (even just a space) shouldn't be collapsed. So, I either need to know how to get page breaks to not occur within table cells (that is, only at the rows between cells) in 0.20.5 or I need to know how to prevent blocks that contain spaces from collapsing in .90alpha. The 0.20.5 solution would be preferred, but I think I can talk my client into moving to .90alpha if it fixes the page break problem. Thanks Jay Bryant Bryant Communication Services - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Either keeps in table rows in 0.20.5 or non-collapsing paragraphs in .90alpha - followup
Hi, all, I'm creating reports for a new client. The reports consist entirely of tables (not blind tables used for layout but actual tabular content). In 0.20.5, I can't get keep-together or keep-with-next to work on a table row. I get page breaks within table-cells. In .90alpha, I don't get page breaks in table-cells, but it causes another problem. .90alpha collapses (renders with 0 height, it seems) blocks that contain just a non-breaking space (that is, character # 1 6 0 ; with extra spaces). I need those blocks to be full height, as I am using them to position things within table cells. Collapsing fo:block/ would be fine (I'm using empty blocks for page breaks between tables, in fact, and it's good there), but it seems to me that blocks with content (even just a space) shouldn't be collapsed. So, I either need to know how to get page breaks to not occur within table cells (that is, only at the rows between cells) in 0.20.5 or I need to know how to prevent blocks that contain spaces from collapsing in .90alpha. The 0.20.5 solution would be preferred, but I think I can talk my client into moving to .90alpha if it fixes the page break problem. Thanks I used block-containers with height attribute values wrapped around empty blocks to make my spacer blocks, so I've gotten the .90alpha solution to work. Combined with the -q option to shut off all the to-do messages, it'll work. I'd still like to know how to prevent page breaks within table cells in 0.20.5 in case my client (or some future client) resists going to .90alpha. Thanks some more. Jay Bryant Bryant Communication Services - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Either keeps in table rows in 0.20.5 or non-collapsing paragraphs in .90alpha
I'm not so much into 0.20.5 these days, so without a demo file to start from (to save time) I can only try to help you with 0.90. We do have some problems with collapsing nbsps as you might have seen on this list lately. What I think could work for you is to specify block-progression-dimension.minimum=1em on a table-row. In that case, a row cannot collapse even if you only use a minimum fo:block/ inside the table-cells. Did I understand you correctly that keep-together on the table-rows works for you as expected in 0.90? HTH BTW, we're planning on releasing a beta version in the next few days, hopefully this week since I want to take a week off. On 21.12.2005 21:52:57 Jay Bryant wrote: Hi, all, I'm creating reports for a new client. The reports consist entirely of tables (not blind tables used for layout but actual tabular content). In 0.20.5, I can't get keep-together or keep-with-next to work on a table row. I get page breaks within table-cells. In .90alpha, I don't get page breaks in table-cells, but it causes another problem. .90alpha collapses (renders with 0 height, it seems) blocks that contain just a non-breaking space (that is, character # 1 6 0 ; with extra spaces). I need those blocks to be full height, as I am using them to position things within table cells. Collapsing fo:block/ would be fine (I'm using empty blocks for page breaks between tables, in fact, and it's good there), but it seems to me that blocks with content (even just a space) shouldn't be collapsed. So, I either need to know how to get page breaks to not occur within table cells (that is, only at the rows between cells) in 0.20.5 or I need to know how to prevent blocks that contain spaces from collapsing in .90alpha. The 0.20.5 solution would be preferred, but I think I can talk my client into moving to .90alpha if it fixes the page break problem. Thanks Jay Bryant Bryant Communication Services Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Either keeps in table rows in 0.20.5 or non-collapsing paragraphs in .90alpha - followup
On 21.12.2005 22:16:46 Jay Bryant wrote: Hi, all, I'm creating reports for a new client. The reports consist entirely of tables (not blind tables used for layout but actual tabular content). In 0.20.5, I can't get keep-together or keep-with-next to work on a table row. I get page breaks within table-cells. In .90alpha, I don't get page breaks in table-cells, but it causes another problem. .90alpha collapses (renders with 0 height, it seems) blocks that contain just a non-breaking space (that is, character # 1 6 0 ; with extra spaces). I need those blocks to be full height, as I am using them to position things within table cells. Collapsing fo:block/ would be fine (I'm using empty blocks for page breaks between tables, in fact, and it's good there), but it seems to me that blocks with content (even just a space) shouldn't be collapsed. So, I either need to know how to get page breaks to not occur within table cells (that is, only at the rows between cells) in 0.20.5 or I need to know how to prevent blocks that contain spaces from collapsing in .90alpha. The 0.20.5 solution would be preferred, but I think I can talk my client into moving to .90alpha if it fixes the page break problem. Thanks I used block-containers with height attribute values wrapped around empty blocks to make my spacer blocks, so I've gotten the .90alpha solution to work. Combined with the -q option to shut off all the to-do messages, it'll work. That seems like a hack. Please try my suggestions I just sent. I'd still like to know how to prevent page breaks within table cells in 0.20.5 in case my client (or some future client) resists going to .90alpha. keep-together is supposed to work if specified on a table-row. Does that mean that this doesn't work in your case. If you can post a small example, I can have a look. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
fop-0.90.alpha1: SVG graphic outside bounds of table cell when using PDF
Hello, I'm using fop-0.90.alpha1. The following is a sample XSL-FO document which when converted to PDF results in the SVG graphic on the last row of the table being outside the bounds of the table cells. Notice the other identical graphics which correctly render inside the bounds of the table cells. Feel free to contact me for further details if needed. I can provide the PDF being generated if requested. Thanks, Ryan - ?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=.5in margin-left=1.0in margin-bottom=.17in margin-top=.17in master-name=standard fo:region-body margin-bottom=.5in margin-top=1.25in / fo:region-before extent=1.25in / fo:region-after extent=1.0in / fo:region-start / fo:region-end / /fo:simple-page-master /fo:layout-master-set fo:page-sequence font-size=11pt font-family=Helvetica master-reference=standard fo:flow flow-name=xsl-region-body fo:table border-style=solid border-width=.25pt border-collapse=separate width=100% table-layout=fixed fo:table-column column-width=5% column-number=1 / fo:table-column column-width=5% column-number=2 / fo:table-column column-width=40% column-number=3 / fo:table-column column-width=50% column-number=4 / fo:table-body fo:table-row fo:table-cell border-style=solid border-width=.25pt display-align=before text-align=left number-columns-spanned=1 number-rows-spanned=1 padding=2pt fo:block2./fo:block /fo:table-cell fo:table-cell border-style=solid border-width=.25pt display-align=before text-align=left number-columns-spanned=2 number-rows-spanned=1 padding=2pt fo:block Blah blah. Blah blah. Blah blah? /fo:block /fo:table-cell fo:table-cell border-style=solid border-width=.25pt display-align=before text-align=left number-columns-spanned=1 number-rows-spanned=1 padding=2pt fo:block fo:instream-foreign-object height=11pt width=11pt svg:svg xmlns:svg=http://www.w3.org/2000/svg; xml:space=preserve height=22 svg:g style=fill:none; stroke:black; stroke-width:2 transform=scale(.5) svg:rect stroke-width=1 height=20 width=20 fill=black y=2 x=0 / svg:rect stroke-width=1 height=20 width=20 fill=white y=0 x=2 / /svg:g /svg:svg /fo:instream-foreign-object Yes fo:instream-foreign-object height=11pt width=11pt svg:svg xmlns:svg=http://www.w3.org/2000/svg; xml:space=preserve height=22 svg:g style=fill:none; stroke:black; stroke-width:2 transform=scale(.5) svg:rect stroke-width=1 height=20 width=20 fill=black y=2 x=0 / svg:rect stroke-width=1 height=20 width=20 fill=white y=0 x=2 / /svg:g /svg:svg /fo:instream-foreign-object
Trying to use TTFReader
Hi. I was trying to use the TTFReader to render a TTF font to a metric file. I used the command provided in the documentary (Win XP, Java1.5.0, FOP 0.20 and 0.90, command: java -cp build\fop.jar;lib\avalon-framework.jar;lib\xml-apis.jar; lib\xercesImpl.jar;lib\xalan.jar org.apache.fop.fonts.apps.TTFReader [options] C:\myfonts\cmr10.ttf ttfcm.xml ) and changed the filenames to the ones of my actual FOP files. But anytime I try to convert a font I get this error message: Exception in thread main java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory at org.apache.fop.fonts.apps.TTFReader.main(TTFReader.java:155) I played around a bit with the option flag, but that didn't change anything. Can anybody tell me, what's my mistake? Best Regards Manuel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: fop-0.90.alpha1: SVG graphic outside bounds of table cell when using PDF
Ryan, you should work with a viewBox attribute on the svg root element. Otherwise, the simple numbers for widths are interpreted as pixels at 72dpi which causes the SVG to appear with a fixed width. Furthermore, it is a good idea to specify the size of the SVG itself as a length (pt, for example). A very simple example: svg width=11pt height=11pt viewBox=0 0 20 20 g style=fill:red; stroke:#00 rect x=0 y=0 width=15 height=15/ rect x=5 y=5 width=15 height=15/ /g /svg Furthermore, if you want the SVG to be fit into the box you define using instream-foreign-object you should specify content-width=scale-to-fit. Otherwise the SVG is simply matched into the upper left corner of the i-f-o's box at the default size. I hope that helps. On 21.12.2005 22:31:02 Ryan Gustafson wrote: Hello, I'm using fop-0.90.alpha1. The following is a sample XSL-FO document which when converted to PDF results in the SVG graphic on the last row of the table being outside the bounds of the table cells. Notice the other identical graphics which correctly render inside the bounds of the table cells. Feel free to contact me for further details if needed. I can provide the PDF being generated if requested. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Trying to use TTFReader
Our fault. We missed a little detail on the page that documents fonts for 0.90. You need to add an entry for lib\commons-logging-1.0.4.jar (and lib\commons-io-1.1.jar) on the command-line because that's where org/apache/commons/logging/LogFactory is found. The following works for me on JDK 1.4 and 1.5: java -cp build\fop.jar;lib\avalon-framework-4.2.0.jar;lib\commons-logging-1.0.4.jar;lib\commons-io-1.1.jar org.apache.fop.fonts.apps.TTFReader FUTURAB.TTF futurab.xml xml-apis.jar, xercesImpl.jar and xalan.jar are only necessary on JDK 1.3.x. I hope that helps. I'll update the documentation. On 21.12.2005 22:45:44 Manuel Strehl wrote: Hi. I was trying to use the TTFReader to render a TTF font to a metric file. I used the command provided in the documentary (Win XP, Java1.5.0, FOP 0.20 and 0.90, command: java -cp build\fop.jar;lib\avalon-framework.jar;lib\xml-apis.jar; lib\xercesImpl.jar;lib\xalan.jar org.apache.fop.fonts.apps.TTFReader [options] C:\myfonts\cmr10.ttf ttfcm.xml ) and changed the filenames to the ones of my actual FOP files. But anytime I try to convert a font I get this error message: Exception in thread main java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory at org.apache.fop.fonts.apps.TTFReader.main(TTFReader.java:155) I played around a bit with the option flag, but that didn't change anything. Can anybody tell me, what's my mistake? Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Trying to use TTFReader
Manuel Strehl wrote: I was trying to use the TTFReader to render a TTF font to a metric file. I used the command provided in the documentary (Win XP, Java1.5.0, FOP 0.20 and 0.90, command: java -cp build\fop.jar;lib\avalon-framework.jar;lib\xml-apis.jar; lib\xercesImpl.jar;lib\xalan.jar org.apache.fop.fonts.apps.TTFReader [options] C:\myfonts\cmr10.ttf ttfcm.xml It seems the command line is missing a class path entry for the commons logging jar. You should find the jar in the lib directory. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Either keeps in table rows in 0.20.5 or non-collapsing paragraphs in .90alpha - followup
Hi, Jeremias, I used block-containers with height attribute values wrapped around empty blocks to make my spacer blocks, so I've gotten the .90alpha solution to work. Combined with the -q option to shut off all the to-do messages, it'll work. That seems like a hack. Please try my suggestions I just sent. It feels like a hack, too. I'll try your ideas. I'd still like to know how to prevent page breaks within table cells in 0.20.5 in case my client (or some future client) resists going to .90alpha. keep-together is supposed to work if specified on a table-row. Does that mean that this doesn't work in your case. If you can post a small example, I can have a look. Well, while I was preparing a sample that would show the problem, I got keep-together=always to work the way it should. I'm not sure what changed, so I'll let the matter drop, as I don't have time to pursue much testing at present. Thanks. J - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Either keeps in table rows in 0.20.5 or non-collapsing paragraphs in .90alpha
What I think could work for you is to specify block-progression-dimension.minimum=1em on a table-row. In that case, a row cannot collapse even if you only use a minimum fo:block/ inside the table-cells. That didn't work with 0.90. Here's a snippet from what I tested: fo:table-row block-progression-dimension.minimum=1em keep-together.within-page=always fo:table-cell border-width=1pt border-style=solid border-color=black fo:block xsl:use-attribute-sets=headerleftxsl:value-of select=@name//fo:block fo:block xsl:use-attribute-sets=headerleftxsl:value-of select=@city//fo:block fo:block xsl:use-attribute-sets=headerleftxsl:value-of select=@address//fo:block /fo:table-cell fo:table-cell border-width=1pt border-style=solid border-color=black fo:block/ fo:block/ fo:block/ fo:block/ fo:block xsl:use-attribute-sets=headercenterxsl:value-of select=@id//fo:block /fo:table-cell 0.90 collapses those empty blocks. Jay Bryant Bryant Communication Services - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
when apache FOP will full support font-family lists and font-selection-strategy ?
hi , thanks fop developers. :) i am using fop to translate xml to fo and then to pdf. :) I want to mixing chinese and english font, when print/render english use english font, and when print/render chinese character use chinese font. :) but I don't know how to do that in the current fop version (0.20.5). can you give me some advice ? thanks. -- zouguangxian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: fop-0.90.alpha1: SVG graphic outside bounds of table cell when using PDF
Jeremias, Thank you, I don't know why those things would actually make a difference, but they do. The following works as a great checkbox, and it positions properly (it's not way off on the left margin of the page in neverneverland): fo:instream-foreign-object width=1em height=1em content-width=scale-to-fit svg:svg xmlns:svg=http://www.w3.org/2000/svg; width=1em height=1em viewBox=0 0 22 22 svg:g style=fill:none; stroke:black; stroke-width:2 svg:rect x=0 y=2 fill=black width=20 height=20 stroke-width=1/ svg:rect x=2 y=0 fill=white width=20 height=20 stroke-width=1/ /svg:g /svg:svg /fo:instream-foreign-object I'm evaluating FOP as an approach for generating paper versions of our online forms, and the fop-0.90.alpha1 release has been working great for me so far. Keep up the good work, and I'll be sure to report any issues I encounter. Thanks, Ryan Jeremias Maerki [EMAIL PROTECTED] 12/21/05 3:53 PM Ryan, you should work with a viewBox attribute on the svg root element. Otherwise, the simple numbers for widths are interpreted as pixels at 72dpi which causes the SVG to appear with a fixed width. Furthermore, it is a good idea to specify the size of the SVG itself as a length (pt, for example). A very simple example: svg width=11pt height=11pt viewBox=0 0 20 20 g style=fill:red; stroke:#00 rect x=0 y=0 width=15 height=15/ rect x=5 y=5 width=15 height=15/ /g /svg Furthermore, if you want the SVG to be fit into the box you define using instream-foreign-object you should specify content-width=scale-to-fit. Otherwise the SVG is simply matched into the upper left corner of the i-f-o's box at the default size. I hope that helps. On 21.12.2005 22:31:02 Ryan Gustafson wrote: Hello, I'm using fop-0.90.alpha1. The following is a sample XSL-FO document which when converted to PDF results in the SVG graphic on the last row of the table being outside the bounds of the table cells. Notice the other identical graphics which correctly render inside the bounds of the table cells. Feel free to contact me for further details if needed. I can provide the PDF being generated if requested. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: when apache FOP will full support font-family lists and font-selection-strategy ?
Both properties are not fully implemented even in the latest release FOP 0.90alpha1. Either you have to place either the Chinese or the English text in fo:inlines and specify the different fonts on the inlines or if you have a TrueType font that supports both Chinese and English characters you can have them mixed. The other option is to help us implement font-selection-strategy and font-family lists. On 21.12.2005 14:24:05 Guangxian Zou wrote: hi , thanks fop developers. :) i am using fop to translate xml to fo and then to pdf. :) I want to mixing chinese and english font, when print/render english use english font, and when print/render chinese character use chinese font. :) but I don't know how to do that in the current fop version (0.20.5). can you give me some advice ? thanks. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Either keeps in table rows in 0.20.5 or non-collapsing paragraphs in .90alpha
Ah, I see you have multiple lines in a table-cell. In that case, just specify 5em (the number of lines you have in em) on block-progression-dimension.minimum. On 21.12.2005 23:54:52 Jay Bryant wrote: What I think could work for you is to specify block-progression-dimension.minimum=1em on a table-row. In that case, a row cannot collapse even if you only use a minimum fo:block/ inside the table-cells. That didn't work with 0.90. Here's a snippet from what I tested: fo:table-row block-progression-dimension.minimum=1em keep-together.within-page=always fo:table-cell border-width=1pt border-style=solid border-color=black fo:block xsl:use-attribute-sets=headerleftxsl:value-of select=@name//fo:block fo:block xsl:use-attribute-sets=headerleftxsl:value-of select=@city//fo:block fo:block xsl:use-attribute-sets=headerleftxsl:value-of select=@address//fo:block /fo:table-cell fo:table-cell border-width=1pt border-style=solid border-color=black fo:block/ fo:block/ fo:block/ fo:block/ fo:block xsl:use-attribute-sets=headercenterxsl:value-of select=@id//fo:block /fo:table-cell 0.90 collapses those empty blocks. Jay Bryant Bryant Communication Services Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: fop-0.90.alpha1: SVG graphic outside bounds of table cell when using PDF
Ryan, the viewBox attribute changes the meaning of coordinates without a length unit (pt, mm etc.). If no viewBox is specified the length unit is interpreted as pixels with the resolution in use by the user agent (user agent here = FOP with 72 dpi). Together with explicit length units on width and height attributes you create a well defined SVG image with an explicitely defined size. Otherwise, the SVG image does not have an explicit intrinsic size, only an implicit one which can vary between user agents (viewer software). On 21.12.2005 23:49:07 Ryan Gustafson wrote: Jeremias, Thank you, I don't know why those things would actually make a difference, but they do. The following works as a great checkbox, and it positions properly (it's not way off on the left margin of the page in neverneverland): fo:instream-foreign-object width=1em height=1em content-width=scale-to-fit svg:svg xmlns:svg=http://www.w3.org/2000/svg; width=1em height=1em viewBox=0 0 22 22 svg:g style=fill:none; stroke:black; stroke-width:2 svg:rect x=0 y=2 fill=black width=20 height=20 stroke-width=1/ svg:rect x=2 y=0 fill=white width=20 height=20 stroke-width=1/ /svg:g /svg:svg /fo:instream-foreign-object I'm evaluating FOP as an approach for generating paper versions of our online forms, and the fop-0.90.alpha1 release has been working great for me so far. Keep up the good work, and I'll be sure to report any issues I encounter. Thanks, Ryan Jeremias Maerki [EMAIL PROTECTED] 12/21/05 3:53 PM Ryan, you should work with a viewBox attribute on the svg root element. Otherwise, the simple numbers for widths are interpreted as pixels at 72dpi which causes the SVG to appear with a fixed width. Furthermore, it is a good idea to specify the size of the SVG itself as a length (pt, for example). A very simple example: svg width=11pt height=11pt viewBox=0 0 20 20 g style=fill:red; stroke:#00 rect x=0 y=0 width=15 height=15/ rect x=5 y=5 width=15 height=15/ /g /svg Furthermore, if you want the SVG to be fit into the box you define using instream-foreign-object you should specify content-width=scale-to-fit. Otherwise the SVG is simply matched into the upper left corner of the i-f-o's box at the default size. I hope that helps. On 21.12.2005 22:31:02 Ryan Gustafson wrote: Hello, I'm using fop-0.90.alpha1. The following is a sample XSL-FO document which when converted to PDF results in the SVG graphic on the last row of the table being outside the bounds of the table cells. Notice the other identical graphics which correctly render inside the bounds of the table cells. Feel free to contact me for further details if needed. I can provide the PDF being generated if requested. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
