
jim said:
Sorry – I guess I assumed people know how to use a regex editor!
um, you just shot yourself in the foot, jim. you assume that people know how to use a reg-ex editor, but you also assume they need to have wdiff wrapped in an .exe? not much logic there, i'm afraid... but hey, for the sake of completeness of the thread, how about you quickly run through how i'd "use a reg-ex editor" for this? because i honestly don't know. (and i _do_ know how to wdiff.) -bowerbird

but hey, for the sake of completeness of the thread, how about you quickly run through how i'd "use a reg-ex editor" for this? because i honestly don't know. (and i _do_ know how to wdiff.)
On Vim I type: :/[{|}]/ Which highlights the edits and takes me to the next set of edits to choose from, thereafter I just type ‘n’ to move to the next set of fixes that I need to deal with. I like Vim because I can just keep my fingers on the keyboard where they belong while editing and not have to mess with the mouse. When you are versioning it is frequently not as simple as “choose A” or “choose B” but often a mix of both that you have to edit. And I like seeing each next to each other in context to help figure out what the “correct” editing moves are. IE if A is the target then maybe it has a word with a scanno, and B has the word without the scanno but with an incorrect capitalization. For example if B is an old PG text you are versioning then it may have ‘italics’ in ALL CAPS whereas A had it in real italics which increases the chance of the A OCR making a scanno. Also these are often the edits are a mixture of inserts, deletes, and substitutions. PS: You criticize me for doing that which the creator of wdiff said he would do if only he had the gumption. PPS: How do you use wdiff to recover lost linebreaks?
participants (2)
-
Bowerbird@aol.com
-
James Adcock