Hussein Shafie wrote: >> 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). >> >> idea. > > Yes very clear. Thank you for your explanations. > > I'm sorry but I don't see how step [2] could be implemented only by > using our extension mechanisms.
In the case of DocBook, whose elements do contain attributes for changes ( revision, revisionflag ), if there was a hook available to process/modify an element post-insert, the extension could just set these attributes on any element insert/paste/edit. If the revision checking is on, mark all edited elements with revisionflag='changed' and revision equaling the latest entry from "/book/bookinfo/revhistory/revision/revnumber". Also, as part of some uber DocBook revision management extension, I nice GUI swing renderer for the revision history block could be implemented making easy entry of elements ( maybe, not really required, but would be nice from a wizard style "you've chosen to enable revision control, but you're document doesn't include revision information". The "book/bookinfo/revhistory" element could also be located in another XML document ( due to multipart documents... ). Hmmm, I also note that revhistory can also be included in a <sectioninfo/> element for tracking revisions in a section, but XXE doesn't seem to know about <sectioninfo> ( http://www.docbook.org/tdg/en/html-ng/sectioninfo.html ) - maybe this is part of the newer DocBook spec? Mark
