On 02/17/2012 12:06 PM, Philippe Nobili wrote: > On 02/17/2012 11:49 AM, Philippe Nobili wrote: >> the only way (the only we have found) is to manually edit the file >> under a text editor and remove the trailing processing instruction. >> This is something we cannot ask our authors to do. > [Correction] > > Actually this is not true, our apologies; if can make a fake change, > back and forth, then save the file again, which has the effect to > recalculate the processing instruction.... > > If implementing our suggestion is not to complicated, we feel it would > be preferable since the error message is somewhat frightening for our > authors... (i.e. often, they do not go any further and close the > document !).
We'll implement both your RFEs. The first one in XXE v5.2 (March 2012) and the second in the release which will follow XXE v5.2. --- PS: Not directly related to your second RFE, however please note that convertdoc has useful -cmp and -diff command-line options. See http://www.xmlmind.com/xmleditor/_distrib/doc/commands/convertdoc_usage.html On 02/17/2012 12:06 PM, Philippe Nobili wrote: > > We plan to deploy release 5.1.1 of XXE for all our authors in order to > benefit from its compare tool. > > We would like to report one issue we have with it -- which seems easy to fix > --; this issue is a blocker right now for this deployment; here it is: > > Context: In our workflow, it may occasionally happen that DocBook files are > modified by external XSL transformations, to account for global changes. > > The Issue: In this situation, XMLmind complains that it cannot reactivate the > track changes when we reopen the file. > We perfectly understand the reason for this and it is not > a problem for us. > > The problem however, is that there seems to be no way to > reactivate it from XMLmind; the only way (the only we have found) is to > manually edit the file under a text editor and remove the trailing processing > instruction. This is something we cannot ask our authors to do. > > Could we suggest to retain the warning dialog (with an option not to show it > again...), but instead of leaving the file in this state, to remove the > corrupted processing instruction and recreate it from the actual content of > the file, thus reactivating the changes from scratch ? This would completely > solve the issue for us. > > Many thanks for your help or suggestion if you have missed something. > Best regards. > Philippe. > > PS: Below a suggestion for improving command-line access to the XXE compare > tool. > > One Suggestion: > > We discussed about the compare tool in XXE versus the integration of a > generic XML diff engine for integration with a SCM system; finally, we agree > that the solution you have chosen is very effective. > > An additional command-line option, e.g. "-cmp", "-diff", etc... would make it > even more efficient when XXE is launched on two files (typically a diff > command from a SCM system between two revisions of the same XML file...). > > E.g. xxe -diff xml1 xml2 Would open both files (as now), and also activate > the compare tool (if possible being given the 2 files), thus providing a > powerful XML comparison tool, directly callable from SCM client windows... -- XMLmind XML Editor Support List [email protected] http://www.xmlmind.com/mailman/listinfo/xmleditor-support
