This has been a lacking feature for my uses as well. We have implemented a current solution, though its not perfect and only really works for DocBook.
All our files are stored in CVS, so its easy to checkout different versions, and tag all files with the revision number when a revision has been approved, etc. We customized Norm Walsh's DiffMK program and added it into XXE. Then all you have to do is checkout two versions of a file from cvs, open one in XXE, click on our customised "Diff" button, choose the second file and voila it gives you a diff.xml file showing added elements in green, changed in yellow and deleted in red. DiffMK adjusts the revisionflag attribute on elements and then you just add your customised css file to display the revisions appropriately. As I said, not a perfect solution, but its works well enough for my users needs. I think revision tracking would be an excellent feature to add to such a great product as XXE. But if not, Jirka hopefully I've given you some ideas of how you could add your own revision tracking in if you need to. Dominique Jirka Kosek wrote: > Hussein Shafie wrote: > >>> Jirka Kosek wrote: >>> is there any way to implement revision tracking in XXE? XXE PE suits >>> almost all needs for my project except revision tracking. >> >> >> I cannot answer this question. I need more information about what you >> would like to have in terms of revision tracking (is it integration >> with something like CSV or subversion? Is it automatic filling of >> DocBook attributes such as revision and revisionflag after an editing >> session? etc) >> >> If you send another email with a short specification, *may be* I'll >> be able to outline how this could be implemented using XXE extension >> mechanisms (commands, document hooks, style sheet extensions, etc). > > > OK. There is a short description: > > 1. At any time during editing of document user can turn on/off > revision tracking. > > 2. When the revision tracking is on all added text is shown in > different color and deleted text is shown with line through. Status of > text is captured by processing instructions (capturing it by means of > DocBook markup seems too complex to me and it would not work for other > DTDs). > > 3. At any time user can invoke revision approval. During this process > editor will offer each revision for approval step by step. For each > revision user can decide to accept it (=> corresponding revision > markup is removed as well text marked up as deleted is deleted), > reject it (changes are rolled back) or left it untouched. From user > point of view this function is very similar to spell checking. > > I hope that it is clear now. You can also see how revisions work in MS > Word or in XMetaL to get better idea. > > Thanks, > > Jirka > >------------------------------------------------------------------------ > > >-- >XMLmind XML Editor Support List >xmleditor-support at xmlmind.com >http://www.xmlmind.com/mailman/listinfo/xmleditor-support > __________________________________________________ This Message is intended for the addressee named and may contain confidential information. If you are not the intended recipient, please delete it and notify the sender. Views expressed in this message are those of the individual sender and not necessarily the views of the Judicial Commission of NSW.
