Hi Darrel, Actually, this is an old problem, and not so unusual at all, if I understand it correctly. A lot of legal material relies on fixed page boundaries for ongoing publishing, and what is often called "looseleaf" updates where only the changed pages are updated, printed, and redistributed. This is becoming less common as more and more legal databases are computerized, but the problem persists, especially in markets that might not justify everyone cutting over to a more computerized set up.
I think the solution is to look into a composition engine that supports this kind of pagination, where page boundaries are carefully maintained version to version. You could then product PDFs for distribution. This suggests, then, a workflow, where the source can be some kind of structured form such as XML but the composition/output engine would need to be linked in such a way that the page boundaries can be tracked. By maintaining the structured source, you can eventually run with this when the pagination requirement is eventually retired, which I suspect it will be (though perhaps later rather than sooner). There are some commercial solutions for this kind of thing. I would be happy to pass along some names. Bill > > The easy solution is to just publish them as PDFs, but that just doesn't > seem to be the elegant solution in my mind. Is there way to store > structured > content in a way that also retains the page structure of the > original typed > paper document? Or would PDF be the way to go? > > -Darrel > -- > http://cms-list.org/ > trim your replies for good karma. > -- http://cms-list.org/ trim your replies for good karma.
