|
[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
[Recent Entries]
[Reply To This Message]
Re: List of effective pages?
Subject: Re: List of effective pages?
From: Dan Vint <dvint@xxxxxxxxx>
Date: Sat, 15 Jan 2011 17:08:13 -0800
|
At 03:56 PM 1/15/2011, G. Ken Holman wrote:
At 2011-01-15 14:43 -0800, Dan Vint wrote:
Not looking for the code or anything right now, but I need to put
together a plan for a new project. I'm working in a milspec
environment and they require that changes be tracked by release for
when/what changed that page.
So first release everything is baseline and no problem. With
subsequent minor revisions, paragraphs and such will be modified.
We will track those changes with markup and a revision level. I
need to maintain the original page breaks as well so that I don't
get information reflowing between releases. Major additions would
create a new point page as well.
The footer for these changed pages will reflect the latest change
that was made and I need to produce a list of pages (a table up
front) that lists every page and its current revision.
Typically this would then be produced as a change package (just the
updated pages) for loose leaf publishing but they haven't required that yet.
Typically this has been done with FOSIs and either Arbortext
publishing or Datalogics composer, I would like to do this with FO if possible.
XSL-FO doesn't support loose leaf publishing because there is no
knowledge of page breaks from one publishing run to the next. No
database of page images either.
You might make some progress with an intermediate form like XEP's,
and comparing one to the next, but then I'm unclear how you would
create change pages, say page 138A/B between pages 137/138 and
139/140. How would you "restart" page 139 in the following run at
the exact same point where page 139 started on the previous run?
What I have seen with FOSI implementations is they put a PI at the
page break from the first run.. When I first started this email I was
only thinking about the LEP itself and capturing the information
about what changed. I had forgotten about the point pages until I was writing.
I figure this was going to be difficult.
Thankfully when my customers with LEP requirements have come to me
for XSL-FO they've been willing to abandon the LEP in favour of
getting to use XSL-FO. In each case they were abandoning loose-leaf
for complete electronic products. If you have change markup on the
way in then using markers one can tell that on a given page there is
changed content by adding something in the header/footer that the
page has changed, but you can't preserve the page breaks that follow
changed content.
If you can't convince your client to abandon loose-leaf, I think
you'll have to use something other than XSL-FO.
I have a hybrid product as it is and I'm making recommendations to
drop some features. I wasn't sure if this was one I wanted to (or
could) tackle with FO. I'll have to check with Arbortext, they may
have some extensions to help with this.
Thanks for the help.
...dan
. . . . . . . . . . . Ken
--
Contact us for world-wide XML consulting & instructor-led training
Crane Softwrights Ltd. http://www.CraneSoftwrights.com/s/
G. Ken Holman mailto:gkholman@xxxxxxxxxxxxxxxxxxxx
Legal business disclaimers: http://www.CraneSoftwrights.com/legal
---------------------------------------------------------------------------
Danny Vint
Panoramic Photography
http://www.dvint.com
voice: 619-938-3610
 |
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format
| RSS 2.0 |
|
| Atom 0.3 |
|
|
Cart
