Python is an interpreter and therefore needs to create executable
memory. Since it doesn't know how to sign that memory it requires
the allow-unsigned-executable-memory entitlement to run in a hardened
runtime. One must apply this entitlement to both Gramps.app and
Gramps.app/Contents/MacOS/dot when codesigning them.
* Narrative web: some strings not translated
The confidence and the date are not translated in the family map page.
The date doesn't use the specified date format.
Fixes#11207
* Narrative web: another string to translate
* Narrative web: markers incorrectly placed.
In the map pages, the markers are not placed where it should be.
reproducible when zoom in/zoom out.
Fixes#11208
* Narrative web: background not correctly set.
If you use the Web_Basic-Cypress.css, the foreground and background
use the same color, so you see nothing.
you must hover the fields to see the text
* Narrative web: Sort problem with places.
Fixes#10868.
Places list is not sorted depending on the selected language.
If you start gramps in english or another language then try to generated
a narrative web report in another language, the navigation alphabet is
incorrect. This is true for the place list and the person list.
The problem was related to pyICU.
* Narrative web: some pylint improvement.
* Narrative web: Sort problem with places.
Fixes#10868.
Places list is not sorted depending on the selected language.
If you start gramps in english or another language then try to generated
a narrative web report in another language, the navigation alphabet is
incorrect. This is true for the place list and the person list.
The problem was related to pyICU.
* Narrative web: some pylint improvement.
The updated uimanager and managedwindow uses the plugin id to create actions for plugins that make a window to support the menus. If the plugin id contains a space, Gramps crashes.
Fixes#11202
If you click on a marker in the family map page, you get a popup.
In this popup associated with a place, if you have several events,
for each event you see the person and the event type.
If you click on the person, you go to the related page for this person.
If you click on the event type, you go to the related page for this event.
Fixes#11150
After asking the OSM support, I was told OSM forward all http request to
https when we use .org url.
So it should work in all cases.
This has an energy cost, so it would be good for the planet to change
http to https.
