jim said:
>   You are attacking my reply re attaching licensing terms
>   by attaching it to unrelated discussions.

jim, i'm not "attacking" anything.  let's steer clear of antagonistic language.

and if you had quoted what you were replying to, i would have _known_
the scope of your reply.  don't blame me because i'm not a mind-reader.


>   Again, you are assuming the problem presupposes a solution
>   which is one of "Choose A" or "Choose B".

well, since my tool lets a person _edit_ either choice a _or_ choice b,
i think i've given the user plenty of leeway.


>   If you use the tool on other than trivial problems
>   you will find out that life is not that simple

oh please, jim, wake up.  i've actually _done_ the kind of comparisons
and diff-resolutions that you're just _talking_about_.  moreover, i have
done them _many_times_.  so i think i have much better _experience_
with the actual situation than you do.  so don't try to "school me", ok?


>   frequently both A and B have some degree of errors that need
>   to be corrected and/or merged to get you where you want to go.

now you're just repeating your "frequently" term, which i have already
demonstrated to be false, using the most recent example i have shared.

in all the resolutions i've done, the vast majority of diffs involved cases
where _one_ of the versions was correct.  very rarely were both wrong...


>   If one wanted to make a graphical tool to do this

i not only _wanted_ to make such a tool, i actually _programmed_ it...


>   If one wanted to make a graphical tool to do this
>   you would not only need the "Choose A" and "Choose B" options
>   but "Edit in Context while displaying a copy of the original scanned page"

you need to read what i wrote, jim.  my tool gives people the option to
edit either choice a or choice b, before selecting that particular choice.

as for displaying the scan, does your pgdiff tool show that information?
because if your tool can show that info, my tool can display the scan...
but as far as i can see, from your limited example, you don't show that.

(and when i say "my tool" in this post, i mean the tool that i wrote that
_supports_ your tool.  in the tools that i've programmed for _my_use_,
i _always_ retain the page-scan information, so i can _display_ the scan.)


>   and if one wants to make that kind of tool one would be
>   better off to put the time and effort into figuring out a tool

and here we wander off into the land of unnecessary complexity...


>   This is not my experience

i've shared many of my experiences in doing the comparison method.
if your experience doesn't match mine, you should share yours as well.


>   Post a portable version or one compiled for windows
>   and I will tell you how it works for me in practice. 

i need to have some questions resolved before i put it out in public.
that's why i furnished you some sample texts to get pgdiff output on.

-bowerbird