On Sun, 2008-03-09 at 11:17 +0900, Gav.... wrote: > Hi All, > > This was going to be an email about how PDF was not working with Dispatcher, > more accurately that it did not work using Pelt Theme or any theme that does > not over-ride FO from /common/ . > > Usually, when I copy over Pelt Theme for over-riding to my project, I also > copy over /common/ just in case I need to change any of that too. This was > my downfall here, because changes made to /common/fo recently did not get > updated in my local project, so broke PDF output.
I usually never copy anything from core. In the rare case I need to override or alter the behavior of a common contract I only copy this contract to my project. The only things that you should have in your project is a general structurer/panels for your theme, some other url specific structurer and a couple of new contracts. > I then spent 1/2 hr fault-finding and correcting errors in > layout-master-set.ft only to find that this had already been done in > whiteboard. > > So, a doh! moment for me, and a heads-up to anyone else that has local > copies of themes/common/* , remember to update them, better still, try not > to change anything in common, copy it to /pelt/ and change it there instead. No, do not copy ANYTHING at all to your project! Just implement the few pieces that you want to override in your project. Remember we are still in the whiteboard and some changes are not announced (there have been a couple of mails about this whole topic when the pdf got updated). Some of the more recent change to document-to-fo.xsl needs to be synced with some of the fo-contracts but most fo-contracts are now using the helper stylesheets from the pdf plugin. salu2 > Gav... -- Thorsten Scherler thorsten.at.apache.org Open Source Java consulting, training and solutions
