Justification and forced page breaks
Hello, when a page is broken automatically within a block the last line before the break is displayed justificated. But when a page break is forced within a block (with alignment settings set to justify) the last line is NOT displayed in justification (example file attached). This is disturbing. Is there a solution to this problem? Best regards, Matthias Brunner?xml version=1.0 encoding=ISO-8859-1? fo:root font-family=Times Roman font-size=12pt text-align=center xmlns:fo=http://www.w3.org/1999/XSL/Format; fo:layout-master-set fo:simple-page-master master-name=A4 page-width=210mm page-height=297mm margin-left=20mm margin-right=20mm margin-top=20mm margin-bottom=20mm fo:region-body/ /fo:simple-page-master /fo:layout-master-set fo:page-sequence master-reference=A4 fo:flow flow-name=xsl-region-body fo:block text-align=justify Wie der eco aus den Statistiken des DE-CIX ermittelte, stellt sich die Spitzenbelastung an Werktagen gegen 17 Uhr ein: Offenbar greifen viele Menschen kurz vor Büroschluss noch mal aufs Netz zu, beispielsweise um letzte E-Mails zu versenden oder sich mit Informationen für den Feierabend zu versorgen, meint der Verband. Der Tag mit dem niedrigsten Datendurchsatz in der fo:block break-before=page/ Woche ist der Samstag, während am Sonntag beim Datendurchsatz fast das Niveau eines normalen Freitags erreicht wird. /fo:block /fo:flow /fo:page-sequence /fo:root - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Manual line breaks
Hello! In a perfect XML world content is always separatable from presentation. Unfortunately, there are cases (at least in publishing) when this is simply not possible. For example, we need to provide the possibility to insert manual breaks into text (especially titles). Web research tells me that whitespace-treatment=preserve is a solution to this, yet unimplemented by FOP. The only workaround I have found so far is to sorround the position at which the line should be broken with non-break spaces. (Example: this#xA0;is#xA0;a#xA0;test !-- intended break position -- this#xA0;is#xA0;a#xA0;test.) Has anyone found a better solution to this? Cheers, Matthias Brunner - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: keep-together / blind tables
On Monday 03 March 2003 19:31, Peter Solberg wrote: Try the :fo:table-header There are other examples in the FOP package.. However, if you want running headers such as fo:retrieve-marker, you cannot use this... you must put the fo:retrieve-marker in xsl:region-before. This helps. Thanks! -Matthias Brunner - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
keep-together / blind tables
Hello, I know this is a FAQ but I did not find anything appropriate to my specific problem. I have paragraphs with a heading and, of course, I do not want the heading to be left alone on one page with the paragraphs being on the next one. ---excerpt--- xsl:template match=paragraphs fo:table table-layout=fixed width=100% fo:table-column column-width=proportional-column-width(1)/ fo:table-body fo:table-row keep-with-next=always fo:table-cell xsl:apply-templates select=heading/ /fo:table-cell /fo:table-row fo:table-row fo:table-cell xsl:apply-templates select=paragraph/ /fo:table-cell /fo:table-row /fo:table-body /fo:table /xsl:template ---excerpt--- keep-with-next works, the heading is never left alone. But even if a paragraph is half a page in size it is not seperated any more thus leaving ugly blank spots on the pages. (strange ASCII art example attached below :) What can I do to allow the separation of this paragraph? Thanks in advance, Matthias Example: p1 heading/ paragraph content content content /paragraph EMPTY EMPTY EMPTY EMPTY --- p2 heading/ paragraph content content content content content content content /paragraph INSTEAD OF: p1 heading/ paragraph content content content /paragraph heading/ paragraph content content- --- p2 content content content content content /paragraph EMPTY EMPTY EMPTY EMPTY - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: oprhan/window control, blind tables, keep-with-next etc
On Thursday 12 December 2002 08:26, Eddy De Clercq wrote: Hi, Thanks for the answer. Since there is no release date for implementing this, are there alternatives for FOP which handle widow/orphans already? Maybe you should check out XEP (http://www.renderx.com/FO2PDF.html). It comes with quite a hefty price tag, though. -- Matthias Brunner [EMAIL PROTECTED] PGP FP 7862 32B3 3B75 292A F76F 5042 8587 21AB 5B89 D501 Check out http://blumenstrasse.vol.at/~mb/gpgkey.asc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Strange irregularities in page breaking
On Wednesday 04 December 2002 15:12, Matthias Brunner wrote: On Wednesday 04 December 2002 13:12, Oleg Tkachenko wrote: Okay, next attempt: show us how are you running FOP from the command line and from an embedding. I have set up a test case (http://blumenstrasse.vol.at/~mb/foptest.zip, 15KB) with all necessary files included. Just copy all of them into a clean FOP 0.20.4 directory. Has anyone had a look it this? Oleg? Should I submit it as a bug? Best regards! -- Matthias Brunner [EMAIL PROTECTED] PGP FP 7862 32B3 3B75 292A F76F 5042 8587 21AB 5B89 D501 Check out http://blumenstrasse.vol.at/~mb/gpgkey.asc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Strange irregularities in page breaking
Hello, I have encountered the following problem: Input files and stylesheets are *exactly* the same. 73 pages are rendered regardless of whether calling from code/command line. (Tried with both PDF and XML renderer) But on page 63 and subsequent fop called from java code breaks differently, yet only a few words. Nevertheless this made me somewhat nervous and I tried the following: Driver d = new Driver(); org.apache.fop.configuration.Configuration.put(baseDir,FOP_HOME); org.apache.fop.apps.Options options = new Options(new File(FOP_HOME/config/userconfig.xml)); No effects. And fop -x ... did not even work! Why are these differences? Thanks in advance! -- Matthias Brunner [EMAIL PROTECTED] PGP FP 7862 32B3 3B75 292A F76F 5042 8587 21AB 5B89 D501 Check out http://blumenstrasse.vol.at/~mb/gpgkey.asc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Strange irregularities in page breaking
On Tuesday 03 December 2002 20:11, Oleg Tkachenko wrote: And fop -x ... did not even work! Did you mean -c? No, -x for dump all configuration settings. Why are these differences? Make sure you are embedding FOP in the same way you are running it from command line (I mean the same baseDir, userconfig.xml, JVM itself and jaxp/sax properties, classpath etc). Should be some difference as we don't believe in a magic. I copied fop.sh and changed only one line to start my class which I copied to FOP_HOME/lib. So I think every setting and the classpath will be the same. Yet output remains different. I don't understand. Software used: fop 0.20.4, JDK 1.4.1_01, Linux Best regards! -- Matthias Brunner [EMAIL PROTECTED] PGP FP 7862 32B3 3B75 292A F76F 5042 8587 21AB 5B89 D501 Check out http://blumenstrasse.vol.at/~mb/gpgkey.asc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Bug when integrating with SAX?
Source) at org.apache.fop.apps.StreamRenderer.render(Unknown Source) at org.apache.fop.fo.FOTreeBuilder.endElement(Unknown Source) at org.apache.xalan.transformer.ResultTreeHandler.endElement(ResultTreeHandler.java:307) at org.apache.xalan.templates.ElemLiteralResult.execute(ElemLiteralResult.java:684) at org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(TransformerImpl.java:2182) at org.apache.xalan.transformer.TransformerImpl.applyTemplateToNode(TransformerImpl.java:2008) at org.apache.xalan.transformer.TransformerImpl.transformNode(TransformerImpl.java:1171) at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:638) at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1088) at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1066) at Paginator.paginate(Paginator.java:38) at Paginator.main(Paginator.java:58) -- Matthias Brunner [EMAIL PROTECTED] PGP FP 7862 32B3 3B75 292A F76F 5042 8587 21AB 5B89 D501 Check out http://blumenstrasse.vol.at/~mb/gpgkey.asc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Bug when integrating with SAX?
On Friday 22 November 2002 14:26, Jeremias Maerki wrote: Mmm, probably, I think I remember some saying that Crimson doesn't work correctly. Namespace issues probably. Not sure. I tried it on the command line, with classpath und java endorsed dirs set. Does not help. BTW: Sorry for mailing 3 times. The mail server turned mad and I thought the first two lost. -- Matthias Brunner [EMAIL PROTECTED] PGP FP 7862 32B3 3B75 292A F76F 5042 8587 21AB 5B89 D501 Check out http://blumenstrasse.vol.at/~mb/gpgkey.asc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Bug when integrating with SAX?
Keiron, On Friday 22 November 2002 14:31, Keiron Liddle wrote: The fix of course would be to set the options on the renderer, you can create the XMLRenderer yourself and set the options on it, then set the renderer on the driver. thanks for this reply. I found the error. Will post a bug report in a minute. You have to do the following: XMLRenderer r = new XMLRenderer(); Hashtable opts = new Hashtable(); opts.put(fineDetail, new Boolean(true)); r.setOptions(opts); fopDriver.setOutputStream(System.out); fopDriver.setRenderer(r); stylesheet.newTransformer().transform( new DOMSource(source), new SAXResult(fopDriver.getContentHandler()) ); (2nd time today) Please only show the relevant part of the stack trace. IMHO it is sometimes very hard to determine which part of the stack trace is relevant, at least for non-developers. I think that error reports can hardly have too much context information, especially since these stacktraces are not really megabytes in size. Kind regards! -- Matthias Brunner [EMAIL PROTECTED] PGP FP 7862 32B3 3B75 292A F76F 5042 8587 21AB 5B89 D501 Check out http://blumenstrasse.vol.at/~mb/gpgkey.asc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to make an element disappear completely?
Hello, I am trying to get pagination information back into the source document. (see http://marc.theaimsgroup.com/?l=fop-userm=103227363003594w=2) It seems that there is no other opportunity than relying on an ugly hack. I intend to scan the Area Tree output in order to see where page breaks occur exactly. Every element in the source document has an id and the following lines will be at the beginning of every template: fo:inlinexsl:value-of select=concat(name(),':',@id)/ /fo:inline Of course, this influences the page breaks itself which it should not do. So I make it smaller: fo:inline font-size=0.01ptxsl:value-of select=concat(name(),':',@id)/ /fo:inline Now the text is gone but, unfortunately, the inline-element still consumes space? How do I make this element disappear completely (but still get it to be in the area tree)? Is there any other way to achieve this? Processing instructions? Kind regards! -- Matthias Brunner [EMAIL PROTECTED] PGP FP 7862 32B3 3B75 292A F76F 5042 8587 21AB 5B89 D501 Check out http://blumenstrasse.vol.at/~mb/gpgkey.asc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
