Yes, I can imagine (and had already accepted) that colouring text in the XML editor window based on an attribute setting would not be a trivial task. An XSLT tweak for using the same attributes to style WebHelp/.pdf output, though, would be pretty nifty :-}
On Mon, Jan 19, 2015 at 9:51 AM, Hussein Shafie <[email protected]> wrote: > On 01/12/2015 08:38 AM, Niels Grundtvig Nielsen wrote: > >> Well, you're right there – the Compare tool seems to do an excellent job >> of identifying changes between files. The only snag is, that's not what >> I need to do at the moment: I need to use the out-of-the-DITA-box status >> attribute to apply different styles to WebHelp (and possibly pdf) output. >> > > We are aware of this need, which is not an uncommon one. > > > > >> I suspect this is going to mean rolling my sleeves up and trying to get >> somewhere with XSLT :-} >> > > There are two problems here: > > 1) Marking modified elements using the DITA status attribute. I don't see > how this problem can be solved simply. > > A future version of the Compare tool could be used to automatically mark > modified elements using the DITA status attribute. However only new and > modified elements could be marked this way, not deleted elements. This > makes this feature not really useful. > > 2) Correctly rendering DITA elements bearing the status attribute by > slightly modifying the XSLT stylesheets. This problem should be quite > simple to solve. > > > > > >> On Mon, Jan 5, 2015 at 11:05 AM, Hussein Shafie <[email protected] >> <mailto:[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 >> <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 >> <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 >> >> >
-- XMLmind XML Editor Support List [email protected] http://www.xmlmind.com/mailman/listinfo/xmleditor-support
