Robert,
I prefer to just use the very short form of the name, in your case just Miami,
as my experience upto now is that the people I gave reports to knew of what
places we were talking about.
For the others I include the complete name as in my case I have eg. three places
called Zell in a radius of 30 km. and there are another 6 in the radius of 100
km.
Depending on ones roots it's difficult to have a golden rule for a short name.
Eg. an ancestor was born in
Nußdorf(Orzechówko), Kreis Briesen(Wabrzezno), Westpommern,
Deutschland(Polska)
For the short I use:
Nußdorf(Orzechówko)
as my relatives know that it's in Poland.
As can be seen, I'm fighting with several problems.
The languages and the history. Prior to 1946 this area was German and since then
it's Polish.
Not only I have this problem as the continental Europe has so many changes in
the last hundreds of years that's it's very difficult to keep track of the names
of places and there locations.
My best sollution is to use the old name and in brackets the present name with
its geographical data.
As Legacy doesn't support UNICODE I will have to edit many Polish name at least
a second time.
Bernhard
________________________________
From: Robert E. Carneal [mailto:[email protected]]
Sent: Saturday, October 22, 2011 3:07 AM
To: [email protected]
Subject: Re: [LegacyUG] Showing Short Location Names on Screens
Here are what I use for long and short names.
Long:
Miami, Miami-Dade County, Florida, United States
Short:
Miami, Fl.
Robert
On Fri, Oct 21, 2011 at 6:58 PM, M. Brenzel <[email protected]> wrote:
Ron,
Yes, that's how I have started to change them. I wanted to
experiment first so I updated only a handful of my locations. Looking back in
the Archives, I see a message from Jenny about this earlier today. Thats what
she said she is doing.
Can you provide an example of what you have for long and short names?
Thanks!
Mary
-----Original Message-----
From: Ron Ferguson [mailto:[email protected]
<mailto:[email protected]> ]
Sent: Friday, October 21, 2011 5:23 PM
To: [email protected]
Subject: Re: [LegacyUG] Showing Short Location Names on Screens
Mary,
Are you long name and short name examples correct? I only ask because it
is
not the way I do it, not because there is anything particularly wrong
with
it - just looks a bit strange to me!
The Help Files are clear that the long name will always be used on the
Information Screens - when you think about it, it has to be so, because
that
is where the long name is entered.
Ron Ferguson
http://www.fergys.co.uk/
-----Original Message-----
From: M. Brenzel
Sent: Friday, October 21, 2011 9:23 PM
To: [email protected]
Subject: [LegacyUG] Showing Short Location Names on Screens
I think that I have found a bug. Either that or my interpretation of
the
effect is incorrect.
Has anyone else set the option for "Short Location Names on Screens" on
the
Customize View tab? It isn't working the way that I thought it would.
As others do, I do not use the "4 field" format for locations. My
locations
contain the full address including names of churches, cemeteries, etc.
Some
users have suggested separating the number portion of a street address
from
the street name itself in order to improve sorting by keeping streets
together. I sort my location list right to left.
For example, I have the following set for 123 Main Street, City, County,
State, Country:
Long name = 123, Main Street, City, County, State, Country
Short name = 123 Main Street, City, County, State, Country
I have done that but I don't like the way that it looks on the Legacy
screens.
Family and Chronology views are good. The short location name is
displayed.
Individual's Information and Marriage Information screens show the long
name
in the vital info and events/facts sections.
I suspect that I still see the location long names because those screens
allow for the selection of the location so it displays the long names,
whereas the other screens are display only.
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
--
Thank you.
Robert
Genealogy without documentation is mythology! Always SOURCE your work.
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
