The inability to use the comparison tool if you make use of tools other
than XXE to modify documents seems like a serious limitation. We
currently use a very old version of XXE but are considering buying the
latest version in combination with a switch from docbook to dita. The
comparison tool is very attractive in that context, but I find it hard
to imagine that we could restrict ourselves to only using XXE.
Would it be possible to produce (for example) a pair of command line
tools that:
(a) replaced the single processing instruction at the end of the file
with a GUID processing instruction inside each element
(b) reversed the process and simultaneously generated new GUIDs for any
elements without them
In other words, some simple means of enabling the comparison tool to
recognise changes made outside of XXE.
Regards
Kevin Flynn
On 11/16/2011 11:49 AM, Hussein Shafie wrote:
On 11/16/2011 10:30 AM, Philippe Nobili wrote:
This mail is just a feedback concerning the compare tool introduced in
release v5.1 of XMLmind XML Editor. Certainly, other customers may have
different views on the subject, we just hope this feedback can be useful
among other contributions.
What is implemented in XXE v5.1 is more or less similar to the "track
changes" mechanism you can find in MS-Word; it is very simple to use. It
does not require any change in the existing XML processing (XSLT etc
etc). The compare tool itself is very easy to use, reviewing changes is
very easy.
T*hose are very good points.
*
However, the overall "track changes" workflow as implemented in XXE 5.1
is not practical in our case, we try to explain why below.
There are two different situations where we need to consider changes
between XML files, both requiring different tools:
*1. *When authors review an XML document within XXE, the "track changes"
mechanism is exactly what they need. But, this must be kept *within one
single document*, and should not require a second document.
*Rationale:* Would force us to keep the life-cycle history of XML
documents (which one is the review of which one), and to keep two
documents, when there is usually only one, stored for instance in a SCM
(source code management) system.
Sorry but I don't understand. The Compare Tool is especially SCM friendly:
If you are using a document store of any kind:
[1] You may want to enable change detection in the last revision of all
your documents using convertdoc. See
http://www.xmlmind.com/xmleditor/_distrib/doc/commands/convertdoc.html
==> From now, an author who checks out its working copy will get it with
change detection activated.
[2] Turn on "Automatically activate change detection". See
http://www.xmlmind.com/xmleditor/_distrib/doc/help/toolsOptions.html#changesOptions
==> From now, an author who creates a new document will create it with
change detection activated.
If you do this, you'll have the equivalent [*] of a generic XML
differencing algorithm such as DeltaXML, plus a user-friendly GUI, the
Compare Tool, similar to the "Review Changes" tools found in other
applications.
Suggestion: Open XML, switch the "track changes", make changes, save.
The "compare tool" becomes a "review changes" tool which requires only
an XML document having the "track changes" on.
Sorry but I don't understand. XXE does not track changes at all (which,
in our opinion, is a good thing). See "Comparison with other approaches"
--
*Kevin Flynn*
Technical Author
Vizrt
Mobile: +47 9343 39 42
[email protected] <mailto:[email protected]>
*www.vizrt.com* <http://www.vizrt.com>
/Disclaimer: This email and any files transmitted with it are
confidential and intended solely for the use of the individual or entity
to whom they are addressed. If you have received this email in error or
are not the named addressee, you should not disseminate, distribute or
copy this e-mail. Please notify the author by replying to this e-mail
and destroy this email and any attachments. /
--
XMLmind XML Editor Support List
[email protected]
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
