Ward, Notwithstanding my comments in earlier posts I have wondered the same myself, it would seem sensible to me for not to break in mid-word to be the default. I have never got round to suggesting this, but as I always check the box it would remove the chance of me forgetting!
Ron Ferguson _____________________________________________________________________ Tutorials: Programme of adding videos commenced http://www.fergys.co.uk/ View the Grimshaw Family Tree at: http://www.fergys.co.uk/Grimshaw/ For The Fergusons of N.W. England See: http://myweb.tiscali.co.uk/fergys/ _____________________________________________________________________ ---------------------------------------- > From: wnkwal...@rogers.com > To: LegacyUserGroup@legacyfamilytree.com > Subject: Re: [LegacyUG] > Date: Mon, 6 Jul 2009 16:39:26 -0400 > > Ron, > > Sorry for the late reply. I was away. > > The short answer is no. I had not checked that checkbox option, so the > export broke lines in mid-word, as expected. For most types of GEDCOM > records, the import properly reconstructed those broken words. For the > 'PAGE' record type, the import improperly inserted a space. > > Thanks for pointing this out, though. I imagine that there is no harm in > choosing the 'old style' export, which works around the import bug (in case > other software products have the same bug). I wonder why it is old style, > and why it is not the default? The difference in file size is trivial. > > Ward > > ----- Original Message ----- > From: "ronald ferguson" > To: > Sent: Thursday, July 02, 2009 2:08 PM > Subject: RE: [LegacyUG] > > > > Ward, > > Are you saying that the export option to "Break between words (old style)" > doesn't work? > > Ron Ferguson > > ---------------------------------------- >> From: wnkwal...@rogers.com >> To: LegacyUserGroup@legacyfamilytree.com >> Subject: Re: [LegacyUG] >> Date: Thu, 2 Jul 2009 13:46:13 -0400 >> >> The extra space appears to be a bug on the import, not on the export. When >> a >> GEDCOM 'PAGE' record is long enough to have a continuation record, Legacy >> is >> not concatenating the 2 lines properly, introducing a space. Here are the >> GEDCOM lines corresponding to my previous example, where the word 'family' >> became 'fami ly' in the imported source detail. >> >> 3 PAGE M432, roll M432_699, Wayne Twp, p. 145, dwelling 2091, fami >> 4 CONC ly 2194, Margaret Jones age 8, accessed 2 Aug 2008 >> >> Other concatenations are working correctly, such as for the 'NOTE' field. >> >> Ward >> >> ----- Original Message ----- >> From: "Ward Walker" >> To: >> Sent: Thursday, July 02, 2009 11:37 AM >> Subject: Re: [LegacyUG] >> >> >>> Ross, >>> >>> This is what I was getting at in my (admittedly long-winded) posts titled >>> "Incomplete Export of Source Details" last week. The source detail info >>> from the first tab all gets strung together into one field in the GEDCOM. >>> Upon re-import, Legacy probably has no choice but to create a Basic style >>> source from it. The effect is that some citations will read quite >>> differently, as I showed in my example. >>> >>> As for the extra spaces, I didn't look closely at the pattern, but I do >>> recall noticing some unwanted spaces at the time. In fact, my example >>> shows the word "family" broken in two. >>> >>> Ward >>> >>> ----- Original Message ----- >>> From: "Ross Chapman" >>> To: >>> Sent: Thursday, July 02, 2009 7:46 AM >>> Subject: RE: [LegacyUG] >>> >>> >>>>I normally do transfer via the backup... this time the GeDCom file was >>>> already created for an upload to my web page so decided to use it >>>> instead. I >>>> have already replaced the file with a backup from my pc so there is no >>>> issue >>>> there. However it also shows me that the data I have passed on to family >>>> members may have issues as they don't use Legacy but PAF and FTM. >>>> >>>> Ross P. Allan Chapman >>>> Toronto, Ontario, Canada >>>> ross.chap...@rogers.com >>>> >>>> Visit my genealogy web page at http://rossallanchapman.tribalpages.com >>>> (major work in progress) >>>> >>>> >>>> -----Original Message----- >>>> From: k...@legacyfamilytree.com [mailto:k...@legacyfamilytree.com] On >>>> Behalf >>>> Of ronald ferguson >>>> Sent: July-02-09 2:19 AM >>>> To: legacyusergroup@legacyfamilytree.com >>>> Subject: RE: [LegacyUG] >>>> >>>> >>>> Ross, >>>> >>>> It may be that if you change the setting for Break notes between Words >>>> may >>>> help (Customise), but I do not know. >>>> >>>> However, why are you using a GEDCOM? I do similar, but because I have a >>>> non-Legacy program on my lap-top. If I was using Legacy then I would >>>> just >>>> transfer my .fdb file - or the zip back-up if I wanted the settings. >>>> >>>> >>>> Ron Ferguson >>>> >>>> >>>> ________________________________ >>>>> From: ross.chap...@rogers.com >>>>> To: LegacyUserGroup@legacyfamilytree.com >>>>> Subject: [LegacyUG] >>>>> Date: Wed, 1 Jul 2009 21:37:11 -0400 >>>>> >>>>> >>>>> >>>>> I exported a copy of my database into a GEDCom file for >>>>> transfer to my notebook and all the source citations were switched over >>>>> to >>>> the >>>>> Basic format. When it did that is started placing spaces in some of my >>>> data >>>>> i.e. splits in file numbers and the like. Any of you out there seen >>>>> this >>>> or >>>>> know of this issue? >>>>> >>>>> >>>>> Ross P. Allan Chapman > _________________________________________________________________ Share your photos with Windows Live Photos – Free. http://clk.atdmt.com/UKM/go/134665338/direct/01/ 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
