Jay,
I think it will be a long time before we have a new interchange standard that
deals with these two features. To my thinking, whenever a software vendor
implements a proprietary new feature for data entry (and internal data
structure), they should implement a workaround for the export of the resulting
data. From day one. Why would I want to send to my distant cousins a GEDCOM for
which I have to apologize due to its garbled sources or missing events?
The Legacy import process already has a few workarounds to accommodate
non-standard quirks in GEDCOMs generated by other products. Why not workarounds
for the two export issues? They both sound achievable at a reasonable cost.
I’ve already gone down the SourceWriter road, but I can easily avoid shared
events until this happens. They are a nifty feature that is only half
implemented.
Ward
From: Jay 1FamilyTree
Sent: Thursday, December 05, 2013 2:23 PM
To: LegacyUserGroup@LegacyUsers.com
Subject: Re: Exporting Shared Events [WAS: Re: [LegacyUG] Shared vital Events]
Ward
When the standards for Gedcom were created way back when, this 'new feature'
wasn't even considered or even imagined.
Don't blame the software for it, blame the standards that haven't been updated.
Whatever browser you are using to read this email and view the web certainly
isnt following the standards of the HTML 3.0 which was the first widely used
and accepted standards for that category of electronic data.
As Kristy said, the issue is wit the gedcom.
Jay
On Thu, Dec 5, 2013 at 7:44 AM, Ward Walker <wnkwal...@rogers.com> wrote:
I agree, Gavin. To me, this is equivalent to the problem with SourceWriter
source citations. I have long advocated that Legacy reformat these into
readable detail citations during the process of converting them into Basic
sources for the GEDCOM export. It seems that Millennia does not believe that a
usable GEDCOM export is important.
Every proprietary new feature should have an option to be mashed into the
primitive GEDCOM standard without loss of data.
Ward
From: Gavin Nicholson
Sent: Wednesday, December 04, 2013 8:56 PM
To: LegacyUserGroup@LegacyUsers.com
Subject: RE: [LegacyUG] Shared vital Events
Thanks Kirsty,
Well I will be putting a change proposal in because it would be simple to
export a copy of the events to each person. Yes it won't be shared anymore but
that is far preferable to not existing at all. Essentially, with this as it is
you can't use shared events and then give your data to anyone who doesnt use
Legacy :-(
Thanks for making us aware of this one.
Gavin...
From: Kirsty M. Haining [mailto:khain...@comcast.net]
Sent: Thursday, 5 December 2013 11:48 AM
To: LegacyUserGroup@LegacyUsers.com
Subject: RE: [LegacyUG] Shared vital Events
Gavin, that is exactly what I’m saying. Using a gedcom export, the data shows
up ONLY under the event initiator’s dataset.
Keep in mind, however, that if you use Legacy to create your reports, charts,
sharing via PDF files, etc. then the shared events should appear properly
within the particular reports (according the report options you’ve chosen). The
issue is with gedcom export.*
cheers,
Kirsty
J
*Or, technically, the issue arises anytime you’re using another software
program to handle a Legacy file, be it gedcom or native FDB format.
Legacy User Group guidelines:
http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages after Nov. 21 2009:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/
Archived messages from old mail server - before Nov. 21 2009:
http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
Online technical support: http://www.LegacyFamilyTree.com/Help.asp
Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our
blog (http://news.LegacyFamilyTree.com).
To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
