This is very wise. Avoid confusion. Avoid abbreviations, USA could be United
States or Union of South Africa. Use appropriate names, enter place as it is
in the time period that the event takes place. Study up on genealogy standards
and practices.
Sent from my iPad
> On Aug 3, 2019, at 9:0
Yes, it is. CA is the abbreviation for both California and Canada, which
is why I always enter California or Canada instead of simply CA.
On Sat, Aug 3, 2019 at 9:23 PM Anne Hildrum wrote:
> Well isn't CA an Acronym.
>
>
>
> Ane
>
>
>
> *From:* LegacyUserGroup *On
> Behalf Of *Ian Macaulay
>
James,
It makes perfect sense. "New York" - is that New York City, New York
County, or New York State?
New York ,,,USA would be city
,New York ,,USA would be county
,,New York ,USA would be state
If you can tell which one someone meant by just entering "New York", you
need to play the lot
Well isn't CA an Acronym.
Ane
From: LegacyUserGroup On Behalf Of
Ian Macaulay
Sent: Saturday, August 3, 2019 10:51 PM
To: Legacy User Group
Subject: Re: [LegacyUG] Location names for Pennsylvania
I Live in CA, Not CaliforniaIMHO Acronyms are not proper English, and it
confuses
Actually, I use the full name for all locations. I am from Canada.
On Sat, Aug 3, 2019 at 9:00 PM Donna Newell wrote:
> Great answer!
>
> Sent from my iPad
>
> On Aug 3, 2019, at 3:50 PM, Ian Macaulay wrote:
>
> I Live in CA, Not CaliforniaIMHO Acronyms are not proper English, and
> it co
Great answer!
Sent from my iPad
> On Aug 3, 2019, at 3:50 PM, Ian Macaulay wrote:
>
> I Live in CA, Not CaliforniaIMHO Acronyms are not proper English, and it
> confuses your Neighbors.
>
>
>> On Sat, Aug 3, 2019 at 3:14 PM James G. Hermsen via LegacyUserGroup
>> wrote:
>> I never had
I Live in CA, Not CaliforniaIMHO Acronyms are not proper English, and
it confuses your Neighbors.
On Sat, Aug 3, 2019 at 3:14 PM James G. Hermsen via LegacyUserGroup <
legacyusergroup@legacyusers.com> wrote:
> I never had a Gedcom file not accept any location file whether it had
> Indianapol
I never had a Gedcom file not accept any location file whether it had
Indianapolis, Marion Co., IN, or even Indianapolis, IN. not to mention
Indianapolis, xxx Township, Marion County, Indiana, United States of America.
You soon get the point that the latter is the creation of someone who thinks
What does not make sense is seeing something like: , , , Indiana, United
States of America. when a simple IN would do. Or: , , , Berlin, Democratic
Republic of Germany. You can find whatever available record in Berlin today
regardless if it was Prussia, Imperial Germany, Natzi Germany, East
Below is an example for the city of Charlesbourg that was merged with Quebec
City. (Note: the numbers in the second field correspond to the unique code that
identifies the city of Quebec – not essential but useful for locations with the
same name but from different areas)
Charlesbourg {Québ
Thanks for all the info & suggestions. I did not know about curley brackets
so that will be a great help.
Thank you everryone.
On Sat, Aug 3, 2019 at 9:43 AM wrote:
> Christopher
>
> I agree with you.
>
> My suggestion of putting the present name between curly brackets after the
> referenced lo
Christopher
I agree with you.
My suggestion of putting the present name between curly brackets after the
referenced location name is simply an easy way to translate old location name
into present day name and it is accepted by the different Gedcom programs.
Georges
De : LegacyUserGr
James, I understand where you're coming from. I just think that handling
data in a manner that deviates from the standard is inviting data integrity
issues. As I said, the choice is yours. Just be aware of the lasting
issues it will cause for those who come after.
Christopher
On Sat, Aug 3, 2019
Exactly my point. Putting historical location in the notes maintains all the
information one needs and still be sensible and useful to family members. If
people import information without looking at the notes, then they are not being
a good genealogist. It tells me that they just copy things
14 matches
Mail list logo