keep-with-next in blind table creates gaps on some pages
Hello, I use blind tables to prevent titles from being severed from the following block. But... If the block is too large to fit on remaining the page, it is ``sent'' to the next one. So I get stuff like this: |p.1 | |1st *title* | |1st block | |1st block | |1st block | |1st block | || || || ---Half of || the page || is empty || |p.2 | |2nd *title* | |2nd block | |2nd block | |2nd block | |2nd block | |2nd block | |2nd block | || || || || where 1st and 2d blocks are large paragraphs that *cannot* be divided into several subblocks. where I want: |p.1 | |1st *title* | |1st block | |1st block | |1st block | |1st block | || |2nd *title* | ---the 2nd block |2nd block | begins on |2nd block | the 1st page |2nd block | || |p.2 | |2nd block | |2nd block | |2nd block | || || || || || || || || If I remove the ``keep-with-next'' att., of course, I get lonely titles wandering at the bottom of some pages. Thanks in advance for the help -- ++ |Nicolas Mazziotta | |Aspirant au doctorat| |Linguistique française | |Département d'études romanes| |Université de Liège | ++ |04/3665382 | |[EMAIL PROTECTED] | ++ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: keep-with-next in blind table creates gaps on some pages
Chris Bowditch wrote: what you need to solve this problem is widow and orphan properties on fo:block. They control the minimum number of lines that are allowed to appear by themselves, either at the start of a new page or at the bottom of an existing page. Trouble is they are not implemented in FOP, and there is no work around. Yes, I've already tried this -and been disappointed. thank you -- ++ |Nicolas Mazziotta | |Aspirant au doctorat| |Linguistique française | |Département d'études romanes| |Université de Liège | ++ |04/3665382 | |[EMAIL PROTECTED] | ++ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: avoid widow/orphan
J.Pietschmann wrote: Nicolas Mazziotta wrote: I know the xslfo keep-w/-next attr. is not fully implemented yet, but does anyone have a hack or stg that would prevent users to manually add page breaks when needed? Did you look at http://xml.apache.org/fop/faq.html#keep-with J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Mea culpa. thank you -- ++ |Nicolas Mazziotta | |Aspirant au doctorat| |Linguistique française | |Département d'études romanes| |Université de Liège | ++ |04/3665382 | |[EMAIL PROTECTED] | ++ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
avoid widow/orphan
Hello, I cannot get the rid of this problem: when a title occurs just before page-break, it is severed from the text it's related with -which happens to be rendered on the next page... I know the xslfo keep-w/-next attr. is not fully implemented yet, but does anyone have a hack or stg that would prevent users to manually add page breaks when needed? thanks in advance for your help. -- ++ |Nicolas Mazziotta | |Aspirant au doctorat| |Linguistique française | |Département d'études romanes| |Université de Liège | ++ |04/3665382 | |[EMAIL PROTECTED] | ++ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
non rendered characters
Hello, [I've posted sample.zip with this message; it demonstrates my problem, ftp://www.ulg.ac.be/merci/sample.zip] I've noticed that text() of tags that occur at page-break as well as the characters that preceed in the same word-unit (surrounded by whitespaces) are not rendered at all in PDF and AWT view. Look at the beginning of page 15 in the pdf file: 'tensible' for 'extensible' [Efo:inlinex/fo:inlinetensible]; notice that even though the first 'e' is not surrounded by any tag, it is not rendered either. One more thing: if I process a 'simple.xml' file with occurrences like [Erx/rtensible], the same happens, even if I dont write any template for the 'r' element. Thank you all for your answers. N. Mazziotta attachment: sample.zip
RE : non rendered characters
I don't know if I have to report it in bugzilla (or if someone else will, since I don't know how to do it). To me it's a severe bug, because no philologue would use FOP knowing that some characters are not rendered... It is not possible to edit texts the words of which have been tokenized. Best regards. N. Mazziotta -Message d'origine- De : Keiron Liddle [mailto:[EMAIL PROTECTED] Envoyé : mercredi 17 avril 2002 14:43 À : [EMAIL PROTECTED] Objet : Re: non rendered characters This problem is a result of the way the line is built. It has pending areas that need to be added to form a word due to different text elements, this happens if you use inline or other xml elements. These areas are dropped at the end of the page. So yes this is a bug. On 2002.04.17 14:22 Nicolas Mazziotta wrote: Hello, [I've posted sample.zip with this message; it demonstrates my problem, ftp://www.ulg.ac.be/merci/sample.zip] I've noticed that text() of tags that occur at page-break as well as the characters that preceed in the same word-unit (surrounded by whitespaces) are not rendered at all in PDF and AWT view. Look at the beginning of page 15 in the pdf file: 'tensible' for 'extensible' [Efo:inlinex/fo:inlinetensible]; notice that even though the first 'e' is not surrounded by any tag, it is not rendered either. One more thing: if I process a 'simple.xml' file with occurrences like [Erx/rtensible], the same happens, even if I dont write any template for the 'r' element. Thank you all for your answers. N. Mazziotta
RE : problem with attribute: visibility
Go there: http://xml.apache.org/fop/implemented.html Visibility attribute is not implemented yet: this means FOP can't handle it yet. No version of FOP can so far (I think). N. Mazziotta -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Envoyé : mercredi 17 avril 2002 15:47 À : [EMAIL PROTECTED] Objet : problem with attribute: visibility Hi, I´m trying to use the visibility-attribute but it doens´t work. I´m using fop 0.20.01. and all I get is the following: Warning: property - visibility is not implemented yet. Has it something to do with the Fop version I´m using? What I actually want to do is to create a blank line (fo:table-row)... Can anybody help? Thanks in advance Markus
RE : Antwort: Re: Antwort: RE : problem with attribute: visibility
just fill cells with non-breakable spaces -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Envoyé : mercredi 17 avril 2002 16:36 À : [EMAIL PROTECTED] Objet : Antwort: Re: Antwort: RE : problem with attribute: visibility I´ve just tried it, but empty cells are ignored in the output pdf. What I actually want to do is to create a blank line (fo:table-row)... Couldn't you simply fill it with an empty cell that spans all columns.
RE : non-editable PDF
see 3.3 [prev in list] [next in list] [prev in thread] [next in thread] List: fop-dev Subject: Re: FAQ Answers please From: Joerg Pietschmann [EMAIL PROTECTED] Date: 2002-03-07 17:21:09 [Download message RAW] (Crossposted to both fop-dev and fop-user. fop-user subscribers, please post follow-ups to fop-dev) alex [EMAIL PROTECTED] wrote: Can anyone capture any important questions and answers which I should put into the FAQ? Well questions are easy, answers somewhat less: Here is my impression 1. FOP specific technical questions 1.1 Using FOP in a servlet. Apparently, the servlet example in the distribution is not sufficient, but still a frist answer. 1.2 Using FOP in a servlet with an XSLT transformation Many suboptimal answers are regulrly posted here and to the fop-user list. The canonical answers are, use XSLTInputHandler or TraxInputHandler if both XML and XSL are files, or a SAX event stream if some XML is generated on the fly or read from an network stream or such. Code can be copied from http://marc.theaimsgroup.com/?l=fop-devw=2r=1s=xsltinputhandlerq=b namely http://marc.theaimsgroup.com/?l=fop-devm=101232320408992w=2 and http://marc.theaimsgroup.com/?l=fop-devw=2r=1s=getContentHandlerq=b unfortunately, there are various neat snippets which would have to be combined in order to show all the possibilites. http://marc.theaimsgroup.com/?l=fop-devm=100583267306925w=2 http://marc.theaimsgroup.com/?l=fop-devm=100703832007931w=2 1.3 User supplied fonts While this is answered in the Docs, some expressive hints about what data are file names and what are file _URLs_ could be noted again. 1.4 Embedding fonts when run from a servlet The usual code how to get the settings from userconfig.xml, as for example seen at http://marc.theaimsgroup.com/?l=fop-devm=101421597727050w=2 This question needs to be indexed twice, obviously. 1.5 Complaints about: 1.5.1 files not found referenced in fo:external-graphics, user fonts etc. 1.5.2 MalformedURLException, especially URIs starting with (null) It should be explained o The file names are URIs. o Users should be encouraged to get familar with URI syntax (quote web ressources, at least the RFCs). o The correct syntax for file URIs is file:///some/path/file.ext (on localhost, the usual case). Emphasize the triple slash. o The resolution mechanism for relative URIs should be explained, especially the role of baseDir. o Note that XSL transformations and JAXP transformers have their own mechanism for resolving relative URIs, could be redirected to the XSLT FAQ http://www.dpawson.co.uk/xsl/xslfaq.html 1.6 Setting baseDir in userconfig.xml 1.7 Setting baseDir in a servlet environment Either via userconfig.xml or the Configuration, code at http://marc.theaimsgroup.com/?l=fop-devm=101354604124258w=2 1.8 New VFAQ: PNG images and other formats dont (no longer) work, Jimi library is missing Jimi is no longer in the distribution. Explain where to get it. 1.9 NoClassDefFound (Command line) Explain again how to set the CLASSPATH. Explain the usage of the batch files and that they have to be started in the correct directory. 1.10 NoClassDefFound (Servlet environment), getting FOP working for various servlet engines. Explain classpath issues, how jar files are gathered by various products, and possible conflicts with existing XML/XSLT libraries Subquestions o Tomcat 4 o Tomcat 3 o IBM Websphere Oh, i have this at hand: Put a copy of a working parser in some directory where WebSphere can access it, for example, if /usr/webapps/yourapp/servlets is the classpath for your servlets, copy the Xerces jar into it (any other direcotry would also be fine) Do not add the jar to the servlet classpath, but add it to the classpath of the application server which contains your web application. In the WebSphere administration console, click on the environment button in the general tab (i have a german version so you may see different names). Fill CLASSPATH in the varianble name box and /usr/webapps/yourapp/servlets/Xerces.jar (or whatever your complete path is) in the value box, press OK, then apply the change and restart the application server. o Others? The mail archive is not very responsive about this today. 1.11 Method not found Explain possible incompatibilites (XML parsers, XSLT engines, Batik). Refer to previous question. 1.12 FOP and multithreading FOP is not thread safe. Explain consequences. 1.13 FOP memory consumption (should be higher in the list). OutOfMemoryException. Mention redesign effords Suggest using multiple page sequences if possible 2. Batik/SVG specific questions 2.1 SVG text rendered in bad quality, how to put SVG text as text into PDF That's here
RE : Antwort: RE : Antwort: Re: Antwort: RE : problem with attribute: visibility
If you use a dtd, try to assign #160; as a value for nbsp; -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Envoyé : mercredi 17 avril 2002 16:49 À : [EMAIL PROTECTED] Objet : Antwort: RE : Antwort: Re: Antwort: RE : problem with attribute: visibility Thank you Nicolas this works. But you have to use #160; instead of nbsp; which obviously cannot be processed.
