* Navweb: multi-language configuration.
* Navweb: multi-language exec, navigation menu, css
* Navweb: make css responsive for multi-language
* Language menu must work with a non english lang
* Avoid to copy common files for each language
* Use cms and archive in multi-languages
* Add the default index.
* Some cleanup.
* Images: performances improvement with image_size
Need to use the magic library (python-magic, python3-magic, ...)
If this library don't exist on the system, continue to use the Gdk method.
- force archive if we use CMS
- remove some unused code
- some strings are not translatable
- stay on the same page when you change language
- add image in the ancestor tree for all levels and not for the first 5
performances:
- copy images and thumbs only for the first language
* Some minor corrections and performances test
* Update comments for methods and functions
* Narweb: add show tags option
* Try to translate tags and suppress the colon (:)
* Narweb: integrate of webcal for multilang use
For each lang, we use the related calendar if it exists
* Death string only translated for the locale lang
* set correct url for extrapage.
* Add optional toggle for html sections
* show birth and death date if close option selected
* No background in references section with Mainz css
* Remove photo from list incompatible with multilang
* Add the first photo to the place page marker
* Add associated persons.
* Solves 'undefined' in map popup.
* Calendar: Set the background for the current day
* Thumbnail align problem with long description.
* Set the contact page date to the note date
* Add a scroll to top button.
* Increase the nb of generations since we can scroll
* Difficult to see the "go to top" icon.
* Better management for the toggle switch
* 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
* 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
* 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.
So that they're together with the other resources instead of in
site-package/gramps. Aside from a better source and installation
layout, this makes it easier to bundle them.
svn: r22576
