Sherry,
This is incorrect. Initial Caps does not change what you type. If you
type it correct the first time it gets saved as you type it.
Even clicking Apply button doesn't change what it can figure out. For
example:
I select the options Initial Caps. I then edit a person and type in:
Surprise, , AZ (If I type it exactly like this it stays this way and
is saved in the master location list this way)
If I typed:
surprise, , az (and tab out of the field and if this location doesn't
already exist in my master location list I end up with)
Surprise, , AZ (Legacy is pretty smart. We know a lot of
abbreviations. Yes, there may be some we can't figure out but for the most
part it simply works).
The above example are even with the option set for Initial Caps.
But, if I type something in as mixed case Legacy feels the user knows what
they are doing so never changes what they type. For example:
SuRpRiSe, , aZ (when tab out of the field and if this location "surprise,
, az" is not allready in my master location list as a saved item then
Legacy keeps the exact text you typed in even if the option of Initial Caps
is set.
This exact text is saved as a new master location list.
"SuRpRiSe, , aZ"
This is because the user typed it in mixed case. So, no matter what
setting I have it keeps it this way.
Duvall, , WA, usa (will stay formatted as I typed it and will be saved as)
Duvall, , WA, usa
That's because I entered it in mixed case.
redmond, , wa, usa (will be formatted and saved as) Redmond, , WA, USA
This is because I entered it all in lowercase letters. So, Legacy uses the
rules and reformats it with initial caps but is smart enough to keep things
it knows like wa shoudl be WA and usa should be USA
I don't recommend turning off Initial Caps setting. It's way faster to
just type the whole location in lowercase letters and let Legacy do it's
job on it. If I do have a location I want entered in some special way then
sure, type it how I want it and if it's mixed case Legacy leaves it a
lone.
Things work the same way with the other fields like given names, etc.
So, let's say I did type something wrong or for some reason the logic
Legacy uses isn't smart enough to format it how it really should be. No
problem, just click the down arrow to the right of the location that is
formatted wrong and this opens the master location list. From here click
on Edit and change it to be how you want it to appear.
For exampel if init caps is on for Surnames and I enter this:
laporte (it becomes) Laporte
If I wanted it to be LaPorte just click the blue down arrow to the right of
the surname field and then click Edit on the Master Surname list and change
the lower case p to be an upper case P and click Save.
If I entered:
mcginnis (it becomes ) McGinnis (wow, isn't Legacy smart?)
The Init caps option is very smart and will try to follow a bunch of rules
we have built in.
But, hey, if you didn't want McGinnis just click the blue arrow, then edit,
change it to Mcginnis and click Save.
Play with it. Open a new empty file and practice a bunch with it. Legacy
is great how it handles things.
Thanks,
Ken McGinnis Millennia Corporation kenmcgin...@legacyfamilytree.com
http://www.LegacyFamilyTree.com We are changing the world of genealogy!
----------------------------------------
From: "Sherry/Support" <she...@legacyfamilytree.com>
Sent: Wednesday, December 18, 2013 10:30 AM
To: LegacyUserGroup@LegacyUsers.com
Subject: Re: [LegacyUG] Lack of Trust
If you have "Initial Caps" selected for location, then the country
will change to Us or Ca or whatever it is.
The first thing I do when I install Legacy is to go to Options and
select "Don't Change What I Enter"
And yes, there is a valid point with the default being Initial Caps.
I personally think "Don't Change What I Enter" should be the default,
otherwise mixed case names and locations will also get changed
(O'Brien to O'brien and LaPorte to Laporte). That would also prevent
changes to Initial Caps when importing a gedcom.
But the change is based on the option setting and nothing else. Legacy
doesn't think you entered something wrong.....
Sincerely,
Sherry
Technical Support
Legacy Family Tree
On Wed, Dec 18, 2013 at 9:22 AM, R G Strong-genes
<rgstrongge...@gmail.com> wrote:
> Everyone is assuming he has an upgraded program, however, I believe he
is
> still using version 5. And also his main complaint was the changing of
the
> letter case of country abbreviations that he uses. Could it be the change
in
> letter case could be that these are not standard Abbreviations and that
is
> why the case changes?
>
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 mail server - before Nov. 21 2009:
http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
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/legacyusergroup@legacyusers.com/
Archived messages from old mail server - before Nov. 21 2009:
http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
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
