On Mon, 5 Sep 2011 11:10:20 -0400, Ward Walker wnkwal...@rogers.com
wrote:
- during the export process, internally format each SourceWriter source
citation as it would appear in a Legacy report;
- output that formatted result as a block in the source detail, in the
GEDCOM file.
They should
As I have mentioned before, I think Millennia could be proactive in
implementing a workaround to this problem. I wonder if any competitors are
doing this? Here is my suggestion:
- during the export process, internally format each SourceWriter source
citation as it would appear in a Legacy
There are people working on a solution to this problem. Check out the
following
URL :http://bettergedcom.wikispaces.com/
TITLE : BetterGedcom - Build a Better GEDCOM Project
DESCRIPTION : The organizers of BetterGEDCOM are members of the genealogy user
community not affiliated with any
On 2011/09/05 17:15, Laura Johnson wrote:
There are people working on a solution to this problem. Check out the
following
BUT! (Big But) This won't get anywhere unless the big players become involved.
--
Regards,
Mike Fry
Johannesburg
Legacy User Group guidelines:
self-interest, as it makes it more difficult for people
to switch from one database program to another.
Ron Ferguson
http://www.fergys.co.uk/
-Original Message-
From: Laura Johnson
Sent: Monday, September 05, 2011 4:15 PM
To: LegacyUserGroup@LegacyUsers.com
Subject: Re: [LegacyUG] GEDCOM
Sourewriter
sources from Legacy properly.
Alan Pereira
-Original Message-
From: Ron Ferguson [mailto:ronfergy@tiscali.co.uk]
Sent: 05 September 2011 16:54
To: LegacyUserGroup@LegacyUsers.com
Subject: Re: [LegacyUG] GEDCOM Issue
Laura,
I wouldn't hold my breath. The organisers/designers
6 matches
Mail list logo
