If the user inputs an invalid date this change keeps the application
from crashing when such a date is found. The invalid date
information is reported to the user in the log.
Fixes#12658.
Fixes#12437 by reverting commit 75921ceaf40f3ced597d99c43794b98f81e49957 due to
reports of regression where processing of the generated TeX file fails due to
bad path specificiation for image files.
Change was introduced in bug fix for #10495.
Bugs #12437 and #12697 reported the regression and confirmed that reverting the
change fixes the regression.
Fix place title in graphical reports which have user-defined display formats
to use date-specific alternate name.
This impacts Ancestor Tree, Descendant Tree, and Family Descendant Tree.
Fixes#12763.
Remove Python2 code obsoleted by Python3, which was corrupting GEDCOM export of Gramps Notes text that includes multi-byte utf-8 characters.
Fixes#12709.
Color tags work correctly in all views except in pedigree views.
These views modify colors:
...
context.set_source_rgba(*(self.bordercolor[:3] + (0.4,)))
... and
context.set_source_rgb(*self.bgcolor[:3])
As it works everywhere except in these views, I think it is a bug
even if we cannot enter color names in tags
Fixes#012866
When we use checkboxes in columns.
The path was converted to int. Why ?
But when we have multiple level, the path format is "x:y" for two levels,
"x:y:z" for three levels, etc
- Consistent usage of "Tag": was "Tag" or "Atrybut", note that
"Attribute" (atrybut) is something different than tag
- "Magazyn" (repository) renamed to "Repozytorium"
- other fixes and addons
The grampletpane module save data in a config file for all
the gramplets added in the dashboard.
The python configparser module doesn't like if we have a "%"
character in a string.
Fixes#012423
