You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(22) |
Jun
(13) |
Jul
(11) |
Aug
(16) |
Sep
(17) |
Oct
(16) |
Nov
(58) |
Dec
(31) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(28) |
Feb
(26) |
Mar
(6) |
Apr
(10) |
May
(14) |
Jun
(14) |
Jul
(18) |
Aug
(33) |
Sep
(23) |
Oct
(36) |
Nov
(36) |
Dec
(29) |
2003 |
Jan
(36) |
Feb
(52) |
Mar
(31) |
Apr
(9) |
May
(37) |
Jun
(29) |
Jul
(35) |
Aug
(34) |
Sep
(30) |
Oct
(44) |
Nov
(107) |
Dec
(95) |
2004 |
Jan
(78) |
Feb
(145) |
Mar
(163) |
Apr
(109) |
May
(61) |
Jun
(110) |
Jul
(137) |
Aug
(138) |
Sep
(100) |
Oct
(81) |
Nov
(28) |
Dec
(153) |
2005 |
Jan
(45) |
Feb
(88) |
Mar
(63) |
Apr
(71) |
May
(124) |
Jun
(47) |
Jul
(52) |
Aug
(66) |
Sep
(72) |
Oct
(54) |
Nov
(57) |
Dec
(54) |
2006 |
Jan
(91) |
Feb
(91) |
Mar
(116) |
Apr
(80) |
May
(116) |
Jun
(49) |
Jul
(55) |
Aug
(80) |
Sep
(84) |
Oct
(135) |
Nov
(82) |
Dec
(215) |
2007 |
Jan
(147) |
Feb
(132) |
Mar
(139) |
Apr
(147) |
May
(149) |
Jun
(174) |
Jul
(177) |
Aug
(91) |
Sep
(137) |
Oct
(123) |
Nov
(150) |
Dec
(110) |
2008 |
Jan
(166) |
Feb
(122) |
Mar
(143) |
Apr
(163) |
May
(134) |
Jun
(157) |
Jul
(144) |
Aug
(209) |
Sep
(176) |
Oct
(215) |
Nov
(178) |
Dec
(170) |
2009 |
Jan
(199) |
Feb
(171) |
Mar
(268) |
Apr
(188) |
May
(181) |
Jun
(154) |
Jul
(110) |
Aug
(162) |
Sep
(104) |
Oct
(128) |
Nov
(225) |
Dec
(137) |
2010 |
Jan
(170) |
Feb
(143) |
Mar
(152) |
Apr
(200) |
May
(199) |
Jun
(150) |
Jul
(160) |
Aug
(155) |
Sep
(77) |
Oct
(66) |
Nov
(222) |
Dec
(120) |
2011 |
Jan
(108) |
Feb
(163) |
Mar
(88) |
Apr
(105) |
May
(157) |
Jun
(201) |
Jul
(140) |
Aug
(168) |
Sep
(177) |
Oct
(126) |
Nov
(96) |
Dec
(99) |
2012 |
Jan
(156) |
Feb
(172) |
Mar
(115) |
Apr
(68) |
May
(107) |
Jun
(188) |
Jul
(134) |
Aug
(169) |
Sep
(347) |
Oct
(168) |
Nov
(128) |
Dec
(177) |
2013 |
Jan
(181) |
Feb
(247) |
Mar
(198) |
Apr
(161) |
May
(215) |
Jun
(319) |
Jul
(196) |
Aug
(149) |
Sep
(142) |
Oct
(130) |
Nov
(130) |
Dec
(100) |
2014 |
Jan
(247) |
Feb
(195) |
Mar
(119) |
Apr
(276) |
May
(96) |
Jun
(325) |
Jul
(180) |
Aug
(190) |
Sep
(169) |
Oct
(262) |
Nov
(79) |
Dec
(185) |
2015 |
Jan
(479) |
Feb
(263) |
Mar
(255) |
Apr
(136) |
May
(361) |
Jun
(198) |
Jul
(349) |
Aug
(645) |
Sep
(96) |
Oct
(196) |
Nov
(99) |
Dec
(233) |
2016 |
Jan
(204) |
Feb
(477) |
Mar
(201) |
Apr
(126) |
May
(182) |
Jun
(108) |
Jul
(180) |
Aug
(309) |
Sep
(177) |
Oct
(315) |
Nov
(424) |
Dec
(334) |
2017 |
Jan
(362) |
Feb
(339) |
Mar
(251) |
Apr
(144) |
May
(231) |
Jun
(290) |
Jul
(89) |
Aug
(96) |
Sep
(62) |
Oct
(137) |
Nov
(226) |
Dec
(181) |
2018 |
Jan
(139) |
Feb
(244) |
Mar
(200) |
Apr
(66) |
May
(138) |
Jun
(111) |
Jul
(265) |
Aug
(291) |
Sep
(232) |
Oct
(233) |
Nov
(247) |
Dec
(397) |
2019 |
Jan
(298) |
Feb
(217) |
Mar
(176) |
Apr
(248) |
May
(147) |
Jun
(143) |
Jul
(78) |
Aug
(215) |
Sep
(230) |
Oct
(295) |
Nov
(205) |
Dec
(266) |
2020 |
Jan
(186) |
Feb
(102) |
Mar
(95) |
Apr
(428) |
May
(294) |
Jun
(45) |
Jul
(48) |
Aug
(267) |
Sep
(171) |
Oct
(135) |
Nov
(32) |
Dec
(80) |
2021 |
Jan
(77) |
Feb
(31) |
Mar
(61) |
Apr
(41) |
May
(33) |
Jun
(55) |
Jul
(45) |
Aug
(26) |
Sep
(14) |
Oct
(38) |
Nov
(58) |
Dec
(23) |
2022 |
Jan
(62) |
Feb
(30) |
Mar
(51) |
Apr
(74) |
May
(26) |
Jun
(8) |
Jul
(6) |
Aug
(8) |
Sep
(14) |
Oct
(7) |
Nov
(14) |
Dec
(45) |
2023 |
Jan
(30) |
Feb
(12) |
Mar
(12) |
Apr
(8) |
May
(22) |
Jun
(17) |
Jul
|
Aug
(14) |
Sep
(50) |
Oct
(11) |
Nov
(2) |
Dec
|
2024 |
Jan
(10) |
Feb
(3) |
Mar
(17) |
Apr
(3) |
May
|
Jun
(8) |
Jul
(5) |
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
From: Enno B. <enn...@gm...> - 2023-09-16 14:15:05
|
Hello Peter, > There is a problem here. I have been trying to reset my password, and > the system says that it is sending me an email, but I never get it. > And No, it is not in my Sp*m folder. And because it won't accept > what I think is my password, I cannot log on to delete my account. I just entered your email address on the list site, and asked it to send a password reminder to you. And now I wonder whether you really get such a thing. And a quick test with my own email suggests that it works. Regards, Enno |
From: Peter M. <pet...@ho...> - 2023-09-16 08:22:30
|
There is a problem here. I have been trying to reset my password, and the system says that it is sending me an email, but I never get it. And No, it is not in my Sp*m folder. And because it won't accept what I think is my password, I cannot log on to delete my account. Peter M. On 15/09/2023 22:54, Victor Engel wrote: > I think he needs to do it himself. > > Follow this link. > > https://sourceforge.net/projects/gramps/lists/gramps-users/unsubscribe > > There will be a form to enter your email. You have to be logged on. If you > don't remember your password, you can have it send a reminder or reset or > something. > > On Fri, Sep 15, 2023 at 4:41 PM Ed Hamilton <edh...@gm...> wrote: > >> Could someone do something about this person who seems to want to be >> removed from the mailing list and decided to write me directly because I >> posted something? When I replied, he got worse, but I put a filter on gmail >> to just delete his stuff and it did, or I would forward that to you as well. >> Thank you. >> |
From: Victor E. <br...@gm...> - 2023-09-15 21:54:59
|
I think he needs to do it himself. Follow this link. https://sourceforge.net/projects/gramps/lists/gramps-users/unsubscribe There will be a form to enter your email. You have to be logged on. If you don't remember your password, you can have it send a reminder or reset or something. On Fri, Sep 15, 2023 at 4:41 PM Ed Hamilton <edh...@gm...> wrote: > Could someone do something about this person who seems to want to be > removed from the mailing list and decided to write me directly because I > posted something? When I replied, he got worse, but I put a filter on gmail > to just delete his stuff and it did, or I would forward that to you as well. > Thank you. > > > Ken Lind <ke...@li...> writes: > > > See!… Like I said… Take me off this email list… I followed your > directions exactly like you wrote and it simply doesn’t work! > > > > You leave me no choice but to respond to every Gramps email asking to be > removed! > > > > On Sep 13, 2023, at 8:16 AM, Ed Hamilton <edh...@gm...> wrote: > > > > Hi, > > > > I use a static site generator for articles and gramps for the trees. I > have links in the sidebar of the articles for the trees. > > > > main site: https://myoldohiohome.com/ > > > > one of the trees: https://myoldohiohome.com/cleveland/ > > > > I don't know if that is what you would want to do or not. I am on > > Linux and use pelican because it was the easiest for me to configure. > > There are many. You already are using wordpress on the Ruminations > > section, you could adapt that somehow. I forget if you'd need to run > > another instance of wordpress or if you can put articles into separate > > folders from their interface. > > > > Nice landing page, by the way. I didn't know you could do that in gramps. > > > > Ed H. > > > > On 9/9/23 7:22 PM, Kyle Davenport wrote: > >> I'm just fishing for ideas about making my Gramps website more > interesting. > >> > >> 1) I have to update the website every few months because of changes and > updates. Is there any way to show what's changed or what's new? > >> > >> 2) When the paper trail runs out, we genealogists have to look for > >> clues in the times and places of our ancestor, somehow dramatizing > >> what their life was like. I wrote such a treatment in a document > >> with all available evidence, lore, and images. See "A Collin's Tale > >> <https://quickening.zapto.org/Collins%20Tale.pdf>". Has anyone tried > >> to incorporate this into their Gramps tree, and how did you do it? > >> > >> 3) I have a nice landing page <https://quickening.zapto.org/gramps/> > >> for my Gramps site, but somehow I would like more of these > >> HTML-formatted stories thru-out the site, either on individual pages > >> or hanging off them. > >> > >> Sort of an aside, I tried to do Openmap places in the narrative web > report and it doesn't seem to work. > >> > >> > >> => I've seen emails to the list strip html. Contact me for the links. > >> > > > -- > Ed Hamilton > > > -- > Gramps-users mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-users > https://gramps-project.org -------------- next part -------------- An HTML attachment was scrubbed... |
From: Ed H. <edh...@gm...> - 2023-09-15 21:38:36
|
Could someone do something about this person who seems to want to be removed from the mailing list and decided to write me directly because I posted something? When I replied, he got worse, but I put a filter on gmail to just delete his stuff and it did, or I would forward that to you as well. Thank you. Ken Lind <ke...@li...> writes: > See!… Like I said… Take me off this email list… I followed your directions exactly like you wrote and it simply doesn’t work! > > You leave me no choice but to respond to every Gramps email asking to be removed! > > On Sep 13, 2023, at 8:16 AM, Ed Hamilton <edh...@gm...> wrote: > > Hi, > > I use a static site generator for articles and gramps for the trees. I have links in the sidebar of the articles for the trees. > > main site: https://myoldohiohome.com/ > > one of the trees: https://myoldohiohome.com/cleveland/ > > I don't know if that is what you would want to do or not. I am on > Linux and use pelican because it was the easiest for me to configure. > There are many. You already are using wordpress on the Ruminations > section, you could adapt that somehow. I forget if you'd need to run > another instance of wordpress or if you can put articles into separate > folders from their interface. > > Nice landing page, by the way. I didn't know you could do that in gramps. > > Ed H. > > On 9/9/23 7:22 PM, Kyle Davenport wrote: >> I'm just fishing for ideas about making my Gramps website more interesting. >> >> 1) I have to update the website every few months because of changes and updates. Is there any way to show what's changed or what's new? >> >> 2) When the paper trail runs out, we genealogists have to look for >> clues in the times and places of our ancestor, somehow dramatizing >> what their life was like. I wrote such a treatment in a document >> with all available evidence, lore, and images. See "A Collin's Tale >> <https://quickening.zapto.org/Collins%20Tale.pdf>". Has anyone tried >> to incorporate this into their Gramps tree, and how did you do it? >> >> 3) I have a nice landing page <https://quickening.zapto.org/gramps/> >> for my Gramps site, but somehow I would like more of these >> HTML-formatted stories thru-out the site, either on individual pages >> or hanging off them. >> >> Sort of an aside, I tried to do Openmap places in the narrative web report and it doesn't seem to work. >> >> >> => I've seen emails to the list strip html. Contact me for the links. >> -- Ed Hamilton |
From: Ed H. <edh...@gm...> - 2023-09-13 15:17:04
|
Hi, I use a static site generator for articles and gramps for the trees. I have links in the sidebar of the articles for the trees. main site: https://myoldohiohome.com/ one of the trees: https://myoldohiohome.com/cleveland/ I don't know if that is what you would want to do or not. I am on Linux and use pelican because it was the easiest for me to configure. There are many. You already are using wordpress on the Ruminations section, you could adapt that somehow. I forget if you'd need to run another instance of wordpress or if you can put articles into separate folders from their interface. Nice landing page, by the way. I didn't know you could do that in gramps. Ed H. On 9/9/23 7:22 PM, Kyle Davenport wrote: > I'm just fishing for ideas about making my Gramps website more > interesting. > > 1) I have to update the website every few months because of changes > and updates. Is there any way to show what's changed or what's new? > > 2) When the paper trail runs out, we genealogists have to look for > clues in the times and places of our ancestor, somehow dramatizing > what their life was like. I wrote such a treatment in a document with > all available evidence, lore, and images. See "A Collin's Tale > <https://quickening.zapto.org/Collins%20Tale.pdf>". Has anyone tried > to incorporate this into their Gramps tree, and how did you do it? > > 3) I have a nice landing page <https://quickening.zapto.org/gramps/> > for my Gramps site, but somehow I would like more of these > HTML-formatted stories thru-out the site, either on individual pages > or hanging off them. > > Sort of an aside, I tried to do Openmap places in the narrative web > report and it doesn't seem to work. > > > => I've seen emails to the list strip html. Contact me for the links. > |
From: Dave S. <dav...@gm...> - 2023-09-10 21:01:43
|
Here's a quick fix for the the maps https://gramps.discourse.group/t/help-with-maps-in-narrative-web-site-needed/2714/13 edit gramps\plugins\webreport\place.py replace “latest” with “v6.15.1” at lines 387 and 390 "https://openlayers.org/en/latest/build/ol.js" "https://openlayers.org/en/v6.15.1/build/ol.js" and "https://openlayers.org/en/latest/css/ol.css" "https://openlayers.org/en/v6.15.1/css/ol.css" and do the same to person.py replace “latest” with “v6.15.1” at lines 722 and 725 On Sat, Sep 9, 2023 at 7:37 PM Kyle Davenport <kda...@tx...> wrote: > I'm just fishing for ideas about making my Gramps website more interesting. > > 1) I have to update the website every few months because of changes and > updates. Is there any way to show what's changed or what's new? > > 2) When the paper trail runs out, we genealogists have to look for clues > in the times and places of our ancestor, somehow dramatizing what their > life was like. I wrote such a treatment in a document with all available > evidence, lore, and images. See "A Collin's Tale > <https://quickening.zapto.org/Collins%20Tale.pdf>". Has anyone tried to > incorporate this into their Gramps tree, and how did you do it? > > 3) I have a nice landing page <https://quickening.zapto.org/gramps/> for > my Gramps site, but somehow I would like more of these HTML-formatted > stories thru-out the site, either on individual pages or hanging off them. > > Sort of an aside, I tried to do Openmap places in the narrative web > report and it doesn't seem to work. > > > => I've seen emails to the list strip html. Contact me for the links. > > -- > Kyle Davenport > Unix Systems Consultant > Dallas, TX > -------------- next part -------------- > An HTML attachment was scrubbed... > > -- > Gramps-users mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-users > https://gramps-project.org -------------- next part -------------- An HTML attachment was scrubbed... |
From: Paul C. <pau...@gm...> - 2023-09-10 15:16:20
|
One of the code sources on the web (OpenLayers) recently changed their web links in such a way that Narrative Web cannot find a needed prerequisite; ol.js and ol.css.files. I don't know if we will be able to get out a new version of 5.1.x to correct this, as we have recently decided to stop producing new versions. The soon to be upcoming 5.2.0 release fixes this. https://github.com/gramps-project/gramps/commit/18da49cd75202480d956acec7c7d3069f3c98e63 shows what was done in the 5.2.0 release to fix this; if you are technically inclined, you might try to patch your installation the same way. Paul C. On Sat, Sep 9, 2023 at 6:37 PM Kyle Davenport <kda...@tx...> wrote: > I'm just fishing for ideas about making my Gramps website more interesting. > > 1) I have to update the website every few months because of changes and > updates. Is there any way to show what's changed or what's new? > > 2) When the paper trail runs out, we genealogists have to look for clues > in the times and places of our ancestor, somehow dramatizing what their > life was like. I wrote such a treatment in a document with all available > evidence, lore, and images. See "A Collin's Tale > <https://quickening.zapto.org/Collins%20Tale.pdf>". Has anyone tried to > incorporate this into their Gramps tree, and how did you do it? > > 3) I have a nice landing page <https://quickening.zapto.org/gramps/> for > my Gramps site, but somehow I would like more of these HTML-formatted > stories thru-out the site, either on individual pages or hanging off them. > > Sort of an aside, I tried to do Openmap places in the narrative web > report and it doesn't seem to work. > > > => I've seen emails to the list strip html. Contact me for the links. > > -- > Kyle Davenport > Unix Systems Consultant > Dallas, TX > -------------- next part -------------- > An HTML attachment was scrubbed... > > -- > Gramps-users mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-users > https://gramps-project.org -------------- next part -------------- An HTML attachment was scrubbed... |
From: Kyle D. <kda...@tx...> - 2023-09-09 23:34:47
|
I'm just fishing for ideas about making my Gramps website more interesting. 1) I have to update the website every few months because of changes and updates. Is there any way to show what's changed or what's new? 2) When the paper trail runs out, we genealogists have to look for clues in the times and places of our ancestor, somehow dramatizing what their life was like. I wrote such a treatment in a document with all available evidence, lore, and images. See "A Collin's Tale <https://quickening.zapto.org/Collins%20Tale.pdf>". Has anyone tried to incorporate this into their Gramps tree, and how did you do it? 3) I have a nice landing page <https://quickening.zapto.org/gramps/> for my Gramps site, but somehow I would like more of these HTML-formatted stories thru-out the site, either on individual pages or hanging off them. Sort of an aside, I tried to do Openmap places in the narrative web report and it doesn't seem to work. => I've seen emails to the list strip html. Contact me for the links. -- Kyle Davenport Unix Systems Consultant Dallas, TX -------------- next part -------------- An HTML attachment was scrubbed... |
From: Peter F. <pe...@si...> - 2023-09-08 15:09:31
|
On 08/09/2023 10:12, Enrique via Gramps-users wrote: > Como la mayoría de estos ficheros son imágenes o .pdf yo los he > archivado en /Imágenes/Fotos/Genealogía/Objetos/ A colleague has just reminded me that I keep my non-genealogical images in ~/Pictures/<dir> so why treat genealogical images any differently. ¡Muchas gracias Enrique!, this is a good idea. > Dentro de ese directorio hay una carpeta por tipo de documento > [...] Las fotos de personas están en /Imágenes/Fotos/aaaa/mm I already have ~/Pictures/Photos/yyyy/mm, so this becomes more obvious by the minute. What's the Spanish for "Duh!" Peter |
From: Enrique <kup...@mu...> - 2023-09-08 09:12:53
|
-- -- «» Mensaje enviado por Enrique a través de Evolution El jue, 07-09-2023 a las 22:19 +0100, Peter Flynn escribió: > On 03/10/2021 12:06, Peter Flynn wrote: > > Thanks to all who responded. I'm looking at several ways of doing this. > > Finally got around to starting dealing with images (only photos so far; > documents come later). > > 1. At the moment all my own genealogy-related files are in > ~/Documents/domestic/family but that could easily be moved. Como la mayoría de estos ficheros son imágenes o .pdf yo los he archivado en /Imágenes/Fotos/Genealogía/Objetos/ Dentro de ese directorio hay una carpeta por tipo de documento (Administración, Blogs, Cartas, Correos, Escrituras, Esquelas, Notarios, Prensa, Recordatorios, Sepulturas, Sitiosweb, etc). Las fotos de personas están en /Imágenes/Fotos/año de la fecha del evento o de la toma de la foto en formato aaaa/mm (por ejemplo: una foto de un retrato pintado en el que aparece un antepasado estaría archivada en la fecha en que se pintó el retrato; si la imagen es una foto tomada directamente a la persona se archivaría en la fecha en que se hizo la foto o en la fecha que correspondiese a la edad que tenía cuando se la tomaron). Traducción: Since most of these files are images or .pdf files I have filed them in /Images/Pictures/Pictures/Genealogy/Objects/ Within that directory there is a folder by type of document (Administration, Blogs, Letters, Mail, Deeds, Death notices, Notaries, Press, Reminders, Graves, Websites, etc). Photos of people are in /Pictures/Pictures/Year of the date of the event or the date the photo was taken in yyyy/mm format (for example: a photo of a painted portrait of an ancestor would be filed on the date the portrait was painted; if the image is a photo taken directly of the person it would be filed on the date the photo was taken or on the date corresponding to the age of the person when the photo was taken). Translated with www.DeepL.com/Translator (free version) > > > On 28/09/2021 15:09, Dave Scheipers wrote: > [...] > > > More importantly, is how you will store your various scans in your > > > media subfolders. By Family? By Event? I opted for event folders. > > 2. With images, AFAICS the key identifier is usually the person or > people in the image — that is, relatives asking questions seem > most often ask about specific people, rather than events or places. > As many images are of groups, I'm open to suggestions about file > naming. > > 3. What is the default $GRAMPSHOME under Linux? Is it ~/.gramps? That > directory contains: > > drwxrwxr-x 2 peter peter 4096 Jan 27 2022 css > drwxrwxr-x 2 peter peter 4096 Jan 27 2022 env > drwxrwxr-x 3 peter peter 4096 Jul 12 11:01 gramps51 > drwxrwxr-x 4 peter peter 4096 Jan 27 2022 grampsdb > -rw-rw-r-- 1 peter peter 239 Sep 7 21:44 recent-files-gramps.xml > -rw-rw-r-- 1 peter peter 18933 Oct 5 2022 report_options.xml > drwxrwxr-x 2 peter peter 4096 Jan 27 2022 temp > drwxrwxr-x 4 peter peter 4096 Jan 27 2022 thumb > > I've never touched any of this, only backed it up. > > > Peter > -------------- next part -------------- An HTML attachment was scrubbed... |
From: Peter F. <pe...@si...> - 2023-09-07 21:19:18
|
On 03/10/2021 12:06, Peter Flynn wrote: > Thanks to all who responded. I'm looking at several ways of doing this. Finally got around to starting dealing with images (only photos so far; documents come later). 1. At the moment all my own genealogy-related files are in ~/Documents/domestic/family but that could easily be moved. > On 28/09/2021 15:09, Dave Scheipers wrote: [...] >> More importantly, is how you will store your various scans in your >> media subfolders. By Family? By Event? I opted for event folders. 2. With images, AFAICS the key identifier is usually the person or people in the image — that is, relatives asking questions seem most often ask about specific people, rather than events or places. As many images are of groups, I'm open to suggestions about file naming. 3. What is the default $GRAMPSHOME under Linux? Is it ~/.gramps? That directory contains: drwxrwxr-x 2 peter peter 4096 Jan 27 2022 css drwxrwxr-x 2 peter peter 4096 Jan 27 2022 env drwxrwxr-x 3 peter peter 4096 Jul 12 11:01 gramps51 drwxrwxr-x 4 peter peter 4096 Jan 27 2022 grampsdb -rw-rw-r-- 1 peter peter 239 Sep 7 21:44 recent-files-gramps.xml -rw-rw-r-- 1 peter peter 18933 Oct 5 2022 report_options.xml drwxrwxr-x 2 peter peter 4096 Jan 27 2022 temp drwxrwxr-x 4 peter peter 4096 Jan 27 2022 thumb I've never touched any of this, only backed it up. Peter |
From: Nick H. <ni...@gr...> - 2023-08-25 21:13:46
|
Version 5.2.0-beta2, an experimental pre-release. Make sure to backup before you upgrade: https://www.gramps-project.org/wiki/index.php?title=How_to_make_a_backup The key word is experimental! It might be unwise to "upgrade" your main/real Gramps family tree into 5.2.0-beta2. In general, we recommend you make a copy of your family tree instead (typically by doing a "gramps XML" export), then try 5.2.0-beta2 on the copy. (You can keep things really separate by using the GRAMPSHOME environmental variable, if you want.) We are interested in your feedback, especially if you discover any bugs or problems which we haven't noticed. 2023-08-25 Version 5.2.0-beta2 * Updated translations: ca, cs, da, de, en_GB, es, fi, he, hr, it, nb, nl, pl, pt_BR, pt_PT, ru, sk, sv, tr, uk. * Add option to exclude fan chart title. * Prevent fan chart title being overwritten by the chart. Fixes #12926. * No longer state that Gramps will close in the backup message. Fixes #12984. * Clean up some Gdk Screen deprecations. * Fix Gedcom import tagging a note with an undefined tag handle. Fixes #12985. * Fix crash when printing notes during endnote creation. Fixes #12983. * Fix `trans_text` keyword in `xgettext`. Fixes #12982. * Fix vertical expansion of family tree manager list. * Fix error 404 with openstreetmap map service. * Restrict access to Stamen maps. Fixes #12971. * Track column width settings for all editor tabs separately. Fixes #12945, #12970. * Add support for Hebrew prefixes. * Add Farsi and Galician to Microsoft Windows Locale list. * Add a scrolled window to the preferences data tab. Fixes #12968. * Addon Manager: * Rename "Upgrade" to "Update". * Fix addon settings bug. * Add installation status filter. * Add project up, down and restore buttons. * Add help button. * Fix error when deleting a surname. Fixes #11744, #12626, #12629, #12963. * Fix glocale problems on Windows. * Fix system locale detection on MS Windows. * Add Windows AIO workflow. * Fixes for the Windows AIO build: * Convert packages from python3 to python. * Replace `share.tgz` with downloaded files. * Add missing dictionaries. * Add missing D-Bus executable. * Use newly available bsddb3 package. * Improved organization of the Addon Manager filter lists. Fixes #12958. * Update the plugin type names and sort them alphabetically. * Swap the order of "Expert" and "Developer" in the audience list. * Reverse the order of the status list. * Include event reference citations and notes in Gedcom export. * Better URLs for gramplet bar help. Fixes #12957. * Tidy up strings in preferences. * Fix spelling mistake in Pro-Gen importer. * Improve Addon Manager search. Fixes #12955. * Check for Windows executables in addon requirements. Fixes #12954. * Do not strip checksum of media object in private proxy. * Update po snippet generation to output msgctxt. * Save column sizes before a rebuild. Save column sizes as floats rather than integers. Fixes #12943. * Set default column size in list views to sensible defaults. Fixes #12944. * String improvements. * Update authors file. * Fix changes reverted by mistake. This restores a couple of autobackup intervals and removes bsddb from the list of backends. * Fix bottombar not saving size. Fixes #12941. * Fix incorrect genealogical symbols. Fixes #12937. * Mac: Use tarball for osm-gps-map instead of git repository. * Changes for Black integration. You can obtain Gramps 5.2.0-beta2 from the GitHub release page: https://github.com/gramps-project/gramps/releases/tag/v5.2.0-beta2 |
From: Harvey N. <ha...@ni...> - 2023-08-19 10:31:50
|
You can create a new family with unknown father and the first child as 'birth' child who is also 'adopted' by the second family. In the graph view, right click on the marriage (oval) symbol for each family and 'edit'. The 'Children' tab can be used to add or edit the children belonging to each family. Cheers Harvey On Sat, 2023-08-19 at 10:54 +0100, REUBY Dianne via Gramps-users wrote: > > Running Gramps 5.15 on Ubuntu 22.04 > > > > I have a female ancestor who had her first child out of wedlock. She > married and had several children with her husband. > > > > When I switch to Charts I can see either her first child and his > descendants, or I can see her husband and second family by choosing > him from People and then switching to Charts. > > > > ID for woman is same, so definitely same person. Marriage shows both > her and her spouse. > > > > Father of first child is unknown, so is this why my chart doesn't > show both her families - because the first one isn't actually a > family in Gramps? > > Thanks > > Dianne > -------------- next part -------------- > An HTML attachment was scrubbed... > |
From: REUBY D. <d....@nt...> - 2023-08-19 09:54:35
|
Running Gramps 5.15 on Ubuntu 22.04 I have a female ancestor who had her first child out of wedlock. She married and had several children with her husband. When I switch to Charts I can see either her first child and his descendants, or I can see her husband and second family by choosing him from People and then switching to Charts. ID for woman is same, so definitely same person. Marriage shows both her and her spouse. Father of first child is unknown, so is this why my chart doesn't show both her families - because the first one isn't actually a family in Gramps? Thanks Dianne -------------- next part -------------- An HTML attachment was scrubbed... |
From: Les B <le...@li...> - 2023-08-17 02:56:45
|
Hi I am far from an expert but would the following work? 1. Backup Up database as something like 'Family History No Notes" 2. Open New Database and import this backup. 3. Highlight and delete all the Notes in the ‘Notes’ tab. 4. Create the Website. If you tag any Notes you do want to have in the Website you can sort by that Tag [cid:image001.png@01D9D105.912A4B10] Interested to hear from others if this would be a viable option. Regards Les -----Original Message----- From: Dave Scheipers <dav...@gm...> Sent: Thursday, August 17, 2023 11:57 AM To: Edward Veal <edw...@gm...> Cc: gra...@li... Subject: Re: [Gramps-users] website question you have probably already determined that the Narrative Web does not allow you to exclude the note records from being included. You can create a database that can exclude all notes, and thus not available to the Narrative Web. Create a custom note filter. General Filters >> Every Note In the Define filter window, check the *Return values that do not match the filter rules *option. Then create an export of your database. Use the output format Gramps (XML)In the options window, set the Note filter to the filter to exclude all notes. (You can set other filters if needed.) Then you can create a new database/tree and import the file you just created and run the Narrative Web from this tree. The filter I created is crude. There MAY be note records that you actually do want in the Narrative web. You may find you need to finetune the note filter.i.e. exclude all notes attached to people, families and/ events. Dave On Wed, Aug 16, 2023 at 9:20 PM Edward Veal <edw...@gm...<mailto:edw...@gm...>> wrote: > I am trying to create a website that only shows data, not my narrative > or notes. I don't see a way to remove that information. What am I missing? > > Ed > > > -- > *Edward Veal* > email: edw...@gm...<mailto:edw...@gm...> > Cell: 806-445-6867 > -------------- next part -------------- An HTML attachment was > scrubbed... > > -- > Gramps-users mailing list > Gra...@li...<mailto:Gra...@li...> > https://kor01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flist<https://list/> > s.sourceforge.net%2Flists%2Flistinfo%2Fgramps-users&data=05%7C01%7C%7C > f6f7626a6a2b4ef36ec808db9ec58934%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C > 1%7C0%7C638278343482101405%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDA > iLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata= > gj9Q%2FTopBXlccaVlwYYY5SnBJ0O7lj1zpfrnzaR%2FyWI%3D&reserved=0 > https://kor01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgram<https://gram/> > ps-project.org%2F&data=05%7C01%7C%7Cf6f7626a6a2b4ef36ec808db9ec58934%7 > C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638278343482101405%7CUnkno > wn%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiL > CJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=zDFUIMY94i8qIV7m0ktg7moFwVyV1jAhNU > uJ5pxDs3A%3D&reserved=0 > -------------- next part -------------- An HTML attachment was scrubbed... -- Gramps-users mailing list Gra...@li...<mailto:Gra...@li...> https://kor01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fgramps-users&data=05%7C01%7C%7Cf6f7626a6a2b4ef36ec808db9ec58934%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638278343482101405%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=gj9Q%2FTopBXlccaVlwYYY5SnBJ0O7lj1zpfrnzaR%2FyWI%3D&reserved=0<https://lists.sourceforge.net/lists/listinfo/gramps-users> https://kor01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgramps-project.org%2F&data=05%7C01%7C%7Cf6f7626a6a2b4ef36ec808db9ec58934%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638278343482101405%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=zDFUIMY94i8qIV7m0ktg7moFwVyV1jAhNUuJ5pxDs3A%3D&reserved=0<https://gramps-project.org/> -------------- next part -------------- An HTML attachment was scrubbed... -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 43285 bytes Desc: image001.png |
From: Dave S. <dav...@gm...> - 2023-08-17 01:57:01
|
you have probably already determined that the Narrative Web does not allow you to exclude the note records from being included. You can create a database that can exclude all notes, and thus not available to the Narrative Web. Create a custom note filter. General Filters >> Every Note In the Define filter window, check the *Return values that do not match the filter rules *option. Then create an export of your database. Use the output format Gramps (XML)In the options window, set the Note filter to the filter to exclude all notes. (You can set other filters if needed.) Then you can create a new database/tree and import the file you just created and run the Narrative Web from this tree. The filter I created is crude. There MAY be note records that you actually do want in the Narrative web. You may find you need to finetune the note filter.i.e. exclude all notes attached to people, families and/ events. Dave On Wed, Aug 16, 2023 at 9:20 PM Edward Veal <edw...@gm...> wrote: > I am trying to create a website that only shows data, not my narrative or > notes. I don't see a way to remove that information. What am I missing? > > Ed > > > -- > *Edward Veal* > email: edw...@gm... > Cell: 806-445-6867 > -------------- next part -------------- > An HTML attachment was scrubbed... > > -- > Gramps-users mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-users > https://gramps-project.org > -------------- next part -------------- An HTML attachment was scrubbed... |
From: Edward V. <edw...@gm...> - 2023-08-17 01:17:51
|
I am trying to create a website that only shows data, not my narrative or notes. I don't see a way to remove that information. What am I missing? Ed -- *Edward Veal* email: edw...@gm... Cell: 806-445-6867 -------------- next part -------------- An HTML attachment was scrubbed... |
From: <Emy...@ya...> - 2023-08-12 20:04:44
|
A new project to produce copies of offline Gramps manuals from the wiki are in progress. The English baseline tests are mostly complete. So now experiments in localizing copies for other languages are starting. Nederlands/Dutch was chosen as test subject. But we need a team of Dutch translators to help figure out oddities, proofread and learn to use weblate with the scripts. Please join the conversation on the Discourse forum. Gary will spawn a private messaging workgroup and invite participants. https://gramps.discourse.group/t/user-manual-nederlands-language-issues/4000 -------------- next part -------------- An HTML attachment was scrubbed... |
From: Peter F. <pe...@si...> - 2023-08-05 21:26:07
|
On 05/08/2023 10:12, Tim Dudgeon wrote: > I've now come across a need for a system that can track and manage > historical information, of which descendancy is an important part, > but there are other aspects that are equally important, and I've not > found a good way to do this in gramps. Am I missing something or are > there better tools to handle this? A non-Gramps solution would be to use TEI XML. This is a dialect of XML designed explicitly for historical as well as literary markup. > As an example, let's consider the kings and queens of England. It > would be relatively straightforward to create a family tree (or > trees!) to describe the descendancy aspect, but what about the role > or position of monarch. Normally TEI XML is used for creating electronic editions of old texts, but its customisable tagset means it could easily be used to carry a hierarchical descendancy structure as well as all the ancillary information you describe (dates and ranges, timelines, roles, positions, etc) The TEI-L mailing list (te...@li...) is full of a lot of people with historical expertise who can probably get you started. Peter |
From: Nick H. <ni...@gr...> - 2023-08-05 14:40:18
|
On 05/08/2023 10:12, Tim Dudgeon wrote: > As an example, let's consider the kings and queens of England. It > would be relatively straightforward to create a family tree (or > trees!) to describe the descendancy aspect, but what about the role or > position of monarch. In the new timeline view that I am writing, the reigns of monarchs are events. Events are tagged to include them in the timeline. See: https://gramps.discourse.group/t/historical-events-or-facts-into-timelines-with-gramps I'll continue this work after v5.2.0 is released. Nick. |
From: Enno B. <enn...@gm...> - 2023-08-05 14:09:06
|
Hello Tim, > I've now come across a need for a system that can track and manage > historical information, of which descendancy is an important part, but > there are other aspects that are equally important, and I've not found a > good way to do this in gramps. Am I missing something or are there better > tools to handle this? I don't think that you're missing something, and I don't know any better tools either, but your questions reminds me of a Dutch genealogy program module called Haza-Goed. More on that later. > As an example, let's consider the kings and queens of England. It would be > relatively straightforward to create a family tree (or trees!) to describe > the descendancy aspect, but what about the role or position of monarch. And > the role of heir to the throne (prince of wales in England, Dauphin in > France). You would want to be able to create these roles and assign them to > the relevant people for the relevant periods and be able to view the > timeline of the roles as first class citizens, not just buried somewhere > deeply (e.g. an event then the person became king/queen). > Other examples where this would be useful is for presidents, popes, prime > ministers, and many, many others. If you describe it like this, it means that you have people that occupy a position, like King of England, or POTUS, Prime Minister of The Netherlands, vicar of Dibley, etc. etc., and position sounds like location, which is a shared object in Gramps. The POTUS is the prime occupant of the White House, King Charles III is the prime occupant of Buckingham Palace, and a few more locations, and a natural extension of the idea would be that positions like these are also turned into shared objects, so that you can create a timeline for the occupants of the position of POTUS or King of England, etc. And for both, you can also add secretaries, and princes, earls, etc. to a hierarchy. When I visit the Amsterdam archive site on the web, I can already see who lived at my address before I lived there, so I think that the analogy itself is the right one. I see no easy way to work this way in the current version of Gramps, other than really creating locations named after these types of positions. I have an old tree in PAF, for Charlemagne and other famous persons, going back to the time before the book of Genesis, where the author added virtual parents named POTUS, or Farao of Egypt, but I don't really like that trick, because it messes up too many things. Regards, Enno |
From: Enrique <kup...@mu...> - 2023-08-05 12:03:24
|
-- -- Mensaje enviado por Enrique a través de Evolution El sáb, 05-08-2023 a las 11:25 +0000, Jon Smith escribió: > You could use a custom tag and link everyone that lived during their reign. > Not sure that will give you the timeline view you want. It really needs the > Relationship view to be expanded to different types of user-defined > Associations (aka the FAN Club of Elizabeth Shown Mills - Friends, Associates, > Neighbors). RootsMagic added that feature, so did FamilySearch. > > Showing everyone during a particular reign can be very valuable as you go back > and the records get scarce. A little analytics goes a long way! > > Great idea! > ________________________________ > From: Tim Dudgeon <tdu...@gm...> > Sent: Saturday, August 5, 2023 5:12 AM > To: Gra...@li... <Gra...@li...> > Subject: [Gramps-users] handling roles or positions > > I've been using gramps for some time for handling traditional family tree > information, and generally am very happy with it. Keep up the good work! > I've now come across a need for a system that can track and manage > historical information, of which descendancy is an important part, but > there are other aspects that are equally important, and I've not found a > good way to do this in gramps. Am I missing something or are there better > tools to handle this? > As an example, let's consider the kings and queens of England. It would be > relatively straightforward to create a family tree (or trees!) to describe > the descendancy aspect, but what about the role or position of monarch. And > the role of heir to the throne (prince of wales in England, Dauphin in > France). You would want to be able to create these roles and assign them to > the relevant people for the relevant periods and be able to view the > timeline of the roles as first class citizens, not just buried somewhere > deeply (e.g. an event then the person became king/queen). > Other examples where this would be useful is for presidents, popes, prime > ministers, and many, many others. > Would welcome any thoughts on this. > Tim > -------------- next part -------------- > An HTML attachment was scrubbed... > > -- > Gramps-users mailing list > Gra...@li... > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fgramps-users&data=05%7C01%7C%7C11672d02527c454a136e08db95946b02%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638268236923123971%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=hrAcktvnzalrq8r8%2B8v0pGbslGFJhUuyfq6QjS8k8Hk%3D&reserved=0 > <https://lists.sourceforge.net/lists/listinfo/gramps-users> > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgramps-project.org%2F&data=05%7C01%7C%7C11672d02527c454a136e08db95946b02%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638268236923123971%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=u146p1cr3PV52caKd0q0YWCiJ%2FEfiat3JzgVqtyzPco%3D&reserved=0 > <https://gramps-project.org/> > -------------- next part -------------- > An HTML attachment was scrubbed... > See: https://gramps-project.org/wiki/index.php?title=Gramps_5.1_Wiki_Manual_-_Filters#Tag_selection_dialog -------------- next part -------------- An HTML attachment was scrubbed... |
From: Jon S. <jon...@ho...> - 2023-08-05 11:25:36
|
You could use a custom tag and link everyone that lived during their reign. Not sure that will give you the timeline view you want. It really needs the Relationship view to be expanded to different types of user-defined Associations (aka the FAN Club of Elizabeth Shown Mills - Friends, Associates, Neighbors). RootsMagic added that feature, so did FamilySearch. Showing everyone during a particular reign can be very valuable as you go back and the records get scarce. A little analytics goes a long way! Great idea! ________________________________ From: Tim Dudgeon <tdu...@gm...> Sent: Saturday, August 5, 2023 5:12 AM To: Gra...@li... <Gra...@li...> Subject: [Gramps-users] handling roles or positions I've been using gramps for some time for handling traditional family tree information, and generally am very happy with it. Keep up the good work! I've now come across a need for a system that can track and manage historical information, of which descendancy is an important part, but there are other aspects that are equally important, and I've not found a good way to do this in gramps. Am I missing something or are there better tools to handle this? As an example, let's consider the kings and queens of England. It would be relatively straightforward to create a family tree (or trees!) to describe the descendancy aspect, but what about the role or position of monarch. And the role of heir to the throne (prince of wales in England, Dauphin in France). You would want to be able to create these roles and assign them to the relevant people for the relevant periods and be able to view the timeline of the roles as first class citizens, not just buried somewhere deeply (e.g. an event then the person became king/queen). Other examples where this would be useful is for presidents, popes, prime ministers, and many, many others. Would welcome any thoughts on this. Tim -------------- next part -------------- An HTML attachment was scrubbed... -- Gramps-users mailing list Gra...@li... https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fgramps-users&data=05%7C01%7C%7C11672d02527c454a136e08db95946b02%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638268236923123971%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=hrAcktvnzalrq8r8%2B8v0pGbslGFJhUuyfq6QjS8k8Hk%3D&reserved=0<https://lists.sourceforge.net/lists/listinfo/gramps-users> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgramps-project.org%2F&data=05%7C01%7C%7C11672d02527c454a136e08db95946b02%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638268236923123971%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=u146p1cr3PV52caKd0q0YWCiJ%2FEfiat3JzgVqtyzPco%3D&reserved=0<https://gramps-project.org/> -------------- next part -------------- An HTML attachment was scrubbed... |
From: Tim D. <tdu...@gm...> - 2023-08-05 09:12:27
|
I've been using gramps for some time for handling traditional family tree information, and generally am very happy with it. Keep up the good work! I've now come across a need for a system that can track and manage historical information, of which descendancy is an important part, but there are other aspects that are equally important, and I've not found a good way to do this in gramps. Am I missing something or are there better tools to handle this? As an example, let's consider the kings and queens of England. It would be relatively straightforward to create a family tree (or trees!) to describe the descendancy aspect, but what about the role or position of monarch. And the role of heir to the throne (prince of wales in England, Dauphin in France). You would want to be able to create these roles and assign them to the relevant people for the relevant periods and be able to view the timeline of the roles as first class citizens, not just buried somewhere deeply (e.g. an event then the person became king/queen). Other examples where this would be useful is for presidents, popes, prime ministers, and many, many others. Would welcome any thoughts on this. Tim -------------- next part -------------- An HTML attachment was scrubbed... |
From: Nick H. <ni...@gr...> - 2023-08-01 14:21:58
|
Version 5.2.0-beta1, an experimental pre-release. Make sure to backup before you upgrade: https://www.gramps-project.org/wiki/index.php?title=How_to_make_a_backup The key word is experimental! It might be unwise to "upgrade" your main/real Gramps family tree into 5.2.0-beta1. In general, we recommend you make a copy of your family tree instead (typically by doing a "gramps XML" export), then try 5.2.0-beta1 on the copy. (You can keep things really separate by using the GRAMPSHOME environmental variable, if you want.) We are interested in your feedback, especially if you discover any bugs or problems which we haven't noticed. 2023-08-01 Version 5.2.0-beta1 * Highlights * Create new Addon Manager dialog. * Add support for open spans. * Add strikethrough and superscript/subscript support. * Add new gender option of "Other". * Add citations to event references. * Deprecate BSDDB, but allow to be loaded with convert to SQLite. * Add coordinates format with description. Fixes #11248 * Add the possibility of case sensitive/insensitive search. * Add source icon to editor dialogs. Implements #11372 * Make the tab columns resizable. Implements #8767 * Support XDG base directory specification. Fixes #8025 * General * Update README, INSTALL and FAQ files. * Update copyright dates. * Update Creative Commons license version to 4.0. * Minor string fixes. Add or remove whitespace. * Append full stops to ends of sentences. Remove full stops after ellipses. * Spelling fixes. * Many Pylint and other cleanups. * Reports * Birthday and Anniversary Report: Add person ID. * Common calendar on Statistics chart. Fixes #12571 * HourGlass graph: Add option to use genealogical symbols for events. * Statistics chart: Small code improvements. * Calendar report enhancements: * Added symbols for birth, marriage and death. * Added symbols for dead spouse in anniversaries. * Optionally include death dates. * Refactored method `collect_data`. * Added flipped text option to Graphical Report Fan Chart. This option flips the names in generations 2, 3 and 4 that on the bottom half of the fan. * Kinship report: change max number of generations. Fixes #12004 * Add a new primary surname substitution keyword option. * Add option name_format to treedoc. Implements #12136 * Enhance name formats in the genealogytree reports. * Add new output format of "graph" to the tree document generator. * Display leap day anniversaries every year on calendars. * Show index of person in ancestor tree report. * Enable markup in ODF backend. * Relationship Graph: Add option for 'offset parents' Replaces 'use subgraph' option. Fixes #11550, #11494 * Add fanchart option with overhang. By adding an overhang to the fanchart, more space can be used. * Do not round rotation in SVG. When making >8 generation fan charts, the rounding of rotation becomes visible. * Family group report enhancements: * Replace Marriage heading with relationship type. * Remove Husband and Wife headings. These are incorrect for same-sex relationships or when the couple are unmarried. Resolves #11199 * Complete individual report: * Use shorter name to reduce line length. * Add option that allows to use the name of the individual as title. * Calendar: Use the death symbol defined in preferences. * Add descriptions to decendant tree report styles. * Gramplets * Improved Age Stats gramplet: * New Histogram widget. * Extra bucket for ages above maximum. * Automatic scaling to available width. * Image Metadata Gramplet expand metadata support: * Enable showing XMP and IPTC metadata. * Add additional metadata fields that contain tags and text descriptions. * Display thumbnails for XMP-mwg-rs Regions. * Calendar gramplet: Add day names. The first day is defined according to the locale. Fixes #12515 * Allow gramplets to have an orientation dependent layout. Use this for the gallery gramplets. Implements #11527 * Update Welcome gramplet. * Link to translated wiki pages in welcome gramplet. * Add a note gramplet for NoteView. * Show note type in notes gramplet. Also move page number next to forward/back buttons. Implements #12402 * Add Copy All functionality to Ancestor gramplet. * Citations gramplet: Add date, page, and confidence. Fixes #9224 * Change columns order and size. * Sort correctly by date. * Display the event date in the backlinks gramplet. Fixes #12230 * AgeOnDate gramplet: Fix position of input field and button. * Add context menu entries for Gramplet Bar. Link to help for Gramplets and the Gramplet Bar Menu. Issue #10919 * Narrative Web Report * Sort events by date in the individual page. Fixes #12717 * Clarify how to get the API_KEY. Fixes #12646 * Solves some problems. Force place name to be "Full" names. Fixes #12821 * Add noindex for robots. * Lightbox feature. Feature request: #12801 * The latest version of openlayers doesn't work: * 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. * Code simplification. * Add a comment if invalid lat/long. Fixes #12565 * Some fixes to alphabet_navigation. Ensure correct index letters according to normal indexing conventions by using ICU AlphabeticIndex. Fixes #12350 * Change order of Event Reference Notes and Notes. Fixes #12356 * Possible loop with associated people. * Add option to show all places. Fixes #12315 * Don't display media, source ref for unused place. * Backlink gramplet problem if no back references. * Show image on the map only if it was collected. * Show the thumbnail place if already collected. * Add place name to birth and death dates when we use the toggle section. * Possible problem with RTL languages. * Inconsistency between the name of the link to a reference and the name of this reference for an individual. Fixes #12336 * Translation problem + missing events on markers. * Addressbooklist: headers aren't translated. * Missing events for markers + code simplification. * Various fixes to user-visible strings. * Toggle bug for source attribute. * Remove the note type 'Html code' for notes. Fixes #12184 * Add php session_start. Fixes #12135 * Multiple languages for the narrative web and optional other additions * Fix letters in comment: * Insert missing letters in comments. * Terms to upper case (gregorian, javascript). * In cms mode, some inconsistent image links. * Incorrect place index if alternate names. The places page index doesn't show the alternate names used. Fixes #11645 * Description message is not translatable. * Possibility to have more than 2 downloads. By default, I set this to 3 downloads. Fixes #11626 * Add family map to family pages. Adapt css files to have a better look. Fixes #11614 * Set unused media to False by default Fixes #11496 * Center correctly the map in the web page. * Dropmenu doesn't work if only one year. * Add notes to updates and delete empty rows. * References enhancement on place pages. * Convert the years in gregorian calendar. * Enclosed places not correctly sorted. Fixes #11487 * Don't use event links if no event pages + some pylint changes. * Map popup links must be visible for all stylesheet. * Add scrollbar in popup content. * 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 * 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. * Open layers optimizations. * Open layers and link in popup. * Some events missing in popup. * Reference date column too large. * Allow the place title to use the maximum of width . * Shift children from one column, adapt the css files to the new table, and fix some inconsistencies between the source and the css. * Make the drop down menu button size usable. * Incorrect rendering when use of alternate place name . * Removing the unused image heigth option. * Click on image link gives a not found URL. * Allow alternate stylesheets in pages. * Allow urls for images in user css files. * Add popup to manage markers. Fixes #11150 * Add Stamen map. Fixes #5984 * Correct English in narrative web report. * Links in notes not obvious in Narrated Web report. Fixes #12105 * Web Calendar * Have config files for multiple databases. * Best management for the narrative web link. * Use arrows, compress monthname and arrows adapt the css files accordingly. * Use arrows in one day within a year compress monthname and arrows adapt the css files accordingly. * Index go now to the current month. * Year glance + some pylint improvements * Incorrect width size with Mainz css. * Problem with Visually css file. * The table cell is highlighted when hover. * Better rendering for full year at a glance. * better rendering on small devices. * Duplicate marriage. * Incorrect results when divorce event. * Add alternate stylesheets. * Missing death symbol. * Geography * Use path from constants. * Remove redundant class members. * Simplify popup menu builder. * Use Gtk.SeparatorMenuItem instead of empty Gtk.MenuItem. * Change Gtk.MenuItem to Gtk.CheckMenuItem for map providers. * Gramps crashes on import of large KML file. Fixes #11954 * Better management when closing database. * Add two new icons. * Better handling of bad tile path. Fixes #11629 * Add custom tiles provider. Fixes #11416 * GUI * Fix for panes that are unable to be resized. * Backup: Add a modal status popup This is used to prevent the user closing Gramps during a backup. Fixes #12846, #12475, #12538 * Fix ColorButton size in preferences. * Display a tooltip warning if a window saves data immediately. Fixes #12117 * Move privacy column in editor citation tabs. * Add Preferences and Addon Manager toolbar buttons. * Update Tip of the Day entries. * Provide better formatting for the import statistics. Also fix concatenation bug. * Enhance InfoDialog to display simple tables * Add "All supported files" as file type selection. Fixes #12161 * Date input: allow yyyy-mm for iso format. * Add option to hide ages for events after death. * Correct spelling of "vCard" in importer. * Add option to control display format of latitude and longitude. Fixes #11248 * Allow entering place latitude and longitude without space. * Use replacement text for blank surname heading in person tree. * Improve description of regular expressions in filter editor. * Add Back/Forward labels to citation tree view. Fixes #12510 * "Number of Parents" column in Person Views doesn't sum all parent. Fixes #12268 * Symbols enhancement: * Add the possibility to set all default value to a string. * Gui configuration improvement. * Possibility to drag and drop a symbol from the symbol list. * Replace death symbol by buried, cremated or killed symbol depending on the event type. * Fix spelling of "Descendants". Resolves #12535 * Provide an option to "hide" the LDS tab. Implements #3872. * Add possibility to select the dialect of CSV export. * Add Abbreviation column to source and citation selectors. Implements #11710 * Update confirmation message in the export assistant. * Implement calendar quarter dates as date ranges. For example, "Q2 2020" is converted to "between 1 April 2020 and 30 June 2020". * Use a contrasting text color in pedigree view. White text shows up better in boxes with a dark background color. Fixes #11799 * Allow user to set default calendar in date editor. Fixes #11809 * Update Preferences dialog. Clean up of existing Preferences tabs. Implements #12049 * Update address lists. Capitalize postal and phone column headers. * Add Phone/Postal to Addresses tab of Person editor. Fixes #11600 * Fix presumed typo in menu item "Sorts events" should be "Sort events". * Move beta warning into the status bar. * Increase information in database summary text report. Add type counts for events, places, sources, citations, repositories and notes. * In familysidebarfilter, search on each part of name. Fixes #12023 * Add tooltips to sidebar filter 'Find' and 'Reset' buttons. Issue #11783 * Media view: Set new media as active. * Typo on variable name in navigator. Fixes #12039 * Pedigree View: Add Help context menu. Fixes #10919 * EditLink: When changing the link type choose the active object as default. * EditLink: When creating a link, prefer linking persons over places, events, ..., and images. * Allow filter rules to access Family filters. * Add a new person filter rule 'HasAddressText'. * New Remove tag from selected rows functionality. * Add 'HasAttribute' filter rule to repositories, sources and citations. Fixes #9845 * Add tooltips for places in clean input data tool. * Improve CSV import to allow places that are not in enclosed order. Fixes #11407 * Update tags: Translation for menu strings added and escape illegal characters. * Types * Add new note type of "Analysis". * Add Stillbirth as pre-defined event type. Add Stillbirth as a fallback for both Birth and Death events. * Change "death cause" to "cause of death". * Add Godparent as event role. * Gedcom * Implement the GEDCOM tag `_RUFNAME`. * Add round trip Ancestry.com `_APID` tag support. Implements #9925 * Explicitly set birth name in GEDCOM export. * Fix GEDCOM import/export DATE/TIME creep by UTC offset. * Improvements in the English manpage * Various grammar improvements. * Use HTTPS URLs. * Use Unicode trademarks and arrows. * Improve syntax. * Translation * Updated translations: ar, bg, br, ca, cs, da, de_AT, de, el, en_GB, eo, es, fa, fi, fr, ga, gl, he, hr, hu, id, is, it, ja, mk, nb, nl, nn, pl, pt_BR, pt_PT, ru, sk, sl, sr, sv, ta, tr, uk, vi, zh_CN, zh_HK. * Support msgctxt in po files instead of a vertical bar in the msgid. * Update check_po to support msgctxt strings. * Add JJ/MM/AAAA French date format. * Add header to XML fragments file. A header containing a charset is required by xgettext. * Holidays: Sort countries alphabetically. * Add Russian holidays. * Add Italian holidays. * Add Catalan holidays. * Add Turkish holidays. * Fix Russian calendar unit test. The translation of "Julian" is hardcoded and the test and will fail if the translation is updated. * Give consistency to short months in Spanish. * Fix unit tests requiring English locale. * Fix invalid Persian calendar dates. Fixes #12576 * Add Turkish Relationship Calculator. * Add translation context to ChildRefType. Needed for Russian. * New de_AT translation Based on the de translation. * Add German date format option for 'numeric date with leading zeros'. * Add context to place name strings. Needed for Russian translation. * Remove translatable attribute from "%s" strings. * Add "Translator" tag to comments intended for translators. * Convert old translator tags. Change the old tags "translator" and "TRANSLATOR" to "Translator". * Only extract comments with the "Translator" tag. Previously all comments before a translated string were extracted. * Remove old translation context separators. * Fix month lexeme translations for da, fi, sl and sv. * Merge translation changes from the gramps51 converting the files to the new msgctxt format. * Fix fatal errors in po files. * German relation calculator fixed issue if more then 24 generations between the two people. * Replace intltool with gettext tools. The build now requires gettext v0.19.7 or above. * Removed obsolete files: gramps.applications, gramps.keys, gramps.mime * Created ITS rules for holidays.xml and tips.xml files. * Included ITS files for shared-mime-info from a gettext v0.20.2 installation. * New datehandler and relationship calculator for de_AT. * Corrected a few relationships in pt relationship calculator. * Locale * Extract win32 localatiztion to a new file win32locale.py. * Fix minor PyLint complaints. * Fix PyLint complaints about import statements. * Remove deprecated locale.getdefaultlocale and locale.format functions. * Extract translation classes from grampslocale.py * Correct remaining pylint issues in maclocale.py * Fix shadowed variables. * Fix unnecessary parens. * Fix unused variables. * Fix pylint line-too-long. * Remove unused numeric. * Remove unused currency. * Use msgctxt in Lexeme docstring. * Technical * Increase minimum version requirements - Python: 3.8 Gtk: 3.24 * Migrate code style to Black. * Use GitHub Actions to run continuous integration checks. * Attempt to derive the resource path from the package path. Intended to allow a Gramps core package to be created as a wheel and installed via pip. * Use setup from setuptools to allow creation of python wheels. * Port from `GtkSpell` to `Gspell`. * Add source files for Windows AIO. Remove old Windows directory. * Add support for thumbnailer plugins. * Add support for CITE plugins Provide a single default plugin that replicates the existing functionality. * Allow custom undo managers in database plugins. * Add `bookmark-list-changed` signal. * Remove redundant code since Gtk 3.24 required. * Fix deprecation of Gtk positional arguments. * Fix Gtk deprecation `Menu.set_title` * Fix Gtk deprecation `ScrolledWindow.add_with_viewport` * Fix `GObject.PARAM_READWRITE deprecation. * Fix deprecation `GObject.GError` -> `GLib.GError` * Fix Gtk deprecation `Widget.reparent`. * Fix Gtk deprecation` `Widget.set_padding` * Fix deprecation on `Gtk.Widget.override_font` and `modify_font` * Fix garbage collection issue in ConfigManager. * Fix garbage collection issue in UIManager. * Fix garbage collection issue in Callback. * Color values in the range [0-1] are supposed to be floats See `rgb_to_hex`. * Save and restore standard streams. * Close standard streams on exit. Prevents the warning: "ResourceWarning: unclosed file". * Replace os.system with subprocess.call in setup.py * Add extra plugin properties: * Add 'Experimental' and 'Beta' status options. * Add audience property with possible values: 'All', 'Developer' and 'Expert'. * Add maintainers and maintainers email properties. * Add `requires_mod`, `requires_gi` and `requires_exe` properties to specify addon requirements. * Allow help url for all plugin types. * Add stock_category_icon support. * Replace deprecated imp by importlib. * CI: Upgrade actions/checkout to v3. * Update Gramps CI workflow to run on Ubuntu 20.04 Ubuntu 18.04 became fully unsupported on 1 Dec 2022. * Fix package installation failures in CI. * Gallery tabs: Avoid signal warning during editor clean up. The signal no longer exists to disconnect from at this point. * Fix display warnings in unit tests Attemps to get rid of the follow warning: "Unable to init server: Could not connect: Connection refused". * Add .venv environments to .gitignore * Migrate build from distutils to setuptools. Distutils is deprecated with removal planned for Python 3.12. * Remove options and disables that pylint no longer uses. * Enable `file:///` URI paths for addons location. * Use ObjEntry to select a person as an association. * ConfigManager: Add support for embedding comments in ini header. * Fix incorrect title of event schema `attribute_list`. * Test: Use temporary directory to test bsddb. * Remove unused constant `ENV_DIR`. * Add gramps_id to repository & note text data lists. * Add unit test for `python3 -m gramps`. * Add `__main__.py` * Skip inspect.stack also when debug logging is disabled. * Wrap inspect.stack in if `__debug__`. * Replace TEMP_DIR by tempfile object. * Remove `xdg-utils` dependency. * Fix application id. * Use reverse-DNS scheme for mime file, application icon, appdata + desktop. * Move MIME icons together with other hicolor icons. This way, all the hicolor icons are logically in the same place. * Simplify looping. Index based loops are mapped to their Pythonic equalivant. * Fix `Place.get_text_data_child_list` * Fix Check&Repair progress meter for Duplicated Gramps_ID check. * Fix no_magic for dbapi. * Cairodoc: Correct enumerations unpacking. * Rework primary object Deletes in views. * Faster Multiple Event delete. * Faster Multiple Person Delete. * Speed up Event, Media, and Repo reference editors. * Speed up Place Reference Editor and Listview for enclose place. Fixes #11531 * Speed up Event displaytab and gramplet. * Fix StatusBar for potential HandleError. * Smoother progress for Rebuid reference maps/secondary indices. * Skip `test3b_delete_tree_constraint` if `$HOME` is a subdirectory of `/tmp`. Fixes #12577. * Remove the "database is closed" warning. Fixes #12492 * Note LINK support for merge of other objects. * Note LINK support for deletes of other objects. * Support Note LINKS as backlinks. * mac modules: Replace git with https in github URI They don't accept unauthenticated git connections anymore. * Fix datehandlers for round trip. Parsers should be able to parse the output from the displayer. * Enhance date handler tests: * Add tests for all languages with a custom date handler. * Remove some months so that the tests run quicker. * Enhance Date Parser Display Test debug tool. Test for both Julian and Gregorian dates. * Check & Repair: search and fix bad "links" in `StyledTextTags`. Issue #11855 * Update `shared-mime-info` for `application/x-geneweb` and `application/x-gedcom`. * Fix tags in shared mime info file. With the switch from intltool to gettext underscores became obsolete. * Update `_pythonmime.py` When editing a Media image, display TIFF image or PNG image instead of Unknown. * Make `gramps -v` consistent with Prerequisites Checker. Issue #12770 * Fix `EditEventRef`, `EditPlaceRef`, `EditMediaRef`, `EditRepoRef` for improperly saving objects in their object lists. Fixes #11917, #11933 * Autobackup: Add delay after wake from sleep/hibernate to allow time for system to settle. Fixes #10953 * Autobackup only if new commits since last autobackup in session. * Fix images: 22x22 to 24x24 Real picture's size from images/hicolor/24x24/actions old size: 22x22 72dpi or 90dpi now: 24x24 72dpi. * Use XDG pictures directory as the default media path. This is a better default for our Flatpak distribution. Fixes #12217. * Add place name to place in geneweb import. Fixes #12710 * Argparser: * Refactor error construction into a common method. * Simplify handling of getops error. * Add unit test for handling getopt error. * Name displayer: * Correct continuation line unaligned for hanging indent. * Remove unused imports. * Correct the assumed order of the name formats. * Use list comprehension for name format list. * Simplify sorting in `get_name_format`. * Add unit tests for methods relying on `name_formats`. * Add test coverage for `get_name_format`. * Update Appdata to pass validation: * Fix tags. With the switch from intltool to gettext underscores became obsolete. * Add content-rating information. * Add link for translators. * Add release information. * Add translation domain. * Make appdata summary consistent with desktop comment. * Avoid using deprecated license identifier. * Tidy up tag order. * merge_ref_test: Tests update for Note rework. * Fix MultiSelectDialog for two issues. * Fix unit test for check & repair tool. * Limit print statement by using logging module `python3 Gramps.py -d "gui.uimanager"`. * Image magic: add bmp and tiff + Readme, exception if file not found. * Fix db corrupted error message to make it apply to all db types. Fixes #12242 * Test: No need to check for mock support with Python 3.3+ * Install application icons into correct directories. * Replace obsolete `file()` -> `open()`. * Remove non-existent old attribute personal for an event. * Use the callback parameter passed to `EditEvent.__init__` by passing it to `EditPrimary.__init__`. * For all types of EditPrimary window, consistently call `self._do_close()` before `self.callback()`, during `save()`. * EditRepository now stores the callback passed to `__init__` and calls it during `save()`. * Better code quality for within area rule. * Add missing `get_number_of_citations` method. You can obtain Gramps 5.2.0-beta1 from the GitHub release page: https://github.com/gramps-project/gramps/releases/tag/v5.2.0-beta1 |