On 25 Jan 2023 as I do recall,
Harriet Bazley wrote:
On 25 Jan 2023 as I do recall,
News wrote:
[snip]
Having just checked his web site, the latest version of Compare is v.
0.32 (23 Jun 2014).
Ah - which specifically mentions that it "Fixed SpriteOp error with RO5.21"....
http://www.avisoft.force9.co.uk/Compare.htm
In my defence, I did do a cursory Web search for "Martin Avison
Compare", but none of the results seemed to be anything to do with RISC
OS, so I assumed that if he really was the Martin Avison of
"angelgroups" then he had gone on to higher and more financially
rewarding things...!
I made a few minor changes to an Impression file (I edited
the contents of one line and deleted a paragraph altogether), then used
Compare to examine them against one another. As expected the
direct byte/line comparisons are not terribly helpful, throwing up 33 differences in files of only 127 and 128 'lines' long respectively.
Although since these are not ASCII files a new 'line' is presumably
anywhere that a linefeed character happens to occur randomly in the
binary data....
The 'Block' mode does much better, identifying ten differences in six
different 'blocks' within the files with large chunks of unchanged data
between them. The first change appears to be the actual filename (which
I had no idea Impression embedded within the document!), and I can't
guess at the second one, although it occurs alongside plaintext strings
such as 'A4' and 'Landscap' so probably has something to do with the formatting/layout of the file, even though I didn't actively change
that. The third block is just two characters that differ within a chunk
of pure binary data and could represent anything.
The fourth block reflects the actual edit I made to the file, altering FEB/MARCH to OCTOBER/NOVEMBER, which shows up quite clearly. The fifth
block is more unknown binary data, and the sixth block reports the text
which is present in the first file but was deleted from the second.
The output file is still quite difficult to read, because it is full of non-ASCII characters between and surrounding the legible text - that is
just what raw Impression files look like, I'm afraid, and why I really
can't cut and paste the output here, because goodness knows what nntp
protocols would do to it in transit - and because as a result StrongED
defaults to loading it into binary Dump mode, so you need to be
sufficiently a power user to be able to force the display back into
BaseMode in order to be able to read it as intended.
I can't say that I'd recommend this as a means of detecting changes
between Impression files for a casual user, but if you are happy poking
around raw chunks of data and have some idea of what edits you made then
you *can* identify the basic differences between the two versions of a
document by this method. It probably isn't what Fay is looking for,
however. :-(
--
Harriet Bazley == Loyaulte me lie ==
St George for England - St Pancras for Scotland
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)