This problem has been identified and fixed in Families Sync 1.2.2 which has
just been released.
Malcolm Green
-Original Message-
From: Sherry/Support [mailto:she...@legacyfamilytree.com]
Sent: 09 November 2011 17:01
To: LegacyUserGroup@LegacyUsers.com
Subject: Re: [LegacyUG] Individual
The original problem, which was fixed in 1.2.0, was that lines were being run
together because of the difference in how iOS and Windows handle newlines.
Unfortunately this introduced the current problem of extra lines, due to
multiple carriage return characters being inserted in some cases.
On Fri, 11 Nov 2011 11:42:11 -, Malcolm Green
malc...@telgen.co.uk wrote:
As far as I'm aware, this only affects reports; when editing notes etc. in
Legacy, the text appears correct, which is why I wasn't aware of the problem
until now.
Malcolm,
In the file I repaired I could see the
In the upper left of the expand/contract location parts screen you have
to tell Legacy what action to take. The default is to expand the long
location name parts and contract the short location name parts. Also
check which records are to be affected. The default is all locations but
if only tagged
Hi Brian. I'm in agreement with you that it is better to use the four
divisions that Legacy recommends. However, is it not true that a person
(if so desired) can use up to nine divisions in the place names,
separated by commas and still perform proper sorting by using the RIGHT
to LEFT sort?
Yes, Legacy does handle up to nine comma separated levels but there are
certain routines, and the expand contract is one of them, that assume
that only four levels are used. With the levels being city, county,
state and country.
By the way I did not say it is better to use four levels only that
Got it - thanks!
Jerry - MerriamFamilyTree.org
On 11/11/2011 5:01 PM, Brian/Support wrote:
Yes, Legacy does handle up to nine comma separated levels but there are
certain routines, and the expand contract is one of them, that assume
that only four levels are used. With the levels being city,
This is why I am trying to correct my location master list. I want it to do
the things it will do if it is correct. I do not understand the location
name parts statements. If I am trying to get everything in my list to fit
with what Legacy recommends, is there one of these I should check? Do you
*Where do we comment? Here on the LUG?
**Thank you.
**Robert*
*Genealogy without documentation is mythology! Always SOURCE your work.*
On Fri, Nov 11, 2011 at 3:49 PM, Geoff Rasmussen ge...@legacyusers.comwrote:
Marian Pierre-Louis is looking for any words of encouragement on getting
I would say the repository is you in this instance, because you have the copy
of the email (either a paper version or stored on your computer.)
Cheers
Jan
-Original Message-
From: Jerry [mailto:jerrysemailgro...@gmail.com]
Sent: Friday, 11 November 2011 05:21
To:
This is good news! Thank you so much. I'll download it and give it a try.
Mary
-Original Message-
From: Malcolm Green [mailto:malc...@telgen.co.uk]
Sent: Friday, November 11, 2011 6:33 AM
To: LegacyUserGroup@LegacyUsers.com
Cc: malcolmcgr...@googlemail.com
Subject: RE: [LegacyUG]
It's fixed! Thank you, Malcolm, for such a quick fix to the spacing problem!
Mary
-Original Message-
From: Malcolm Green [mailto:malc...@telgen.co.uk]
Sent: Friday, November 11, 2011 6:42 AM
To: LegacyUserGroup@LegacyUsers.com
Cc: malcolmcgr...@googlemail.com
Subject: RE: [LegacyUG]
*I noticed that. Clicking that didn't work for me, so I assumed this was a
work in progress. Did that button work for you?
**Thank you.
**Robert*
*Genealogy without documentation is mythology! Always SOURCE your work.*
On Fri, Nov 11, 2011 at 4:25 PM, Mark Lang markl...@adam.com.au wrote:
Maybe my approach is over-simplification...but the way I look at
repository is based on:
IF someone wanted to see the object of the source, WHERE could they find
it?
Answer: Is based upon WHERE you found it...i.e. in YOUR email...or in YOUR
conversation with the source of the information.
14 matches
Mail list logo
