Re: [PAF] FTW makes broken GEDCOM -- how to import cleanly into PAF 5?

[John Reynolds <jjreynold@home.com>]

Actually I got the problem solved. As I was saying in my last post it
was
really a Family Tree Maker bogon. Once I switched a mapping over to a
more
correct GEDCOM tag it "worked." I actually think they've made PAF read 
in this "still broken, yet not as broken as before" GEDCOM exported from
FTW 4 or 3 despite the fact that the GEDCOM still is not correct.
Whatever.
I'm happy--all my data is in PAF5 now (not seeing any bizzare problems
with
PAF5 either, but I've not been on this list long, so I don't have the
context
you do). I just wish I could get the file-format specifics for the .paf
so that I could throw together a "paf like" clone for Unix :)

-Jr

OldMingus@aol.com wrote:
> 
> HI there.  I too am a computer weinie with some 45 years wrestling
> problems
> for the LDS Church.  I am still using PAF 4.0 for the very reasons you
> so
> clearly delineated.  I suggest you make contact with Salt Lake and see
> what
> they recommend.  They are the ones who screwed up the latest versions
> of PAF.
>  I think you will find some very sympathetic people there and good
> information instead of hearsay.
============================================================================
For assistance and help for the PAF Mailing List please contact
ed.rogers@innernet.org or http://www.innernet.org/paf/
Searchable list archives at http://www.innernet.org/paf/archives/
Want to unsubscribe? Try this link:
mailto:majordomo@innernet.org?subject=unsubscribe&body=unsubscribe%paf
============================================================================