RE: Table-question
Hi, Please, in the future, can you post a XSL-FO file rather than PDF? Check if your fo:table width is given in physical units, replace with percents. (width=100%) should do the trick. Pascal -Message d'origine- De : Thomas Zastrow [mailto:[EMAIL PROTECTED] Envoyé : jeudi 1 février 2007 22:31 À : fop-users@xmlgraphics.apache.org Objet : Table-question Hello, I'm new to the FOP and I think it is a realy great tool! If I ask stupid questions, please be patient ;-) I played around with the examples in the FOP-distribution. But I have one problem: If I set the style of a page to two-columns (column-count=2) and there is a table on that page which is bigger than one of the columns, the text of the second column flows into the table and not around it. I put my example online: http://www.thomas-zastrow.de/temp/normal.pdf The PDF is 29 kb, the table I mean is on page 2. It would be nice if anyone can give me a tip what I have to do that the text flows in both columns around the table? Thank you very much! Best regards, Tom - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Embedding font triplets w/ a single TTF file
On 31.01.2007 11:32:09 Chris Bowditch wrote: Jeremias Maerki wrote: Just for those technically interested how this effect would be done in PDF, here's an example: snip what=very useful PDF snippet/ I think the key value here is the use of 2 Tr which gives each glyph a border of a certain width which makes the font appear bold. So if anyone wants to implement something like that, here's the template. :-) Very interesting. Thanks for the tip. The main drawback of course being that it only works for PDF :( Well, similar effects can be achieved in PostScript, Java2D and PCL. Don't know about AFP, though. But this has to be implemented separately for every renderer. snip/ Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Crimson +FOP + Tomcat
Hi all... I'va a problem with FOP in a web application environment with Tomcat If I run only with jdk (1.4.2), fop works with org.apache.crimson.jaxp.SAXParserFactoryImpl as SAXParserFactory and works well but when i call this same class from a web app in tomcat, it throws this exception org.xml.sax.SAXParseException Exception: can't declare any more prefixes in this context. As i can see, it isn't a XSL problem as i can run this same class without problems in jdk... And if i remove Xerces from TOMCAT_HOME/common/endorsed it works well and this exception desappears... How can i fix it? anybody knows? How can i set a different SAXParserFactory to Driver (with FOP 0.20)?? I've tried to do this System.setProperty(javax.xml.parsers.SAXParserFactory, org.apache.xerces.jaxp.SAXParserFactoryImpl); but it doesn't work, and driver.setXMLReader(new FOInputHandler(new File(Configuration.getStringValue(baseDir))).getParser()); doesn't work... Thanks in advance - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Table-question
On Friday 02 February 2007 09:25, Pascal Sancho wrote: Hi, Please, in the future, can you post a XSL-FO file rather than PDF? Sorry! Check if your fo:table width is given in physical units, replace with percents. (width=100%) should do the trick. Thank you very much - but it seems not to work ... I'll post the FO-code here in this mail, is this OK? Or should I put the file on a webserver? The problem is with the table under the comment Here is the problematic table: --- ?xml version=1.0 encoding=UTF-8? fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; xmlns:svg=http://www.w3.org/2000/svg; fo:layout-master-set fo:simple-page-master master-name=TitelSeite page-width=21cm page-height=29.7cm margin-top=1cm margin-bottom=1cm margin-left=2.5cm margin-right=2.5cm fo:region-body margin-top=1cm margin-bottom=3cm column-count=2 / fo:region-before extent=3cm/ fo:region-after extent=1.5cm/ /fo:simple-page-master fo:simple-page-master master-name=content page-width=21cm page-height=29.7cm margin-top=1cm margin-bottom=1cm margin-left=2.5cm margin-right=2.5cm fo:region-body margin-top=1cm margin-bottom=3cm column-count=2 / fo:region-before extent=3cm/ fo:region-after extent=1.5cm/ /fo:simple-page-master fo:page-sequence-master master-name=SeitenReihenfolge fo:repeatable-page-master-alternatives fo:conditional-page-master-reference master-reference=TitelSeite page-position=first / fo:conditional-page-master-reference master-reference=content page-position=rest / !-- recommended fallback procedure -- fo:conditional-page-master-reference master-reference=content / /fo:repeatable-page-master-alternatives /fo:page-sequence-master /fo:layout-master-set fo:page-sequence master-reference=SeitenReihenfolge fo:static-content flow-name=xsl-region-after fo:block text-align-last=center font-size=10pt ~ fo:page-number/ ~ /fo:block /fo:static-content fo:flow flow-name=xsl-region-body !-- Header -- fo:block font-size=18pt font-family=sans-serif line-height=24pt space-after.optimum=15pt background-color=green color=white text-align=center padding-top=3pt font-variant=small-caps Toms FOP-Test /fo:block !-- Titel -- fo:block font-size=16pt font-family=sans-serif line-height=12pt space-after=10pt space-before=10pt text-indent=5pt text-align=left padding-top=10pt background-color=#beeeb4 Einleitung fo:leader leader-length=10cm leader-pattern=rule alignment-baseline=middle rule-thickness=0.5pt color=green/ /fo:block fo:external-graphic src=url(loeweKlein.jpg) margin-bottom=1cm / fo:block font-size=12pt font-family=sans-serif line-height=15pt space-after.optimum=3pt text-align=justify Weit hinten, hinter den Wortbergen, fern der Länder Vokalien und Konsonantien leben die Blindtexte. Abgeschieden wohnen Sie in Buchstabhausen an der Küste des Semantik, eines großen Sprachozeans. Ein kleines Bächlein namens Duden fließt durch ihren Ort und versorgt sie mit den nötigen Regelialien. Es ist ein paradiesmatisches Land, in dem einem gebratene Satzteile in den Mund fliegen. Nicht einmal von der allmächtigen Interpunktion werden die Blindtexte beherrscht - ein geradezu unorthographisches Leben.Als es die ersten Hügel des Kursivgebirges erklommen hatte, warf es einen letzten Blick zurück auf die Skyline seiner Heimatstadt Buchstabhausen, die Headline von Alphabetdorf und die Subline seiner eigenen Straße, der Zeilengasse. Wehmütig lief ihm eine rethorische Frage über die Wange, dann setzte es seinen Weg fort. Doch alles Gutzureden konnte es nicht überzeugen und so dauerte es nicht lange, bis ihm ein paar heimtückische Werbetexter auflauerten, es mit Longe und Parole betrunken machten und es dann in ihre Agentur schleppten, wo sie es für ihre Projekte wieder und wieder mißbrauchten. Und wenn es nicht umgeschrieben wurde, dann benutzen Sie es immernoch. Eines Tages aber beschloß eine kleine Zeile Blindtext,
Re: Table-question
In your XSL-FO, I see 3 things that should be corrected: Thank you very much, I corrected the errors ;-) And now I got tit also with the table: I had to put the table into an own block and then setting this block to span=all. Thanx for your help! Best, Tom - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Exception in thread main java.lang.ExceptionInInitializerError
Hello, When I'm trying to use an svg image als an graphic in FOP im getting following error: [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [INFO] FOP @version@ [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [INFO] building formatting object tree [INFO] setting up fonts [INFO] [1] [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser Exception in thread main java.lang.ExceptionInInitializerError at org.apache.batik.ext.awt.image.spi.ImageTagRegistry.getRegistry(ImageTag Registry.java:273) at org.apache.batik.bridge.SVGImageElementBridge.createRasterImageNode(SVGI mageElementBridge.java:280) at org.apache.batik.bridge.SVGImageElementBridge.createGraphicsNode(SVGImag eElementBridge.java:138) at org.apache.batik.bridge.GVTBuilder.buildGraphicsNode(GVTBuilder.java:182 ) at org.apache.batik.bridge.GVTBuilder.buildComposite(GVTBuilder.java:148) at org.apache.batik.bridge.GVTBuilder.build(GVTBuilder.java:76) at org.apache.fop.render.pdf.PDFRenderer.renderSVGDocument(PDFRenderer.java :590) at org.apache.fop.render.pdf.PDFRenderer.drawImageScaled(PDFRenderer.java:3 80) at org.apache.fop.render.AbstractRenderer.renderImageArea(AbstractRenderer. java:326) at org.apache.fop.image.ImageArea.render(ImageArea.java:107) at org.apache.fop.render.AbstractRenderer.renderAreaContainer(AbstractRende rer.java:451) at org.apache.fop.layout.ColumnArea.render(ColumnArea.java:71) at org.apache.fop.render.AbstractRenderer.renderSpanArea(AbstractRenderer.j ava:100) at org.apache.fop.layout.SpanArea.render(SpanArea.java:94) at org.apache.fop.render.AbstractRenderer.renderBodyAreaContainer(AbstractR enderer.java:368) at org.apache.fop.layout.BodyAreaContainer.render(BodyAreaContainer.java:13 7) at org.apache.fop.render.AbstractRenderer.renderRegions(AbstractRenderer.ja va:529) at org.apache.fop.render.pdf.PDFRenderer.renderPage(PDFRenderer.java:904) at org.apache.fop.render.pdf.PDFRenderer.render(PDFRenderer.java:880) at org.apache.fop.apps.StreamRenderer.queuePage(StreamRenderer.java:302) at org.apache.fop.layout.AreaTree.addPage(AreaTree.java:108) at org.apache.fop.fo.pagination.PageSequence.makePage(PageSequence.java:415 ) at org.apache.fop.fo.pagination.PageSequence.format(PageSequence.java:338) at org.apache.fop.apps.StreamRenderer.render(StreamRenderer.java:262) at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:223) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDis patcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unkno wn Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.fop.apps.Driver.render(Driver.java:498) at org.apache.fop.apps.CommandLineStarter.run(CommandLineStarter.java:106) at org.apache.fop.apps.Fop.main(Fop.java:62) Caused by: java.awt.HeadlessException at java.awt.GraphicsEnvironment.checkHeadless(GraphicsEnvironment.java:121) at java.awt.Label.(Label.java:133) at java.awt.Label.(Label.java:100) at org.apache.batik.ext.awt.image.spi.JDKRegistryEntry.(JDKRegistryEntry.ja va:102) ... 36 more Any Ideas whats wrong with that image? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
display-align=justify
When doing the pagination of a large block of text, with columns, the text is if the keepers/orfan/widows are defined acordingly, passed to the next column leaving some space behind in the previous page. The visual effect of the full pages isn't great, specially if you have for instance 3 columns per page. What happens is that the text seams to ondulate in the bottom (diferent kinds of white space in the 6 columns that will be in side by side). To solve this, the only thing that i see that is fast and easy would be to exist a justify property value for the display-align. But unfortunatly i dind't found it. The hard way would be to setup a container with diferent orientation (if that is possible) so that a simple text-align=justify would just justify other blocks vertically, will they contain text in other orientation (i'm not sure if i'm clear here). Any sugestions on how to archieve vertical justification of columns? Thanx in advance, Luis Ferro Teladigital.pt -- View this message in context: http://www.nabble.com/display-align%3D%22justify%22-tf3162421.html#a8772141 Sent from the FOP - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: display-align=justify
On Feb 2, 2007, at 19:07, Luis Ferro wrote: When doing the pagination of a large block of text, with columns, the text is if the keepers/orfan/widows are defined acordingly, passed to the next column leaving some space behind in the previous page. The visual effect of the full pages isn't great, specially if you have for instance 3 columns per page. What happens is that the text seams to ondulate in the bottom (diferent kinds of white space in the 6 columns that will be in side by side). IIRC, in the code there are references to a value of distribute being allowed for display-align (as an extension to the XSL Rec.) I haven't tried whether its implementation is complete, but maybe it will do the trick here...? HTH! Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: display-align=justify
Hi Luis, Luis Ferro a écrit : When doing the pagination of a large block of text, with columns, the text is if the keepers/orfan/widows are defined acordingly, passed to the next column leaving some space behind in the previous page. The visual effect of the full pages isn't great, specially if you have for instance 3 columns per page. What happens is that the text seams to ondulate in the bottom (diferent kinds of white space in the 6 columns that will be in side by side). Hehe, you won't find many layout programs which handle that! Fortunately you found FOP. To solve this, the only thing that i see that is fast and easy would be to exist a justify property value for the display-align. But unfortunatly i dind't found it. You don't need any special property, actually. Provided there is some elastic spaces, FOP will justify pages as it does for paragraphs. It's easy to add elastic spaces if your text contains section, sub-sections, etc. with titles, or if your layout design requires spaces between paragraphs. You just have to specify the space-before and space-after properties the right way, e.g.: fo:block space-before.minimum=6pt space-before.optimum=10pt space-before.maximum=14pt A paragraph... /fo:block The more you specify spaces between blocks of text, the easier it will be to justify pages. HTH, Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
