On 12/01/2015 10:30 AM, Grundtvig Nielsen Niels wrote:
Thanks to your earlier advice on conditions, I'm now fairly confident
with using <ph status=> and a ditaval file to flag changes between two
versions of a document.
What I'm wondering now is whether it's possible to use both status and
rev for really fine-grain control of output. When I was managing
regulatory documents in FrameMaker, I used conditions to achieve a
sequence like this over the course of three revisions, without needing
to delete anything in the source files before producing revision C:
*revision A*
Runway orientation is 137°W
*revision B*
Runway orientation is 137°W138°W
*revision C*
Runway orientation is 138°W
In approximate DITA code, I guess the update would look something like this:
<p>Runway orientation is
<ph rev="B" status="deleted">137°W</ph>
<ph rev="B" status="new">138°W</ph>
</p>
So is it possible to use a ditaval file for revision B to say
IF rev="B" and status="deleted" – output text, formatted grey strikethrough
IF rev="B" and status="new" – output text, formatted green
---
<val>
<prop action="flag" att="status" color="gray" style="line-through"
val="deleted"/>
<prop action="flag" att="status" color="green" val="new"/>
</val>
---
("line-through" not standard but it is supported by XMLmind DITA
Converter , AKA ditac)
and then a new ditaval file for revision C to say
IF rev="B" and status="deleted" – do not output text
IF rev="B" and status="new" – output text with no special formatting
*May* *be*
---
<val>
<prop action="exclude" att="rev" val="B"/>
<prop action="include" att="status" val="new"/>
</val>
---
But I'm not convinced that this would solve your problem.
Of course, all this can be easily implemented using a single attribute.
Example:
<p>Runway orientation is
<ph otherprops="B-deleted">137°W</ph>
<ph otherprops="B-new">138°W</ph>
</p>
I appreciate this is getting dangerously close to a DITA question rather
than a pure XXE question … but would welcome your advice.
Yes, this is a 100% DITA, 0% XXE, question. I tried to answer your
question only to promote a new XXE feature. See below, next to your [ps].
[ps] by the time I moved on, I had FM files that included tracked
changes for over thirty versions of the content;
As of version 6.4 (September 11, 2015), XXE can do this.
Excerpts from http://www.xmlmind.com/xmleditor/changes.html#v6.4.0:
---
XXE now allows to store all the revisions of a document in the XML file
containing this document. This option may be turned on by selecting
"Tools|Revisions|Store All Revisions in the Document" for the document
being edited or it may be turned on once for all by checking
"Automatically store all revisions in the document"
(Options|Preferences, Tools|Revisions section).
New menu item "Tools|Revisions|Open Revision" displays a dialog box
listing all the revisions of a document for which option "Store All
Revisions in the Document" has been turned on. This dialog box allows to
select one or more revisions in order to open or compare these revisions.
See http://www.xmlmind.com/xmleditor/_distrib/doc/help/revisionsMenu.html
See
http://www.xmlmind.com/xmleditor/_distrib/doc/help/toolsOptions.html#revisionsOptions
Tutorial "Reviewing changes using the Compare tool" has been updated in
order to show a typical use case for these new facilities.
See http://www.xmlmind.com/xmleditor/_tutorial/review_changes/index.html
---
no-one ever asked, but
it would have been possible to go back and generate the content from any
version with just the delta from the previous version highlighted
XXE cannot do this.
--
XMLmind XML Editor Support List
xmleditor-support@xmlmind.com
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
