I followed the advice of David (see the linked idea) and created this idea.
In the Slavic group of languages for the name of the person using a 3 ID: Surname (family name), First name and Patronymic.
First name - for centuries (and some thousands of years) they do not change, can be added from other languages, but this happens very rarely, that is, the list can be called fixed.
Surname (Lastname) - most often it is a derivative of the activity, which in past centuries dealt with this family or any feature inherent in this family. That is the name of remembering in the first place, if you need someone to find, because coincidence the last name (within the organization) is very rare.
Patronymic ("Middlename") - is derived from the name of the father.
Surname, name and patronymic confusion is impossible, they are always clearly distinguishable. Therefore, the commas in the format name was never used.
There are 2 kinds of First name: the full (official) and short (used in daily life people who are close). For example, my full name Vladislav, short - Vlad, and so on...
Valid in the official world or in the appeal junior to senior is considered: Firstnamefull Middlename.
Official name format post-Soviet countries:
For registrations, declarations, powers of attorney (where a need for full identification) uses the format:
Lastname<space>Firstnamefull<space>Middlename, authorities have a comma is added year of birth.
In other documents (especially internal) instead of Firstname and Middlename use their first symbols, ie, the format looks like this:
Lastname<space>F.<space>M. or Lastname<space>F.M.
By signing the documents used this format:
F.M.<space>Lastname or F.<space>M.<space>Lastname
For the signature of informal letters using the format:
Those who know the functional Lotus Notes (@UserName, @Name, etc.), imagine thousands of programmers in the Views, Computed text, and other, constantly engaged in turning names using the @Left, @Right or @Explode. In addition, it is terribly inconvenient, it increases the formula and makes it difficult building indexes...
In the @Name is missing a few [action] for formats:
First name<space>Lastname (without Middlename)
As for templates mailbox and address books, they also have to be corrected under the desired format (to remove the commas, turning names...) keep up templates with new releases is very difficult, as developer have to do the job again manually or abandon the new templates...
I see this solution:
1. Add missing [action] in the @Name.
2. Add an option to format name in the address book and CalendarProfile mailbox corresponding function @Name, then in the submissions would be enough to write @Name(@GetProfileField("CalendarProfile"; ActionFieldname); PersonName).
This solution would be flexible, versatile and would satisfy the needs of a variety of international formats.