Thanks for the tip! with 25+ years of explicit change-tracking under my belt, I'd not even thought about a compare function. I'll take a good look at the documentation and tutorial.
Mind you, explicit change tracking is often a requirement for regulatory documents. I used to maintain a large documentation set in FrameMaker where each release highlighted changes between that release and the previous release and the entire revision history (23 releases by the time I left the company) was safely stored in the single source-file for each chapter … Being able to style the output based on the status of <ph> could help with this approach, especially if the different states were also highlighted in the GUI. On Mon, Jan 5, 2015 at 11:05 AM, Hussein Shafie <[email protected]> wrote: > On 01/05/2015 10:36 AM, Niels Grundtvig Nielsen wrote: > >> Getting into the swing of things using DITA for deliverables here, and >> now we've reached the stage where the first document needs an upate. >> This prompts the question "what do you suggest for implementing track >> changes": should I use <ph> elements with attributes and tweak the >> stylesheet so I can mark added and deleted text, >> > > Personally, I would never do this given the fact we have the Compare tool: > > http://www.xmlmind.com/xmleditor/_distrib/doc/help/comparePane_primer.html > > > > or is there some more elegant approach? >> >> > Tutorial (including a screencast): > > "Reviewing changes using the Compare tool" -- http://www.xmlmind.com/ > xmleditor/_tutorial/review_changes/index.html > > OK, it's not change tracking per se (à la MS-Word), but it implements a > similar functionality and it works flawlessly whatever the number and the > complexity of the changes. I mean the author of a document will never miss > a change made by a reviewer. > > So my advice is: please give this feature a *serious* try. It will do the > job and you'll like it. > > >
-- XMLmind XML Editor Support List [email protected] http://www.xmlmind.com/mailman/listinfo/xmleditor-support
