I think the general rules of thumb with naming a family tree are:
If you are the sole editor of the family tree and are building it for recording historical information about a certain linage, then you can safely name it based on the surname of the top ancestor.
If you are creating a family tree where multiple members can edit and expand, you can name it after several of the main family names, e.g., "McRae - Williamson - Kelly - ...."
If this is a family tree when many members share information, add photos and greet each other on birthdays and so on, I found it better, as you did, to just call the site "My Family" or "Our Family" or something of that nature so that everyone will feel welcome and not a marginal part of the family.
Thanks for the tip. That works if the maiden name is known and entered. If the maiden name is blank, FTB5 displays the married name, which is not what I wanted. (I believe FTB4 displayed a question mark, which made sense.)
I've found a klutsy workaround. I entered "<surname unknown> in the maiden name field. I don't like it. I think FTB should leave it blank if you set the last name to "maiden name" in the Names options.
Are you referring to the following situation: You did not enter the woman's maiden name and you HAVE entered her married name? In this case, FTB does show the married name since there is no maiden name to show at all. I guess you will need to manually enter "?" for the maiden name if you want to show this last name in this case.
Yes, Uri, that's the situation. I think this behavior is different in FTB5 because I used to see "?" there before. For those of us who want to work with maiden names and know when the maiden name is unknown, it's hard if FTB defaults to a married name instead of showing a blank or a "?". By the way, I tried to enter a "?" manually, but this seems to be a reserved character for FTB because it won't save it. Likewise, entering "unknown" doesn't work. I ended up having to enter something that FTB thinks is a real name, such as "<surname unknown>". Finally that worked.
I will make sure we will add a fix in the near future so that if you ask to show maiden names, and there is only a married name but not a maiden name, the last name will not show the married name but will rather show "?"
Tools > options > names > last name for married women = maiden name
Tools > options > names > empty last names = ?
It works for me!
CORRECTION: The above comment is not strictly true - I hadn't remembered that I had deleted married name using edit person which seems to solve it in FTM but once uploaded reverts to married name. The program does seem to have been 'broken' for unknown maiden name display.
Could I make a suggestion? I have found out the hard way that having "Unknown" for empty first, last & full names that when exported as a GEDCOM, that the record seems to disappear. I have had a couple of instances when the the file has been saved/updated that the record numbers go "crazy". an example is when there are, say, 750 names (including unknown) and FTB says there are 750 persons, when a new name is added, the next record ID is 1501, ie, double the number of persons plus 1. (also note when using the 'plus' sign in these forums that the symbol disappears when previewing before sending!) When this happens I export as GEDCOM to another program, then import back to FTB and the unknown entries are no longer there! As I rely on the ID numbers for publishing to my Web Site (NOT My Heritage as I have developed my own site), this is most annoying.
While I'm on that subject, what causes the ID numbers to do that?
If I list the names as NOT KNOWN for last name and Not Known for first name, this fixes the problem. Therefore in the Options --> Names could "Not Known" be added as well as 'blank' '?' '-' '---' and 'Unknown'?
I hope the development team would seriously consider adding 'Unknown to the list of defaults. Maybe ASAP.
Michael, if the "blank last name" is set to "?" and the woman's name is set to "maiden name" and the woman has no maiden name entered but a married name listed, FTB5 displays the married name. If that's not the behavior you're seeing, you might be using an older version of FTB (and what I hope will be the behavior of the next version of FTB!).