Nuno wrote: > > Hi Bill, can you please elaborate a wee bit more your solution because I > can't quite figure out how what you propose solves the problem at the > moment. >
Hi Nuno, I think Mike McNamara's follow-on posting does a nice job of explaining the problem and potential solution further. (In fact, Mike is a colleague and we have worked on similar systems in the past). The basic point is this--you need a pagination engine to determine and then preserve page boundaries. Especially for any kind of complex page layout, there is tremendous logic behind pagination rules, so why write the logic into the CMS? And there is nothing in a generic CMS platform that will help with this. So the solution for this kind of problem is to tie the two systems together-- a CMS to manage the content in some logical organization, and a pagination engine to determine and later preserve page boundaries. You could then have some integrating code that passes the page boundary information back to the CMS. I have worked on XML-based systems that would, as an example, preserve the page boundaries in the source XML as a processing instruction. My experience is with commercial pagination engines, but this could be done with solutions like TeX and XSL, depending on the composition and pagination requirements. Hope this helps, and, by the way, I really enjoy your postings to this list. Bill -------------------- http://www.nmpub.com -- http://cms-list.org/ trim your replies for good karma.
