Dave and I met about this yesterday and have some ideas.
First of all, one of our great challenges when developing the SourceWriter was
to ensure that no information is lost when sharing via GEDCOM. Because the
GEDCOM standard does not have specific fields for the specific SourceWriter
fields,
Hi Geoff, that sounds wonderful to me!! I would be glad to be a
tester for this if you have need for that kind of help. Also, there
is another guy who uses Legacy and TNG and who is also a good
programmer (better than I am anyway!). He said he would work with me
on the TNG end to see if we
Millennia Corporation
[EMAIL PROTECTED]
www.LegacyFamilyTree.com
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jenny M
Benson
Sent: Friday, August 15, 2008 10:52 AM
To: LegacyUserGroup@LegacyFamilyTree.com
Subject: Re: [LegacyUG] V7 Sources: Nifty formatting
Geoff, that sounds like a very well thought out and effective way to correct
the issue of the export. Well done.
On Fri, Aug 15, 2008 at 11:56 AM, Geoff Rasmussen
[EMAIL PROTECTED] wrote:
Dave and I met about this yesterday and have some ideas.
First of all, one of our great challenges
Geoff:
That sounds like a great solution to me - especially if you have an
option to export to TNG. Thanks for your efforts!
Gene
==
At 11:56 AM 8/15/2008, you wrote:
Dave and I met about this yesterday and have some ideas.
First of all, one of our great challenges when developing
Rasmussen
Sent: Saturday, 16 August 2008 2:56 AM
To: LegacyUserGroup@legacyfamilytree.com
Subject: RE: [LegacyUG] V7 Sources: Nifty formatting lost in gedcom output
Dave and I met about this yesterday and have some ideas.
First of all, one of our great challenges when developing the SourceWriter
]
To: LegacyUserGroup@legacyfamilytree.com
Sent: Wednesday, July 30, 2008 6:00:32 PM
Subject: RE: [LegacyUG] V7 Sources: Nifty formatting lost in gedcom output
snip
Your point about there being no one answer to sourcing is absolutely true,
and therein lies the problem. There are established
Gail:
What a crushing disappointment! I don't have a website, but as I've worked
away at converting sources I've also wondered how they will appear when posted
at RootsWeb's WorldConnect via gedcom. (I haven't tried it yet because of the
source repetition bug.) I wasn't expecting a perfect
]
To: LegacyUserGroup@legacyfamilytree.com
Subject: RE: [LegacyUG] V7 Sources: Nifty formatting lost in gedcom output
Date: Wed, 30 Jul 2008 10:17:56 -0700
Gail:
What a crushing disappointment! I don't have a website, but as I've worked
away at converting sources I've also wondered how
Ron:
Thanks for the encouraging report.
Kirsten
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of ronald
ferguson
Sent: Wednesday, July 30, 2008 11:26 AM
To: legacyusergroup@legacyfamilytree.com
Subject: RE: [LegacyUG] V7 Sources: Nifty formatting lost
Subject: Re: [LegacyUG] V7 Sources: Nifty formatting lost in gedcom output
I think Legacy's gedcom format is not the problem. It's just that a
gedcom file strips away all the formatting that Legacy uses to create
the nice EE-style citations. One example is that the US census
template asks
--and independent souls can continue to do
their own thing.
Kirsten
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of ronald
ferguson
Sent: Wednesday, July 30, 2008 1:20 PM
To: legacyusergroup@legacyfamilytree.com
Subject: RE: [LegacyUG] V7 Sources: Nifty formatting lost
] V7 Sources: Nifty formatting
lost in gedcom
output
Gail,
You may well be right. As I think you probably know,
I have little time for
prescribed or even proscribed formats, having only
one belief, and that is
that the sourcing must be clear and reproducible.
Even so I have tried out
13 matches
Mail list logo
