I did some experimenting in PAF and found that PAF does not have a double dating function like Legacy. Legacy uses a specific format and will modify a user entered date to add double dating in the form 1 Jan 1654/5 if a user has double dating turned on and is entering a date between 1 Jan and 25 Mar in those years when
Since PAF has no function to change a double date to a recognizable format each user is free to enter double dates in any fashion they choose. Without a standardized date format to look for when importing data from PAF it is impossible to know how to change a date into the Legacy double date format. I could find nothing in the PAF help about dates that even mentions the double date convention let alone a recommendation on how users should enter those dates where double dating is a possibility. That may be why this problem report about converting double dates from PAF has been on our list for as long as it has. Brian Customer Support Millennia Corporation [email protected] http://www.LegacyFamilyTree.com -- On 25/07/2013 9:36 AM, Brian/Support wrote: > That is, unfortunately a known problem when importing double dates from > PAF. I have sent a reminder to the programmers that this issue is still > outstanding. > > Brian > Customer Support > Millennia Corporation > [email protected] > http://www.LegacyFamilyTree.com > -- > > On 25/07/2013 3:52 AM, Robert Sterry wrote: >> Following Family Search's recent announcement that support for PAF is >> ending, I have decided to move from using PAF to Legacy as my main family >> tree program. >> >> This is my first post to the Legacy User Group. >> >> After importing my PAF files into Legacy I notice that double dates appear >> as, for example, '2 Feb 1632-2 Feb 1633' rather than '2 Feb 1632/1633'. >> >> Is there any way of customising the way the double dates appear? Personally >> I prefer the more compact format. >> >> With thanks >> >> Robert Sterry >> >> >> >> >> >> >> Legacy User Group guidelines: >> http://www.LegacyFamilyTree.com/Etiquette.asp >> Archived messages after Nov. 21 2009: >> http://www.mail-archive.com/[email protected]/ >> Archived messages from old mail server - before Nov. 21 2009: >> http://www.mail-archive.com/[email protected]/ >> 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 >> >> >> . >> > > > > Legacy User Group guidelines: > http://www.LegacyFamilyTree.com/Etiquette.asp > Archived messages after Nov. 21 2009: > http://www.mail-archive.com/[email protected]/ > Archived messages from old mail server - before Nov. 21 2009: > http://www.mail-archive.com/[email protected]/ > 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 > > > Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ 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
