OK, I'm confused.  I realize the GEDCOM standard is old, but it is
still the only method available for transferring data between
programs.  If the new SourceWriter data and ESM's templates do not
transfer well by gedcom, what is the alternative? Should we stop using
SW until a new gedcom standard is developed?  That may never happen
because as far as I know, LDS has no plans to update the gedcom.
Chick Lewis


On Tue, Aug 25, 2009 at 11:20 AM, Ward Walker<wnkwal...@rogers.com> wrote:
> Jeff,
>
> The thread addresses that as well. In fact, the thread started with an issue
> with Basic style sources. In short, if you have a mix of SourceWriter and
> Basic style sources, and if you place text in the Source Detail field of
> some Basic sources, and if you sometimes want that text in your citation and
> sometimes not, then there is a problem. (I ended up removing text from that
> field if it was only there as a comment and not to be in the citation.) I
> see this as a Legacy oversight and not a GEDCOM issue. Leaving the box
> "Override Source options - include all source information" UNchecked should
> only apply to Basic sources, not to SW sources (which always need the source
> details).
>
> Back to your original question about SW sources, Connie's reply explains it
> quite well. I expect that a more elaborate GEDCOM file standard is required,
> in order to deal with EE style citations.
>
>  Ward
>
> ----- Original Message ----- From: "jeffma...@orthohelp.com"
> <jeffma...@orthohelp.com>
> To: <LegacyUserGroup@legacyfamilytree.com>
> Sent: Tuesday, August 25, 2009 7:37 AM
> Subject: Re: [LegacyUG] combining/replacing sources
>
>
>> Thanks Ward.  I will look up the thread.
>>
>> How about the old style sources? Do they export correctly to other
>> programs and via gedcom?
>>
>> Jeff
>>
>> Ward Walker wrote:
>>>
>>> No, they will not transfer correctly, even back into Legacy. Yes,
>>> GEDCOM has difficulty.
>>>
>>> I mentioned this on-list only 8 days ago. For details, see my post in
>>> the archive on 25 June, titled 'Incomplete Export of Source Details'.
>>> Some types of sources will survive this process better than others,
>>> depending on how much the master and detail fields are interspersed.
>>>
>>>  Ward
>>>
>>> ----- Original Message -----
>>> From: "jeffma...@orthohelp.com" <jeffma...@orthohelp.com>
>>> To: <LegacyUserGroup@legacyfamilytree.com>
>>> Sent: Sunday, August 23, 2009 4:11 PM
>>> Subject: Re: [LegacyUG] combining/replacing sources
>>>
>>>
>>>> A question about the sources produced by the new source writer: will
>>>> they transfer correctly in a gedcom to another genealogy program? In
>>>> other words, does gedcom have any difficulty with the new style of
>>>> sources compared the to the older style?
>>>>
>>>> Thanks.  Jeff
>>>>
>>> ...
>>>
>>>
>>>
>>>
>>> Legacy User Group guidelines:
>>>  http://www.LegacyFamilyTree.com/Etiquette.asp
>>> Archived messages:
>>>  http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
>>> Online technical support: http://www.LegacyFamilyTree.com/Help.asp
>>> To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
>>
>>
>>
>>
>> Legacy User Group guidelines:
>> http://www.LegacyFamilyTree.com/Etiquette.asp
>> Archived messages:
>> http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
>> Online technical support: http://www.LegacyFamilyTree.com/Help.asp
>> To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
>>
>>
>>
>
>
>
>
> Legacy User Group guidelines:  http://www.LegacyFamilyTree.com/Etiquette.asp
> Archived messages:
>  http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
> Online technical support: http://www.LegacyFamilyTree.com/Help.asp
> To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
>
>
>
>



Legacy User Group guidelines:
   http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages:
   http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
Online technical support: http://www.LegacyFamilyTree.com/Help.asp
To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp



Reply via email to