Replacing variable length file paths in a GEDCOM file

Web Master

@peterjones Thanks. I’ll try coaching the user first. :)

I am so impresssed with the speed and quality of response to my post. Thank you so much Alan and Peter

Neil Schipper

@web-master Hi. Here’s a variation on Alan’s solution which has the feature that users enter the replacement text as is (so they won’t have to be so careful about entering text into a field containing cryptic regex codes) : (?<=^\d FILE /).*(?=/)

(Edit: slightly simplified)

Web Master

@neil-schipper said in Replacing variable length file paths in a GEDCOM file:

(?<=^\d FILE /).*(?=/)

Forgive me Neil, but I’m not clear how to use this modified example?

Neil Schipper

@web-master I could have been more clear.

The idea is that you perform a Regex search in the same way as the earlier recipe, except the Find expression is the one I offered, and, the Replace expression is simply and completely the text you want to substitute in.

Thus, instead of your people having to carefully modify the Replace expression from ${1}/Smith_1234/ to ${1}/Jones_4567/ as they proceed from one task to the next, they can more comfortably change Smith_1234 to Jones_4567 – no funny confusing text in the Replace text box.

Also, if you want the solution to be robust against users inadvertently checking that option box to the right of Reg Exp, prefix the Find expression with (?-s) as per Alan’s earlier expression.

Also, if you want to make it impossible to match a completely empty path (nothing between two slashes: //), in my Find expression, we’d replace * with +, hence: (?-s)(?<=^\d FILE /).+(?=/)

Web Master

@neil-schipper Hi Neil. OK, that’s what I thought you meant, but when I do that, Find and Replace does nothing

Alan Kilborn

@neil-schipper said in Replacing variable length file paths in a GEDCOM file:

Also, if you want to make it impossible to match a completely empty path (nothing between two slashes: //), in my Find expression, we’d replace * with +

I’m surprised you changed (my) original usage of .+ to .* in your version, then backed it out with “we’d replace * with +”. :-)

Neil Schipper

@web-master

Just to be clear:
Find: (?-s)(?<=^\d FILE /).+(?=/)
Replace: Smith_1234
Mode=regex; checkbox to the right doesn’t matter anymore

Then, Find Next to observe expected matching, Replace to perform the substitution on the currently selected match, Replace All to perform the substitution on entire file.

I have tested this. Are you sure you aren’t acting on a file that has already had the substitutions done?

Neil Schipper

@alan-kilborn said:

you changed (my) original usage of .+ to .*

That’s not how it actually went. I devised my solution independently from reading the OP (deciding early that it should have a look-behind and a look-ahead). Then I saw you had a solution that was satisfactory, and I saw no reason to pipe in.

Much later I noticed in the follow-up convo that @web-master was trying to reduce complexity for his non-technical volunteers, and realized my solution was favorable to that. And it was after that that I realized our solutions also differed in the modifier, and that the asterisk was maybe a bit too loose (although, dollars to doughnuts, they perform equally).

Alan Kilborn

@web-master said in Replacing variable length file paths in a GEDCOM file:

Is there a way to put this into a macro so that at runtime the user is prompted for the replacement string?

As @PeterJones mentioned, not possible with a macro.

But as a PythonScript it is rather simple:

replacement_text = notepad.prompt('Replacement text:', '', '')
if replacement_text:
    find_regex = r'(?-s)(?<=^\d FILE /).+(?=/)'
    editor.rereplace(find_regex, replacement_text)

You’d run the script and then get prompted with:

After pressing OK the replacements would be made.

Web Master

@neil-schipper Yes, I copied and pasted the expression direct from here and the file had def not been processed already.

I don’t know what the protocol is here. May I PM you the file so you can try it?

Alan Kilborn

@web-master

Why don’t you just post a line – or a few lines – here that you think it should match, but it isn’t? That may be more instructive (for those reading along) than taking it offline into some private discussion.

While initially impressed with your initiative, I’m now losing faith in your debugging skills. :-(

Neil Schipper

@web-master Does PM mean the chat? Sure go ahead, but I’m not sure if it supports file transfer. Another option is to put file on a hosting site so we can all access it.

An easy thing to do is to gather up at least a few screens worth of “interesting” data (stressful/challenging to the algorithm) and tossing it into a “literal text” box as you’ve already learned to do (I’m not sure of upper size limit). (Here’s a trick: to defeat inappropriate colorization, add txt immediately after the opening line’s triple-backquotes).

But over and above all of this, do notice that Alan’s post above provides a solution that is everything you dreamed of. You’ll need to install the Pythonscript plugin and learn a bit about making / saving / running a script (I’ve seen step-by-step recipes; I expect someone will link you to a reliable up-to-date one).

Have fun.

Web Master

@alan-kilborn Hi Alan

I have to be circumspect about what I put in a public domain because a GEDCOM file contaions personal; info of living people so there’s a GDPR issue. But, sure I can cut out some of the lines that are giving trouble and post them here. One moment…

Web Master

@web-master OK here are a few lines that are not following Neil’s rule. Note NONE of the lines in the 4,000 line file were changed. It said there were zero occurrences. I copied and pasted the query so it shouldn’t be operator error, but PICNIC problems can’t be ruled out! :)

2 FILE ~/Pictures/Reunion Pictures/Imported Media/HOBDAY, Audrey Lilian.jpg
2 FILE ~/Pictures/Reunion Pictures/Imported Media/HOBDAY, Audrey Lilian - 1.jpg
2 FILE ~/Pictures/Reunion Pictures/Imported Media/HOBDAY, Audrey Lilian - 2.jpg
2 FILE ~/Pictures/Reunion Pictures/Imported Media/Robert Frederic & Audrey Lilian - 3.jpg
2 FILE ~/Pictures/CUMBERLAND BMD/Audrey Cumberland Death Certificate.jpeg
2 FILE ~/Pictures/HOBDAY/Mums School Report.jpg
2 FILE ~/Pictures/CUMBERLAND Parish Registers/Frederick Charles Cumberland Baptism 1901.jpg
2 FILE ~/Pictures/CUMBERLAND BMD/Frederick Cumberland Death 1985.jpeg
2 FILE ~/Pictures/CUMBERLAND DAVIS PHOTOS/Cumberland L0005.jpg
2 FILE ~/Pictures/CUMBERLAND DAVIS PHOTOS/Cumberland L0332.jpg
2 FILE ~/Pictures/CUMBERLAND DAVIS PHOTOS/Cumberland L0370.jpg
2 FILE ~/Pictures/CUMBERLAND DAVIS PHOTOS/Cumberland L0003.jpg
2 FILE ~/Pictures/CUMBERLAND DAVIS PHOTOS/Cumberland L0150.jpg
2 FILE ~/Pictures/CUMBERLAND DAVIS PHOTOS/Cumberland L0014.jpg
2 FILE ~/Pictures/CUMBERLAND DAVIS PHOTOS/Cumberland L0080.jpg
2 FILE ~/Pictures/CUMBERLAND DAVIS PHOTOS/Cumberland L0141.jpg
2 FILE ~/Pictures/CUMBERLAND DAVIS PHOTOS/Cumberland L0172.jpg
2 FILE ~/Pictures/CUMBERLAND DAVIS PHOTOS/Cumberland L0254 (2).jpg
2 FILE ~/Pictures/CUMBERLAND DAVIS PHOTOS/Dance Programme 1.jpg
2 FILE ~/Pictures/CUMBERLAND DAVIS PHOTOS/Dance Programme 2.jpg
2 FILE ~/Pictures/CUMBERLAND DAVIS PHOTOS/Dance Programme 3.jpg
2 FILE ~/Pictures/CUMBERLAND BMD/Frederick Cumberland Cremation 1985.jpg
2 FILE ~/Pictures/CUMBERLAND DAVIS PHOTOS/Dance Programme 4.jpg
2 FILE ~/Pictures/CUMBERLAND DAVIS PHOTOS/DSCN0101.jpg
2 FILE ~/Pictures/CUMBERLAND DAVIS PHOTOS/DSCN0102.jpg
2 FILE ~/Pictures/CUMBERLAND CENSUS/Frederick Cumberland 1921 Census.jpg
2 FILE ~/Pictures/CUMBERLAND CENSUS/Frederick Cumberland 1921 Census (1).jpg
2 FILE ~/Pictures/CUMBERLAND DAVIS PHOTOS/Cumberland L0108.jpg

Alan Kilborn

@web-master

My 30ms reaction to this data: The ~ is a new, never mentioned before feature of your data. Of course the expressions provided before don’t match it. But you already know this.

Web Master

@alan-kilborn I mentioned in my OP - bullet 2

Alan Kilborn

@web-master said in Replacing variable length file paths in a GEDCOM file:

I mentioned in my OP - bullet 2

It’s true; you did:

The old file path always starts at char 8 in the string but may be: \ / ~ or a drive letter, so position 8 is the most reliable start point

But everyone missed it. :-)
Because we are more focused on sample data and what it looks like.
I guarantee it wouldn’t have been missed if it was provided as part of the original sample data.

Web Master

@alan-kilborn I shall breakout the sackcloth and ashes. :)

Alan Kilborn

@web-master

Possibly the expression you now want (OK, you wanted it from the start!) is:

(?-s)(?<=^\d FILE )~?/.+(?=/)

BTW, here’s the English explanation of it, for maximum learning:

Use these options for the whole regular expression (?-s)
- (hyphen inverts the meaning of the letters that follow) -
- Dot doesn’t match line breaks s
Assert that the regex below can be matched ending at this position (positive lookbehind) (?<=^\d FILE )
Match the character “~” literally ~?
- Between zero and one times, as many times as possible, giving back as needed (greedy) ?
Match the character “/” literally /
Match any single character that is NOT a line break character (line feed, carriage return, form feed, next line, line separator, paragraph separator) .+
- Between one and unlimited times, as many times as possible, giving back as needed (greedy) +
Assert that the regex below can be matched starting at this position (positive lookahead) (?=/)
- Match the character “/” literally /

Created with RegexBuddy

Neil Schipper

@alan-kilborn said in Replacing variable length file paths in a GEDCOM file:

~?

New spec says we need to handle both kinds of slash, tilde, and drive letter, so it needs to be more complex than that, right?

Annoyingly, since the behind text is now varlen, this demolishes the glory of replace text being pure user-text.

Instead of mucking about with all the variations of drive letters and slashes and tildes, I’m gonna propose a looser spec:

following <space after “FILE”>, match any run of text, min len 1, until trailing forw slash

Hence:

Find (?-s)(?<=^\d FILE ).+(?=/)
Replace: /Smith_1234
So replacement text now needs the starting slash.
To keep the user experience elegant, this would be incorp’d into the script:

editor.rereplace(find_regex, '/' + replacement_text)