As noted before naming is a very difficult and problematic area. This is caused very often by the lack of consistant entry between software programs. Many programs do not support the same convensions as others.
1) I always follow the GEDCOM standard v5.5.1
2) I always enter the prefered name as known at birth unless not known.
4) I always enter an additional name tag for married names.
5) I NEVER use _AKA or aka because it is not valid GEDCOM
6) I always add additional NAME tags with TYPE subtags to describe the type of name (i.e. birth, married, aka, name change, stage name, etc) Not Support by FTM
7) I always enter the name as a person would spell and use it. For some names this means surname first then given name.
8) I always use the local alphabet (Scaninavian, Slavic, Left to Right,R2L) on the primary name, then add a second NAME tag for an English spelling.
9) I always enter separate names where the spelling could be different regarding immigration changes.
10) When a custom gives surname spelling based on gender I enter the gender based surname and use other GEDCOM tags to index these individuals together. Not supported by FTM
11) When custom gives multiple surnames based on father/mother surnames. For example in many countries the child will receive a surname from both thier father and mother then add (for females) a husband's surname. I enter these names based on custom. Not supported by FTM.
12) Where custom gives no surname I do not enter a surname.
the GEDCOM standard is not perfect regarding names. It does not support name based on location or clan. I have to work around this issue.