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
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.
* 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
* 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
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
* Narrative web: multiple problems.
1 - Added an option for the statistics page.
2 - We have problems with notes : pages are too large
3 - Difficult to see some page on a mobile phone when you have notes.
4 - Resizing of images on a mobile
5 - Maps are too bigs on a mobile
6 - Split the event line to have a narrower page
7 - The note is spanned on two columns (Place + Description)
7 - In media pages, the progress meter doesn't work well.
8 - Add a progress meter for the medialistpage
Issues #10344
* Narrative Web: several modifications + css files
* Stylesheet problems and reverse set_header
* Removing memory cleanup.
Bug #10285
FTM adds subordinate PLAC and OBJE data to INDI.ADDR which is
non-standard. So treat it as a Residence Event, instead of an
Address.
FTM puts _DATE and _TEXT tags subordinate to OBJE, also non-standard.
* Mainz css file produces left aligned FamilyMap pages
Solving Mainz problem creates new ones with Basic-Blue
and Nebraska styles sheet.
Some cleanup with unused css file (GeoView.css)
Fixes#10268
* Many problems with css files and the ancestor tree
* media file not created if we have unused media.
Original code used readline() when file was in binary mode; this works
only if file contains '\n', true only for CRLF and LF line endings.
Switched to file text mode with correct encoding and universal newline
support.
I updated the appdata.xml file to the latest version of the specification
(https://www.freedesktop.org/software/appstream/docs/index.html), adding
some new tags in the process.
I also installed the appdata.xml file to the latest location in the
specification.
The XML has bene validated by the appstreamcli validation tool, and the
patch applied in Debian (Gramps 4.2.3).
If it looks OK, it should probably be cherry-picked to the gramps42
maintenance branch.
