Kathy, you're right, I can attach a Word document as a multimedia file to each
name explaining the diacritical situation and giving the correct names (meaning
with diacriticals)for each surname, given name and location, especially all the
AKAs, different ways the names were spelled. I hadn't tho
FamilySearch is trying to standardize things, for obvious reasons, but I
don't think they intend to impose that standard on any other programs or
services. They are not trying to change genealogical standards; they are
using set standardized locations so when you have someone in Chicago, it is
rec
Personally, I hope that Legacy never becomes so rigid that we won't have the
option to ignore standards if that is our wish or need.
-Original Message-
From: Kirsten Bowman [mailto:vik...@rvi.net]
Sent: Tuesday, June 14, 2011 9:31 PM
To: LegacyUserGroup@LegacyUsers.com
Subject: RE: [Lega
There's no question that genealogical practice recommends using the name of the
place as it was at the time of the event (and in the language of the place, if
you want to go that far). I'm just wondering how that and other location
issues that Legacy allows will integrate with FamilySearch's g
On Tue, 14 Jun 2011 16:31:25 -0700, "Kay Fordham"
wrote:
>Twould be great to have an option
>to use just the city or whatever after the second location incidence.
Or use the long location name the first time it is mentioned for a
person and the short name thereafter?
--
Dennis Kowallek (LTools
Hi Dan,
One of my "Mothers" had me put "Unnamed" rather than none or unknown.
Julie McNeice
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 ma
Thanks, Dennis. That is what I thought, and I do not wish to edit hundreds
(thousands?) of locations in RTF format. Twould be great to have an option
to use just the city or whatever after the second location incidence. Will
indeed make a suggestion.
Kay F
- Original Message -
From: "Denn
On Tue, 14 Jun 2011 15:53:53 -0700, "Kay Fordham"
wrote:
>Is there a way to preclude seeing repetitive locations in reports, such as
>he was born in Faulkton, Faulk County, South Dakota - was married in
>Faulkton, Faulk County, South Dakota - died in Faulkton, Faulk County, South
>Dakota - over a
Legacy 7.5.0.77, April 2011
Is there a way to preclude seeing repetitive locations in reports, such as
he was born in Faulkton, Faulk County, South Dakota - was married in
Faulkton, Faulk County, South Dakota - died in Faulkton, Faulk County, South
Dakota - over and over again for one individual?
I always put the location as it was at the time of the event. I realize that
in Europe places has really changed. My biggest ones are pre-Revolutionary War
in the US and in Europe Prussia vs. Germany vs. Poland
michele
From: Gene Adams
Sent: Tuesday, June 14, 2011 5:35 PM
To: LegacyUserGroup
Since the records will reflect original (old) names, that is what I use. If I
know that there are new names/locations I will put that information in a note.
I do this with many entries, as the cities come and go, Counties, State lines
and territories disappear and change. The Countries are not
Which brings up another issue. When you get back far enough, which is the
better means of identifying locations? The current "modern" standard location
as known today, or do you identify the location as it was known at the time of
the ancestor. What is the correct identity to be used?
You c
Which, of course, Michele, will give you an incorrect location for most of
the countries in the UK and much of Europe. In the American 4 field
convention, a space means that part of the location is missing. If that part
does not exist, and never has existed, then it will give the wrong message
to a
I agree. Even if you use the "Add Clipboard Source to all Used Fields and Events" button, it shouldn't add a clipboard source to empty fields.-Original Message-
From: cranberryf...@cobridge.tv
Sent: Jun 14, 2011 1:50 PM
To: LegacyUserGroup@LegacyUsers.com
Subject: Re: [LegacyUG] This is do
Hm, I suppose that is possible because I do exactly as you say. I will
pull up a similar source and edit. The only thing, since this is a just a book
I don’t think I would have done it that way since it is simple to do as a new
source but I certainly won’t rule it out.
michele
From: Don
With foreign countries, I still use the same 4 place holders but just leave
the parts blank that don't apply.
Michele
Legacy User Group guidelines:
http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages after Nov. 21 2009:
http://www.mail-archive.com/legacyusergroup@legacyusers.com/
Ar
However, they still wouldn’t explain why the source showed up in every spot
possible on each individual.
michele
From: cranberryf...@cobridge.tv
Sent: Tuesday, June 14, 2011 2:43 PM
To: LegacyUserGroup@LegacyUsers.com
Subject: Re: [LegacyUG] This is downright STRANGE!
Hm, I suppose that is
As a non LDS Volunteer I came across the standardisation of locations very
early on. I am based in the UK and most of my genealogical events are in the
UK.
When placing locations into nFS it is possible to enter the location you have
in your Legacy file and ignore the standardisation process.
I
Michele, You may want to revisit the 67 other people.
When I create a new Master Source, I often Edit an existing source (in an
attempt to get some consistency) and when I Save I get the option to apply the
changes to ALL references to the source or apply to a NEW source entry. If you
did thi
I certainly agree with Michele's comments. I also watched the webinars but
they raised more questions than answers, especially regarding locations. There
seem to be standardized LDS locations. How does that work with, say, Upper
Canada or Canada West (now Ontario), or American colonies like
I was wrong. There were 73 people linked to this source. I just deleted the
source and all of the citations and I will resource the 6 people.
michele
From: cranberryf...@cobridge.tv
Sent: Tuesday, June 14, 2011 1:44 PM
To: LegacyUserGroup@LegacyUsers.com
Subject: [LegacyUG] This is downright
I was working on a new line about a week ago. I was using this source...
Edgar C. Emerson, editor, Our County And It's People. A Descriptive Work on
Jefferson County, New York (Boston, MA: The Boston History Company, 1898),
905-906.
I was only working with a family group of 6 people. Today I
Second the motion
Gene A
From: "cranberryf...@cobridge.tv"
To: LegacyUserGroup@LegacyUsers.com
Sent: Tuesday, June 14, 2011 4:11 AM
Subject: [LegacyUG] webinar comment
Yesterday I watched two of the Webinars,
Improving Your Use of New FamilySearch: Data Cleanup
Yesterday I watched two of the Webinars,
Improving Your Use of New FamilySearch: Data Cleanup Strategies
New FamilySearch Made Easy with Legacy Family Tree
I am not LDS but I am looking forward to them opening up FamilySearch to the
rest of us and I want to be ready for it by getting my file clean
I am looking for a product to migrate to from PAF. I imported my file into
Legacy and noticed that all the Polish national characters except ó had been
skipped in the process. I joined this group for the purpose of asking this
single question about a work-around for the problem. Having read the
Word does accept these characters. Any attempt to paste them into Legacy
results in a “?” instead of the pasted character. Legacy seems to be in the
minority of software not supporting these characters.
Alan
From: Ron Ferguson [mailto:ronfergy@tiscali.co.uk]
Sent: 14 June 2011 10:20
To:
Kathy,
I cannot speak for WORD as I use OpenOffice.org, however it should be possible
to set the coding to UTF8 and then use Search and Replace to change the names
in question. I doubt if it would do this automatically.
Ron Ferguson
http://www.fergys.co.uk/
From: Kathy Meyer
Sent: Tuesday, Ju
27 matches
Mail list logo
