while allowing searchbar to find alt and primary names
related to
Issue #9276
while allowing searchbar to find alt and primary names.
Currently, the Place View and Place Selector name column shows a comma separated list of the primary and alt names for a place. With the advent of GeoNames and Gov data, the alt names lists are getting populated with (sometimes long) lists of (sometimes duplicated) names. This doesn't look very good in the view. I've gotten a couple of email complaints about this.
The Name column was originally extended (for Gramps50) to include alt names to allow the use of the top search bar (enabled when sidebar is turned off via 'View/Sidebar'), to perform a search through all the alt names as well as primary name. https://gramps-project.org/bugs/view.php?id=9276
This PR creates a new (hidden) column in the place model containing the full name list, and reverts the 'Name' column to the primary name. It also modifies the PlaceSelector and PlaceView classes to cause the search bar to use the new (hidden) column.
* Narrative Web : thumbnails bad alignment.
Fixes#10854
also solves the following problems in the Nebraska style sheet :
1 - float parameter has no value "center"
2 - "[" instead of ";" at end of line 1100
* overlapping with long titles
Use recent-export-dir as default for Export View
instead of the console default directory, which can be where
program resides (on Windows), or other inappropriate place.
Use USER_HOME for default directory on 'Export' (recent-export-dir)
if first run (default settings) rather than default directory, which
can be where program resides (on Windows), or other inappropriate
place.
Use USER_HOME for default directory on 'Import' (recent-import-dir)
if first run (default settings) rather than recent file which is
generally set to the grampsdb path.
Fixes#10802
The Descendant Fan chart had several bugs:
1) a bug that affected the centering of the chart for these modes
2) the chart was drawn in the wrong quadrant
3) the centering of the chart for printing was incorrect
(the legend was off the page some of the time).
4) the sizing of the chart for printing was incorrect
(for very small charts of one generation, the legend would
overwrite the chart).
The Fan Chart for the quadrant view:
1) the centering of the chart for printing was incorrect
(the legend was off the page some of the time).
Fixes#10817
Fixed some issues in the Dutch relationship calculator and also
extended the ordinal and removed lists till 50, just like the
English lists.
* Replaced huge lists by reusable lists.
* Fixed bug in which uncles/aunts, nephews/nieces (niblings),
siblings and cousins with an unknown gender show up as female.
* Fixed some misspellings:
drieëntwingste > drieëntwinTIgste
vierentwingste > vierentwinTIgste
edelovergrootOUD > edelovergroot
edeloudvergroot > edeloudOvergroot
Space between place, description and the event note when there are
many sources.
Change the css order between print and screen.
The chosen theme can erase prior values.
Add a width for the source column in all themes.
Fixes#10810
With this commit, two more reports now show a year as an
ordinal number in Croatian, and a year I missed before in
webcal.py is now fixed.
This commit also reverts the Croatian ordinal year fix in
the gramps50 statisticschart.py since upon reflection I
feel it would be better done in master, since then our
translators will have until 5.1.0 is released to do the
two new strings the fix requires.
Issue #10822
I ran gramps with a fresh copy of the example.gramps tree,
then ran the Complete Individual report. The options which
matter are "Entire Database" and "Include Notes" but I also
included the gramps-ID since that speeds up my work.
Then I noticed that hundreds of names at the end of the
output file all had the same note (N0001), whose text said
it referred to a specific person.
So I looked higher and the note inclusion started with I0044,
the default person. It was real for him but not for the next
person after him, or all the people after her.
I introduced the problem when I fixed 10033, in d6a97cf90e.
Note that this bug is independent of the CIR fix in p.r. 676
and still happens even after that pull request is applied.
