Gramps Web is an interesting way to access your genealogy database online. However, if you format patronymics as a variant of a personal name, then in Gramps Web, the First Name, Patronymic, Lastname is displayed as First Name, Last Name, Patronymic (like Ivan Sidorov Petrovich). In Gramps Desktop, everything is fine.
Gramps 6.0.8
Hi,
support for name formats is discussed here
offen 08:48PM - 22 May 24 UTC
Hi!
In my culture preferrable order of names looks like this:
```
<given na… me> <patronymic surname> <surname>
```
Or another order also possible:
```
<surname> <given name> <patronymic surname>
```
But in GrampsWeb another order of names is widely used:
```
<given name> <surname> <patronymic surname>
```
Or another possible order of such set of names in GrampsWeb:
```
<surname> <patronymic surname> <given name>
```
All these order existing in GrampsWeb are looks very strange and unusual in my culture.
Lets look at some examples.
List of persons (`https://<domain>/people`):
Info about concrete person (`https://<domain>/person/<person_id>`):
Ancestor tree and other types of trees (`https://<domain>/tree`):
Maybe some other views exists with same order of names unusual for my culture.
Desktop Gramps application has elegant way to solve this problem. It has setting for for custom name display format:
https://gramps-project.org/wiki/index.php/Gramps_5.2_Wiki_Manual_-_Settings#Display_Name_Editor
I can set it to desired value and after it order of names looks natively to my culture in all views I have found in desktop app. For example some screenshots from Desktop Gramps 5.2.2 after setting of custom name display format (sorry for screenshots from desktop app - they are in translation to my language, I can't find howto change translation to English in desktop app).
List of persons:
Info about concrete person:
Tree:
Please, implement ability to change default order of names in all views in GrampsWeb according to setting of custom name display format in GrampsWeb, just like works in desktop Gramps.
P.s.
Version of GrampsWeb where I created screenshots:
```
Gramps 5.2.2
Gramps Web API 2.3.0
Gramps Web Frontend 24.5.0
Gramps QL 0.3.0
locale: en
multi-tree: false
task queue: false
```
P.p.s. I have discussed this feature request at [gramps discourse group](https://gramps.discourse.group/t/is-it-possible-to-use-custom-name-display-formats-in-grampsweb/5495).
Also I found another feature request is very close to current: https://github.com/gramps-project/gramps-web/issues/411.
It is about ability to change names order from `Surname, FirstName` to `FirstName Surname` in tree, graph & Chart view.
I think, it is a part of current more generic feature request.
So, after discussion in [gramps discourse group](https://gramps.discourse.group/t/is-it-possible-to-use-custom-name-display-formats-in-grampsweb/5495) I decided to open this new feature request.
and some work was started here
master ← vktimofeev:name_display_branch
offen 08:38PM - 12 Aug 25 UTC
…, a "name_display" field to the person profile, and initialization code using g… ramps.gen.display.name displayer
main ← vktimofeev:name_display_branch
offen 11:59AM - 22 Aug 25 UTC
... instead of the join of profile.name_given and profile.name_surname/
This … is just a sketch code, however working good for me. It is a sort of "natural" solution to use the user defined format to display primary names instead of just concatenation of profile.name_given and profile.name_surname via a spacebar, as it is implemented in many places in the **main** branch now.
However such a solution is incomplete: for example, the names in the associations list are rendered from the serialized Person class instances
https://github.com/gramps-project/gramps-web/blob/31ed0bd98b8eec1b903f2215f91bcfaabcd7a97b/src/util.js#L45-L#53
and the Person class contains no `name_display` field which contained the primary name in the user defined format.
The serialized Person class instances are produced by the following backend code:
https://github.com/gramps-project/gramps-web-api/blob/fdb0d4b4157494994acc67572c8fc6312a12f06c/gramps_webapi/api/resources/util.py#L771-L774
...
https://github.com/gramps-project/gramps-web-api/blob/fdb0d4b4157494994acc67572c8fc6312a12f06c/gramps_webapi/api/resources/util.py#L809-L819
and the same code is used from src/components/GrampsjsSearchResultList.js
https://github.com/gramps-project/gramps-web/blob/31ed0bd98b8eec1b903f2215f91bcfaabcd7a97b/src/components/GrampsjsSearchResultList.js#L96-L101
via
https://github.com/gramps-project/gramps-web/blob/31ed0bd98b8eec1b903f2215f91bcfaabcd7a97b/src/util.js#L311-L314.
Couldn't we add, for example the person profile to the serialized Person class instances when they are returned in the REST API reply? The serialized Person class instances on the client side can contain additional fields to the server side instances, can't they?
but the frontend part wasn’t completed.
I won’t work on this myself as I don’t need it (selfish maintainer…) but I totally agree this is a needed feature and I’d be happy consult on the implementation if anyone wants to bring it to the finish line.