I need to add the facility to post the latest issue at the footer per page as opposed to per section/chapter within a manual.
The issue is taken from a change element's issno attribute value. As there may be several changes per page, I need to get the latest change for each page. If a page has not been changed, it retains issue 1 in the footer.
I know this has not been possible with Editor in the past as the issue number could not be resetfollowing the up issued page as there is no way of determining page end; the latest issue just ran on to subsequent pages until the next issue changed it.
Does anyone know whether this has now been resolved so that changes per page can easily be supported ?
yeah...I remember Arbortext providing a solution at one stage but as you say...nothing provided in the core product. Thishas beena major drawback with Arbortext Editor as there have been numerous requests over the years from major aerospace and defence organisations who want to have this page change functionality. Ended up having to get the author to insert issue end PI's into the markup to reset the issue. However, this proved time consuming as each time, a print preview was required to determine where this should be inserted. It only worked if inserted at the top of the following page the issue needed reseting. If there were some way of dtermining page end that may help. Thanks
First of all, I would think what you're asking can be done through FOSI and ACL combinations. I agree in that it's complex, to say the least. There are many liimitations to the FOSI in evaluating the document, especially when it comes to where the end of the page occurs. PE (and Editor) performs a composition in 2 passes... First to lay out all the formatting of the elements, and then to lay the results out on pages. The two don't overlap in any way so moving information (variable values) between the two is very difficult. I find myself constantly using ACL to add to the FOSI thoselimitations. Especially when I have to manipulate the content based on some condition.
Off the top of my head, you could tie a function to each element that would have an issue number, call a function that would compare the element's valueto a running value to get the highest, clear the element's value after the element, use the highest value at the bottom of the page and then clear the running value after the page. Sounds good in theory... haven't specifically tried it.
As for Arbortext and a Change Package...PTC (Arbortext)DOES have the Change Page for Defense system that is an add-on to PE. I've been specificially invovled with Versions 1.2, 1.4, 1.5 and now 1.6 M010 (tied to PE 5.4M020). It is an ongoing product that, to the best of my knowledge, will be around for some time. It is based on the TMSS DSS set supporting about 23 different DTD's. It works quite well, I might add. As long as you are not using a CMS to manage your documents, It would do well for you.
Anyway, for what it's worth, that's my 2 cents...