in reply to Re: Converting GEDCOM files
in thread Converting GEDCOM files

Hi chipmunk this does not work :o(

Update

Seems fixed now though. Really clever solution. I really like the "\n0" now that I understand it ;-) - a very neat way to chop the file into records, much nicer than the method I used.

I have learned a very good use for $/ in a practical example - thanks.

cheers

tachyon

s&&rsenoyhcatreve&&&s&n.+t&"$'$`$\"$\&"&ee&&y&srve&&d&&print

Replies are listed 'Best First'.
Converting GEDCOM files
by Joes (Acolyte) on Jul 10, 2001 at 16:28 UTC
    Hi tachyon.
    1. In the clever little script you did for me, I find that I should have asked for the GEDCOM line 1 CHAR IBM DOS to be changed to 1 CHAR ASCII
    Can you please show me how to insert an amendment in your script?

    2. The standard for the GEDCOM names after each 0 @Inn@ INDI is in the next line:
    1 NAME First_name Middle_name/SURNAME/
    The first name syntax is as shown, with the first character in Upper case.
    The SURNAME between the forward slashes is in UPPERCASE, as shown.
    Unfortunately, in merging many GEDCOM files from various genealogists, we end up with sample names like:
    JOE/SLAVEN/
    Joe McDonald/Slaven/
    Joe McDONALD 'Macca'/SLAVEN/
    /SLAVEN/
    Joe
    Joe/SLAV.../ (this last one when the surname is illegible)
    Any chance of you please having a go at looking at each 1 NAME Firstname Middlename/SURNAME/ line and converting it to the standard syntax?

    3. In selecting the name of the output file, how do I go about naming it as the original input file name filename.ged, but with PAF added, as in filenamePAF.ged My best wishes
    Joe, Townsville, Australia

[reply]
[reply]

In Section Seekers of Perl Wisdom