From: Paul V. <pa...@vi...> - 2004-08-17 12:35:40
|
Hi Lester, >> So the only option (at least as long as we use Apache FOP) seems to >> be: wrap every header in a single-cell table together with the text >> that follows it. This requires editing our transformation >> stylesheets; don't know how complicated it will be, but I'll have a >> look at it (somewhere in the next weeks). Hm, this approach has its drawbacks: it could lead to lots uf *unwanted* pagebreaks, namely if header + all of the following text don't fit on the remainder of the page. But I've thought of something else (see next post). > Seems to be a bit of a major bobo ;) > It is the only thing that two of my customers both picked up and > commented on. Just a simple 'page break' would solve the problem, > and hopefully something that will come. Just need to find just where > to post a bug report :) It's not a bug - it's an unimplemented feature ;-) The people at Apache FOP are aware of this and full keep-with-next support will be implemented... one day. See the Standard Compliance page at http://xml.apache.org/fop/compliance.html more specifically: http://xml.apache.org/fop/compliance.html#fo-property-keepsbreaks > I'll pull the file set together to a single 'book' with 'chapters' > for each OS and probably a separate book for all the Eclipse > stuff. That does not need to be part of the basic stuff, but it will > be nice to have it all documented for my own reference. Yes, the Eclipse stuff - but also the logo stuff - shouldn't be in there. But the Eclipse info is very useful; could you make it an <article> so we can add it to the "Documentation for Firebird docwriters" book? That would be its rightful place. As for the logo stuff - is it ready to be published yet? I thought there needed to be some official OK first (from admin group and/or FFmembers). Greetings, Paul Vinkenoog |