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.
Force place name to be "Full" names.
Force the country field to be the last field of the place name
Force the State/province to be the penultimate field of the place name
We use place names that stop in the country, but iff we have place names
such as: city, province, country, continent, planet with the continent and
planet as the custom place type, the State/Province field will be
the name of the place continent... (should never happen, but...)
Fixes#12821
This patch is related to Bug report #012770.
When a problem occurs, we ask to the user the result of "gramps -v"
and not the result of the PrerequisitesCheckerGramplet
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
RUFNAME is the German word for "call name", i.e. the part of the given
name commonly used to address somebody. Some official documents mark it
as such.
The GEDCOM standards 5.5.1 and 5.5.5 mention this tag.
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
* The latest version of openlayers doesn't work
Every years, openlayers change its "latest" version.
If this no longer works in the browser we need to change "latest"
by another version.
v6.15.1 is the latest working version and is available several years.
If this no longer the case for this version, we need to change this version
in the gramps.ini file.
The section will be:
...
[external_modules]
;;openlayers_version=‘v6.15.1’
…
You'll need to remove the two commas before openlayers_version and
change v6.15.1 to the working version.
Available versions are provided in the OLDER SECTION of https://openlayers.org/Fixes#012680
* Change the location of js and css files
* Menu simplification and usage clarification
Show in which file the openlayers version should be modified.
Show the config name to modify.
Ensure correct index letters according to normal indexing conventions by
using ICU AlphabeticIndex.
- Add ICU AlphabeticIndex
- Modify modules that use alphabet_navigation to use AlphabeticIndex
If Alphabetic index is not available, fix some other issues.
- Implement a local AlphabeticIndex for when ICU AlphabeticIndex is not
available, using existing code algorithms
- Fix Serbian contraction DŽ not being recognised
- Fix contractions not getting a separate entry in the
alphabet_navigation
- Ensure that import from either icu or PyICU works
- Fix primary_difference to set collation strength to PRIMARY
- Fix contractions lookup to use locale for current report
- Fix get_first_letter to pass current report locale
Fixes#12350
They are no longer required and translators sometimes include
them in translated strings by mistake.
This change also makes it possible to use the vertical bar
character in translatable strings.
