* NAVWEB: set unused media to False by default
Fixes#11496
* Navweb: Center correctly the map in the web page
* Webcal: Dropmenu doesn't work if only one year.
* Navweb: Add notes to updates and delete empty rows
* Navweb: some code cleanup.
* Navweb: remove unused variable
* Narweb: references enhancement on place pages.
* Navweb: convert the years in gregorian cal.
* Narweb: remove unused argument
* Narweb: really solves the pyICU problem
* WEBCAL: missing death symbol
* Navweb: Don't use media regions in some case:
- If we don't show families
- If we don't show events
Fixes#011500
* Navweb: side effect between event and media pages
When a media is processed in the media display section for an event
page, it's remove from the media_list, so when we try to create the
media regions in the media page, the media list is empty and we
can't display the regions.
* Narweb: Don't show the regions for a thumbnail
When editing a Media image, Unknown is displayed if the image is a Tiff or Png. This changes this to display TIFF image or PNG image instead. Just a cosmetic change.
* Fix import file chooser filter to accept upper case extensions
Fixes#11463
* Allow import file filter to accept case insensitive extensions
Co-authored-by: Nick Hall <nick-h@gramps-project.org>
* Narrative: Don't use event links if no event pages
+ some pylint changes
* map popup links must be visible for all stylesheet
* Narrative web: add scrollbar in popup content
* Narweb: Some improvement in popup
* Narweb: remove unused variable.
* Narrative web: Some improvements
- Event type, Date and place in bold
- Family events shifted one column on the left
- ancestortree css file before narrative-screen to allow modification
- Adaptation for all themes
Fixes#11393
* Narrative web: forgot a comma during last merge
* Allow scrolling if the ancestor tree is too large
* Translation of alternate stylesheets name
* Crash when using the family map
* Translate only the css title, not the file name
* Some minor corrections to css files
* Narrative web: open layers optimizations
* Narrative web: open layers and link in popup
* Narrative web: some events missing in popup
* Narrative web: Reference date column too large.
Allow the place title to use the maximum of width
* NarrativeWeb: shift children from one column
- adapt the css files to the new table
- some inconsistencies between the source and the css
* Make the drop down menu button size usable
* NarrativeWeb: Incorrect rendering when use of
alternate place name
* NarWeb: removing the unused image heigth option
* Click on image link gives a not found URL.
If the image used in home, introduction or contact page
is not already associated by a filtered object, we have a 404 error
* NarWeb: Index images and thumbnails pages optional
* Narweb: Improper Notes subtitle in web pages
* Narweb: List index truncated after 999
* Narweb: NarrativeWeb usage enhancements
* Narweb: avoid duplicate files in archive.
* Narweb: Add an optional news and updates page:
When you have a big database and you make intensive updates, it's
useful to have a list of the last modified objects.
you can select the period to show and how many records to see per object type.
* Narweb: forgot to add the module updates.py
* Narweb: some minor changes (pylint, img index bug)
* Popups don't work with the last openlayers version
It only needs to move the scripts at the end of the html body.
Use addEventListener instead of onload in the html body statement.
* Narweb: some popup problems
* Narweb: better score for pylint
* WEBCAL: Have config files for multiple databases.
* WEBCAL: best management for the narrative web link
* WEBCAL: use arrows, compress monthname and arrows
adapt the css files accordingly
* WEBCAL: use arrows in one day within a year
compress monthname and arrows
adapt the css files accordingly
* WEBCAL: index go now to the current month.
before this patch, the default month for the year calendar
was the month found at the web calendar generation.
Now, even if you create this report 8 months ago, the current
index will point to the current month.
* WEBCAL: trailing space.
* WEBCAL: year glance + some pylint improvements
* WEBCAL: incorrect width size with Mainz css.
* WEBCAL: problem with Visually css file
* WEBCAL: The table cell is highlighted when hover.
* WEBCAL: better pylint score.
* WEBCAL: Better rendering for full yer at a glance
* WEBCAL: better rendering on small devices
* WEBCAL: better quality code
Fixes#10124
Fix up Event Editors Place display for bidi text with Gramps ID (PR 924)
Some versions of Gtk/Pango have trouble with text containing both LTR and RTL characters. The bug notes this shows up in our Event Editor on the 'Place" field, where we have the place displayer title and the Gramps ID concatenated into the same string.
In older versions of Gtk (3.18.9 tested) the bracket around the Gramps ID would get mangled to the beginning of the string:
<images>
In newer versions of Gtk (3.24.3 tested) it was better to start with:
<images>
The older version of Gtk/Pango doesn't seem to properly interpret all of the potential Unicode bidi control characters, so the fix shown is the best I can do. The fixed version of the newer Gtk version is what is desired.
I note that the Place displayer should be fixed up to use more appropriate separators than just commas for RTL text, but that is another issue.
Fixes#11410
The bug submitter noticed that the GEDCOM export contained translated strings in the MEDI lines of his export. GEDCOM should contain English values for most such cases where 'types' are exported.
I scanned the export code for other potential cases, and found:
* Certain unexpected event types on individuals (Marriage)
* Certain unexpected event types on families (Immigration, Residence, etc.)
* Pedigree types that were not standardized on PEDI,_FREL,_MREL (Sponsored, Unknown)
* Family Attributes other than Number if children (Caste, Description, National etc.)
* Personal Attributes other than Caste, Description, ID, National, number of children, SSN (Occupation etc.)
* The MEDI types of this bug report...
Fixes#10762
User "petpil" (Gramps Bugtracker) noted that the Calculate Estimated Dates addon would not expand the size of its window content when the window was stretched. That addon used the ToolManagedWindowBatch which uses a Gtk Notebook to support several tabs. He also submitted a patch which fixes the problem.
The Gtk.Container.add method originally used apparently did not have expand/fill settings to allow the expansion. The Gtk.Box.pack_start used instead does.
I tested this with all the users of ToolManagedWindowBatch and ToolManagedWindow which inherit from ToolManagedWindowBase, and did not see any bad/unexpected side effects. The Calculate Estimated Dates addon was the only one that really could use this, as it was the only one which I spotted using a potentially large widget in the notebook tab.
* Max ages should be divisible by 5 to avoid out of range
errors.
* The chart width should be greater than 45 to look right and
avoid division by zero errors.
Fixes#11384
It turns out the changes was actually changing the wrong config setting...
I had to look this one up. Using a lambda like this is called a 'closure' by some; what is happening is that the value 'constant' is being evaluated at the time the lambda is called, not when it is assigned. So in this particular bit of code the preference setting was actually changing 'preferences.family-relation-type' (the value of the variable 'constant' set a bit after the lambda definition.
I reverted this particular bit of code, as I think this kind of Python knowledge is pretty obscure (I could have just used a different unique name for the 'constant' variable).
Fixes#11390
As it says, if Family Tree name contained non-ASCII characters, the titlebar on Windows would display it wrong. Turned out to be reading of a utf8 file without the 'encoding' set. On Windows this results in using the default encoding which is one of the code pages, NOT utf8.
that passes
If user has only a single font available that passes check for the Genealogical Symbols being all present, the original code crashed. Apparently never tested... #598Fixes#11395
Fixes#11380, #11339
In prior versions of Gramps you could use the undo/redo keys to edit items in the text entries. This no longer works.
This is related to the changes to suppress odd characters and leading/trailing spaces. The Gtk.Entry.set_text() call is effectively clearing the undo/redo list at every keystroke or when you leave the field.
In this PR I move the odd characters cleanup into UndoableEntry.do_insert_text instead of MonitoredEntry.
I scanned the users of MonitoredEntry and they all appeared to use Glade files, I scanned the glade files for anyone using just plain Entry (none found), they all appeared to use UndoableEntry or ValidatableMaskedEntry, so this should cover everyone.
* Narrative web: Ancestor's tree display looks weird
Solves the following:
- Person boxes overlap
- Some person boxes partially visible or hidden
Fixes#11382
* Narrative web: some cleanup in ancestortree.css
* Narrative web : ancestor tree and long names.
* Adapt ancestor tree css file for all themes
Via email a user noted a bug when "Gramps -v" was used with Gtk not installed (and gi was).
When the "gi.require_version('Gtk', '3.0')" was added during Gramps 5.0.0 timeframe, a corresponding exception was not.
Fixes#11366
* Make PedigreeView listen on event update signals.
The PedigreeView was not listening for updates on events, so changes to a birthday or death would not be reflected in the view.
* Remove comment about signal side-effects.
Fixes#11378
For the index, toc, bookmark etc. normal XML escape is correct, the original code also added sub-tags for line break and tab which was NOT correct.
Useful when you create a site web, you don't need to create a new
web when you are testing the stylesheets. The final user can change
the stylesheet for the current page.
i.e. on Firefox: View -> Page style -> The stylesheet
The "graph" is the data part for genealogytree without the boilerplate
code around it that makes up a full LaTeX file. This format is useful
for people who have their own (more sophisticated) LaTeX file with
custom styles and so on.
The implementation is pretty straight-forward: Just don't output the
LaTeX code.
Currently dates and places contain XML special characters (example: birth date
= "1867 <?>"), the item is rendered incorrectly in the report, when images are
included. Escaping special characters with html.escape solves the problem.
Also fixes the & sign in the name, which earlier caused the report to fail.
If you create a filter with the rule name:
"Events with a particular type"
or
"Events with <data>"
The menu "Travel", "Academic"... are not translated
Fixes#11293
From 5.1 the narrative notes are placed just after the name, gender and
age at death. This follow the feature request #6772.
Some people want to have this placement an option to have the same
functionality as before
Fixes#11283
* 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.
* Avoid comma in a lat/lon entry field.
* Be more precise on the tooltip text.
* conv_lat_lon should not accept comma in lat/lon
* Tests failed with comma in lat/lon
* geoplaces fails to center if bad lat/lon
In this patch:
1 - If you copy/paste strings from another application,
you can add CR, LF, TAB and other special characters. I remove them.
2 - suppress all leading and trailing spaces for these entry field.
Check all values of an attribute type and not only the first one.
Check all values of an attribute type. If a person has several attributes with the same type/key the current behaviour is that only the first value is checked.
Example Person X Atrributes:
(Key=occupation: Value=farmer)
(Key=occupation: Value=soldier)
(Key=occupation: Value=smith)
=> Currently: Filter 'persons with attribut' (Key=occupation, Value=farmer) returns Person X, but no return of Perrson X for (Key=occupation, Value=soldier) or (Key=occupation: Value=smith).
=> After fix: Person X is returned for all three filter searches.
* Fix '_havechildren.py' person filter
Check all families of a person for children and not only the first family
* Update 'person_rule_test.py' and '_havechildren.py'
Correct number for persons who have children is 905
This tool is looking for place names with leading or/and trailing spaces.
It also looks for in the first name and surname.
For each entry which contains leading or trailing spaces,
a row is added in a treeview.
You can see where the spaces are for each row as the name is underlined.
If you double click on the row, you can edit the Place or the Person.
Fixes#10824
User can now add the following columns in the csv import file for a person:
- Occupation description
- Occupation date
- Occupation place
- Occupation source
- Residence date
- Residence place
- Residence source
- Attribute type
- Attribute value
- Attribute source
the corresponding events will be added to the person.
The user can put several lines for the same person if two occupations are known, one event per line will be created.
10341:
When we are on a mobile phone or a small device, we suppress the navigation tab.
In place, we have a new icon on the upper left which is used to show the dropdown menu.
Thanks to Theo van Rijn for showing me the way to do that.
10962:
For Home, Introduction and Contact, If we have an image and this image contains regions,
show the regions. We can go directly to the person page associated to this region.
If we click on the image, we go directly to the associated media page. This will be true only if we selected "include images and media objects" and "create and only use thumbnail" is unselected
11018:
The first line identifying a family will be more legible.
The link is not useful in the parents and pedigree section for the current person.
Adapt some css files.
11029:
sort the place references either by date or by name.
Resolves#10341, #10962, #11018, #11029
Gramps should be able to use genealogy symbols everywhere.
Several kinds of use for the genealogical symbols :
The graphical interface (GUI, editors, graphical views, ...)
The Web reports (webcal, narrativeweb, ...)
The Text reports (odf, rtf, pdf, ...)
The graphical reports (odf, rtf, svg, ...)
Resolves#9098
Use the current Gtk theme settings for the appearance of the
ValidatableMaskedEntry widget in its error state. This avoids
problems with dark themes.
Fixes#11046.
This was already used in PersonDetails and (incorrectly) in TreeDoc.
Add it to the list in AttributeType, provide translations and fix
usage in TreeDoc in case the user is not running with English translation.
Fixes#10145
Note: a completely empty birth event is removed by Check and Repair; this is wrong in that sometimes we know a person is born, but not date/place. In Gedcom this is indicated by "1 BIRT Y" lines.
So this PR adds a description to the birth event. This is not an issue for other event types, the C&R tool sees the non-default type and leaves it alone, but birth is the default type.
like Event delete or update.
Fixes#11051
Looks like someone simply forgot to register the handles with the callman...
I checked other similar cases and did not see any other issues.
* Fix Gedcom import/export for more comprehensive mime types
Fixes#11041
* Fix Gedcom import to better find media files
Issue #11041
* Fix Gedcom test files for media mime and error location message
Fixes#10966
When we try to merge two objects, we should stay on the selected row
in list views.
This problem occurs for persons, families, events, places, sources,
citations, repositories, media and notes.
Another problem:
In case we select the first family and select the gramps_id of the
second family, the new gramps_id is ignored: problem in MergeFamilyQuery
This enhancement adds a new 'compact' field to the Narrated
Web Report. A compact tree is one that is not a simple binary
layout but uses the algorithm of Buchheim/Walker to create a
layout that is sensible but also compact.
Creating a compact layout is slower than a simple binary
tree but the results are significantly improved and do not leave
large areas of whitespace where there are no nodes to be shown.
* Media Manager: add help button and remove '...'
Issue #9042
* Edit/Preferences: add Help button
Issue #9042
* Style Editor, Document Styles dialog: add help buttons
Issue #9042
* Fix Select Person dialog Help button URL
Issue #9042
* Fix Select Repository dialog Help button URL
Issue #9042
* Relationship Calculator: Add help button
Issue #9042
* Reorder Relationships dialog; add Help button
Issue #9042
* Generate Book Dialog; Fix Help URL
Issue #9042
* Manage Book dialog; add help button
Issue #9042
* Fix Detached Gramplets Help button URL when 'help_url' not in .gpr
Issue #9042
* Fix help URLs when they contain illegal characters and to match wiki
section targetID algorithm
Issue #9042
* Update/Completion Croatian translation
This is a big update. The croatian translation is now 100% complete.
Translated all missing strings, made lots of corrections, improved
consistency in the wording, tested thoroughly. Also, it will work
with the updated datehandler file "_date_hr.py", which i'll be
updating simultaneously.
* Croatian Datehandler update
Made changes to fit croatian specific date handling. Also because i've
updated the hr.po file. I've tested it with the present
"_datedisplay.py" of the maintainance/gramps50 branch.
Basically it would be great, if next to the obligatory "display_iso"
format, only two more formats would show up in the croatian drop-down
menus: "dd_dformat01" (numerical) and "dd_dformat04". Other formats
are unneeded.
9. 5. 2018. => ordinal numbers, all separated by spaces
9. svibnja 2018. => ordinal numbers and genitiv month's form,
all separated by spaces
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.
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
Instead of requiring that the entire search string matches a single one of the Person's names, the function will require that each word in the search string matches any of the Person's name fields.
Fixes#7950
Added an option to the birthday report that allows for the year of birth
(or in the case of a wedding it's year) to be printed in the report.
Resolves#5948
Added a text option to have a string that will show after a persons name
in the birthday and anniversary report. This works for both birthdays
and anniversaries.
Issue #3540
