You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(35) |
Jun
(11) |
Jul
(41) |
Aug
(96) |
Sep
(29) |
Oct
(44) |
Nov
(70) |
Dec
(61) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(126) |
Feb
(31) |
Mar
(64) |
Apr
(84) |
May
(57) |
Jun
(56) |
Jul
(20) |
Aug
(23) |
Sep
(31) |
Oct
(19) |
Nov
(60) |
Dec
(34) |
2003 |
Jan
(30) |
Feb
(61) |
Mar
(32) |
Apr
(30) |
May
(78) |
Jun
(55) |
Jul
(111) |
Aug
(108) |
Sep
(104) |
Oct
(98) |
Nov
(92) |
Dec
(73) |
2004 |
Jan
(71) |
Feb
(70) |
Mar
(68) |
Apr
(40) |
May
(118) |
Jun
(51) |
Jul
(71) |
Aug
(251) |
Sep
(77) |
Oct
(155) |
Nov
(74) |
Dec
(57) |
2005 |
Jan
(183) |
Feb
(94) |
Mar
(170) |
Apr
(242) |
May
(233) |
Jun
(42) |
Jul
(69) |
Aug
(70) |
Sep
(99) |
Oct
(60) |
Nov
(65) |
Dec
(210) |
2006 |
Jan
(169) |
Feb
(99) |
Mar
(31) |
Apr
(179) |
May
(142) |
Jun
(72) |
Jul
(131) |
Aug
(98) |
Sep
(110) |
Oct
(189) |
Nov
(262) |
Dec
(207) |
2007 |
Jan
(376) |
Feb
(255) |
Mar
(168) |
Apr
(174) |
May
(167) |
Jun
(192) |
Jul
(197) |
Aug
(171) |
Sep
(307) |
Oct
(572) |
Nov
(454) |
Dec
(471) |
2008 |
Jan
(707) |
Feb
(365) |
Mar
(464) |
Apr
(410) |
May
(251) |
Jun
(142) |
Jul
(112) |
Aug
(143) |
Sep
(94) |
Oct
(280) |
Nov
(337) |
Dec
(232) |
2009 |
Jan
(508) |
Feb
(491) |
Mar
(363) |
Apr
(280) |
May
(186) |
Jun
(250) |
Jul
(231) |
Aug
(487) |
Sep
(189) |
Oct
(344) |
Nov
(456) |
Dec
(439) |
2010 |
Jan
(514) |
Feb
(725) |
Mar
(591) |
Apr
(256) |
May
(209) |
Jun
(75) |
Jul
(118) |
Aug
(248) |
Sep
(230) |
Oct
(393) |
Nov
(368) |
Dec
(276) |
2011 |
Jan
(457) |
Feb
(308) |
Mar
(358) |
Apr
(277) |
May
(333) |
Jun
(320) |
Jul
(198) |
Aug
(186) |
Sep
(87) |
Oct
(238) |
Nov
(123) |
Dec
(129) |
2012 |
Jan
(127) |
Feb
(182) |
Mar
(208) |
Apr
(134) |
May
(230) |
Jun
(138) |
Jul
(126) |
Aug
(176) |
Sep
(231) |
Oct
(235) |
Nov
(164) |
Dec
(219) |
2013 |
Jan
(316) |
Feb
(371) |
Mar
(393) |
Apr
(165) |
May
(321) |
Jun
(301) |
Jul
(124) |
Aug
(183) |
Sep
(191) |
Oct
(285) |
Nov
(172) |
Dec
(196) |
2014 |
Jan
(392) |
Feb
(284) |
Mar
(134) |
Apr
(206) |
May
(123) |
Jun
(115) |
Jul
(41) |
Aug
(157) |
Sep
(122) |
Oct
(124) |
Nov
(63) |
Dec
(56) |
2015 |
Jan
(249) |
Feb
(335) |
Mar
(277) |
Apr
(98) |
May
(274) |
Jun
(214) |
Jul
(142) |
Aug
(240) |
Sep
(57) |
Oct
(77) |
Nov
(18) |
Dec
(171) |
2016 |
Jan
(217) |
Feb
(167) |
Mar
(62) |
Apr
(180) |
May
(270) |
Jun
(86) |
Jul
(112) |
Aug
(50) |
Sep
(57) |
Oct
(91) |
Nov
(62) |
Dec
(101) |
2017 |
Jan
(116) |
Feb
(115) |
Mar
(85) |
Apr
(35) |
May
(54) |
Jun
(123) |
Jul
(65) |
Aug
(35) |
Sep
(103) |
Oct
(28) |
Nov
(21) |
Dec
(7) |
2018 |
Jan
(27) |
Feb
(64) |
Mar
(42) |
Apr
(72) |
May
(49) |
Jun
(24) |
Jul
(18) |
Aug
(4) |
Sep
(9) |
Oct
(39) |
Nov
(11) |
Dec
(45) |
2019 |
Jan
(35) |
Feb
(24) |
Mar
(28) |
Apr
(38) |
May
(16) |
Jun
(41) |
Jul
|
Aug
(49) |
Sep
(41) |
Oct
(22) |
Nov
(15) |
Dec
(32) |
2020 |
Jan
(61) |
Feb
(3) |
Mar
(31) |
Apr
(29) |
May
(38) |
Jun
(16) |
Jul
(26) |
Aug
(87) |
Sep
(12) |
Oct
(4) |
Nov
(14) |
Dec
(5) |
2021 |
Jan
(3) |
Feb
(4) |
Mar
(26) |
Apr
(2) |
May
(55) |
Jun
(64) |
Jul
(96) |
Aug
(71) |
Sep
(1) |
Oct
(2) |
Nov
(17) |
Dec
(5) |
2022 |
Jan
(23) |
Feb
(22) |
Mar
(9) |
Apr
(7) |
May
(8) |
Jun
(6) |
Jul
(2) |
Aug
|
Sep
(14) |
Oct
(10) |
Nov
(1) |
Dec
(10) |
2023 |
Jan
(3) |
Feb
|
Mar
|
Apr
(34) |
May
(14) |
Jun
(25) |
Jul
(10) |
Aug
(13) |
Sep
|
Oct
|
Nov
(2) |
Dec
(7) |
2024 |
Jan
(1) |
Feb
(23) |
Mar
(33) |
Apr
(19) |
May
(5) |
Jun
(46) |
Jul
(2) |
Aug
(7) |
Sep
(6) |
Oct
|
Nov
|
Dec
|
From: Don A. <don...@co...> - 2005-09-01 19:41:20
|
Martin Hawlisch and I were looking at the status of some of our translations using the new check_po tool that I wrote this week. It has shown several problem areas, but in particular it shows that some of the translations are significantly out of date, probably to the point to where we really cannot claim support of these languages anymore. The current status is below. LANG Total Untranslated Coverage ====== ===== ============ ======== de 2332 0 100.00% fi 2332 3 99.87% ru 2332 40 98.28% cs 2332 71 96.96% sv 2332 69 97.04% nb 2332 81 96.53% no 2332 81 96.53% es 2332 115 95.07% da 2332 141 93.95% nl 2332 146 93.74% fr 2332 170 92.71% hu 2332 335 85.63% pt_BR 2332 335 85.63% it 2332 361 84.52% eo 2332 364 84.39% ro 2332 831 64.37% pl 2332 1379 40.87% zh_CN 2332 1700 27.10% As you can seen, we have several translations that have less the 70% coverage. What I do not know is, at what point are we better off not shipping a translation? Do we need to make the hard decision to say that we are dropping translations? Or do we keep the translations, but not claim that we support them? It looks like pl and zh_CN are probably not all that usable anymore. Any advice from our users would be helpful here. Thanks. Don |
From: Don A. <don...@co...> - 2005-09-01 11:48:22
|
We've been having problems with SourceForge's CVS server over the past couple of weeks. It goes offline everyone once in a while. However, it seems to be back up now. Don On Thu, 2005-09-01 at 08:40 +0200, Tieum wrote: > Hello, > I am unable to update from cvs: >=20 > cvs.sourceforge.net: Connection timed out > cvs [update aborted]: end of file from server (consult above messages if = any) >=20 >=20 > Matthieu --=20 Don Allingham <don...@co...> |
From: Tieum <tie...@fr...> - 2005-09-01 06:41:06
|
Hello, I am unable to update from cvs: cvs.sourceforge.net: Connection timed out cvs [update aborted]: end of file from server (consult above messages if any) Matthieu |
From: Don A. <don...@co...> - 2005-09-01 01:00:29
|
Actually, I already checked that one in. :-) Don On Thu, 2005-09-01 at 04:33 +0400, Alexandre Prokoudine wrote: > On 9/1/05, Don Allingham <don...@co...> wrote: >=20 > > So for example, running on the ru.po file (Russian translation) > >=20 > > dona@wallace:~/gramps20/src/po$ ./check_po ru.po > > Total: 2332 > > Untranslated: 40 > > %s mismatches: 0 > > %()s mismatches: 1 > > %() missing s/d: 0 > > Coverage: 98.28% >=20 > Okay, okay, I got it, I'll fix it :) >=20 > Now seriously, thank you for this automation script. It sounds like a > real time saver. >=20 > Alexandre >=20 >=20 > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practic= es > Agile & Plan-Driven Development * Managing Projects & Teams * Testing & Q= A > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel >=20 --=20 Don Allingham http://don.allingham.org |
From: Alexandre P. <ale...@gm...> - 2005-09-01 00:33:11
|
On 9/1/05, Don Allingham <don...@co...> wrote: > So for example, running on the ru.po file (Russian translation) >=20 > dona@wallace:~/gramps20/src/po$ ./check_po ru.po > Total: 2332 > Untranslated: 40 > %s mismatches: 0 > %()s mismatches: 1 > %() missing s/d: 0 > Coverage: 98.28% Okay, okay, I got it, I'll fix it :) Now seriously, thank you for this automation script. It sounds like a real time saver. Alexandre |
From: Don A. <don...@co...> - 2005-09-01 00:14:20
|
I've added a new script in the src/po directory to help translators look for error in their .po files. To run (in the src/po directory): ./check_po <pofile>=20 This program checks for untranslated strings, %s mismatches, named %()s mismatches, and missing d or s at the end of a %(). So for example, running on the ru.po file (Russian translation) dona@wallace:~/gramps20/src/po$ ./check_po ru.po Total: 2332 Untranslated: 40 %s mismatches: 0 %()s mismatches: 1 %() missing s/d: 0 Coverage: 98.28% -------- %()s mismatches ------------ '%(event_name)s: ' : '%(name_event)s: ' --=20 Don Allingham http://don.allingham.org |
From: Don A. <don...@co...> - 2005-08-31 18:49:14
|
On 08/31/2005 12:54:38 PM, Eero Tamminen wrote: > I just tested latest CVS and the same time made Finnish translation > up to date. Thanks for the translation update. > > > > Question: > > > > What's the difference between system filters and custom > filters? > > > > Both of these menu items bring up the same user defined filters > > > > editor dialog and system filters are not mentioned in the > > > > documentation. > > Alex? Alex is the best person to answer this. We've discussed removing the system filters, but we have not done it yet. Right now, Alex is on a cross country journey moving from Minnesota to San Fransisco, driving a 24 foot truck and towing a car behind it, battling the winds associated the northern states. So, it might take a few days for an answer. Alex can correct me if I'm wrong, but I think that the system filters where supposed to be system wide filters that could be defined for all users of a system, while custom filters are specific to each user. I think we've come to the conclusion that the system filters will probably never be used. > Btw. Now when Gramps starts, it outputs the following: > --------- > Spell.py: No module named gtkspell If you install the gnome-python-extras package (or what ever your distribution likes to call it), this message will go away, and a spelling checker is enabled on all note dialogs (you can disable this). > WARNING: Invalid number of arguments in filter 'test2'! > --------- > I guess this is harmless? Yes. The fix to the filter problem you reported was removing an unnecessary argument that should not have been passed. This is just a warning letting you know that the filter is a bit out of date. The filter is now smart enough to ignore the unnecessary parameter. Don |
From: Eero T. <eer...@ne...> - 2005-08-31 18:36:53
|
Hi, On Tuesday 30 August 2005 07:11, Don Allingham wrote: > These should be fixed in CVS now. Thanks! I just tested latest CVS and the same time made Finnish translation up to date. > > > * It seems that the filter radio button "Exactly one rule must apply" > > > doesn't work properly. If I have just one rule (meaning that the > > > radio button selection shouldn't affect the selection), switching > > > from the other options to the "Exactly one rule must apply" will > > > change what is selected. > > > > This is still broken. For example: > > - Create a filter with one rule selecting the ancestors filter > > for Edwin Michael Smith > > - With all rules apply radiobutton selected > > - Get back to filter list and test the filter > > -> results look OK > > - Change the filter to Exactly one rule must apply radiobutton > > - Get back to filter list and test the filter > > -> results contain almost all people in the database > > Results should be the same. With only one rule the radiobuttons > > should have no effect. Verified. > > > * If I use a filter taking another filter as parameter, for example > > > by creating following filters: > > > 1. One person: with rule "People with <ID>" (with some person) > > > 2. His descendents: with rule "Descendants of <filter> match" (with > > > above filter given as parameter) > > > And then try either to test or use 2), I get the following backtrace: > > > ------- > > > Traceback (most recent call last): > > > File "/home/eero/garnome/share/gramps/plugins/FilterEditor.py", > > > line 423, in test_clicked > > > handle_list = > > > filt.apply(self.db,self.db.get_person_handles(sort_handles=False)) > > > File "/home/eero/garnome/share/gramps/GenericFilter.py", line 2015, > > > in apply > > > rule.prepare(db) > > > File "/home/eero/garnome/share/gramps/GenericFilter.py", line 440, > > > in prepare > > > filt = MatchesFilter(self.list) > > > File "/home/eero/garnome/share/gramps/GenericFilter.py", line 96, > > > in __init__ > > > self.set_list(list) > > > File "/home/eero/garnome/share/gramps/GenericFilter.py", line 106, > > > in set_list > > > assert len(list) == len(self.labels), \ > > > AssertionError: Number of arguments does not match number of labels. > > > list: [u'One person', u'1'] > > > labels: ['Filter name:'] > > > -------- Verified. > > > Question: > > > What's the difference between system filters and custom filters? > > > Both of these menu items bring up the same user defined filters > > > editor dialog and system filters are not mentioned in the > > > documentation. Alex? > > > Btw. the filter names in the documentation on Gramps site don't > > > anymore match the names in Gramps (I think they are the old names > > > without angle brackets). > > > > > > I also noticed that the filter names are a bit misleading. For > > > example filter "Descendant family members of <person>" matches also > > > the <person> and his/her spouse, not just their descendents. > > > > I noticed also following when I closed the filter editor dialog from > > the window titlebar close button: > > (gramps:11101): Gtk-CRITICAL **: file gtkcellview.c: line 707 > > (gtk_cell_view_cell_layout_clear_attributes): assertion `info != NULL' > > failed > > > > (this might be because of my pretty old pygtk version though.) Btw. Now when Gramps starts, it outputs the following: --------- Spell.py: No module named gtkspell WARNING: Invalid number of arguments in filter 'test2'! --------- I guess this is harmless? - Eero |
From: Martin H. <Mar...@gm...> - 2005-08-31 09:40:13
|
Hi Frode, the text in <> brackets is used in the user-visible name for filters and should not be used programmably. They are just there to tell the user that the filter uses that kind of other object to be functional. You can translate this without problems. Cheers, Martin. > Von: Frode Jemtland <fro...@sk...> > Betreff: Re: [Gramps-devel] String freeze for 2.0.7 > There are a lot of strings including words in the <> brackets. (A list > from > another posting is included at the end of this mail.) Inside these > brackets > are <filter>, <person>, <name>, <event> and more. I thought these "words" > was > going to be replaced in some code, so I haven't translated them. I have > included them in the translation, "as is". In the same way that I did > with variables starting with a %. > > Tuesday 17. May 2005 23:13, wrote Alex Roitman: > > Relationship path between <persons> > > Descendants of <person> > > Descendants of <filter> match -- GMX DSL = Maximale Leistung zum minimalen Preis! 2000 MB nur 2,99, Flatrate ab 4,99 Euro/Monat: http://www.gmx.net/de/go/dsl |
From: Frode J. <fro...@sk...> - 2005-08-31 09:28:29
|
Tuesday 30. August 2005 02:51, wrote Don Allingham: > We've entered a string freeze for the 2.0.7 release. I've updated the > template.po for translations. Since the goal is to get the release out > on Sunday, please try to have your translations done be Saturday night. > > Few strings should have changed between 2.0.6 and 2.0.6, so hopefully it > won't be too much of an effort. Hi. I have started to work on the translation to Norwegian, and I found that I must have misunderstood something, (or all of the other translators has misunderstood this.... ;) ) There are a lot of strings including words in the <> brackets. (A list from another posting is included at the end of this mail.) Inside these brackets are <filter>, <person>, <name>, <event> and more. I thought these "words" was going to be replaced in some code, so I haven't translated them. I have included them in the translation, "as is". In the same way that I did with variables starting with a %. I see that the string "People with the personal <event>" the <event> tag has been translated to <Ereignis> in de.po, <tapahtuma> in fi, missing in fr, and more... while I have kept the <event>. Should I also translate this, or do that break some program code/autoreplace ? Tuesday 17. May 2005 23:13, wrote Alex Roitman: > Relationship path between <persons> > Descendants of <person> > Descendants of <filter> match > Descendants of <person> not more than <N> generations away > Descendants of <person> at least <N> generations away > Children of <filter> match > Siblings of <filter> match > Descendant family members of <person> > Ancestor of <person> > Ancestors of <filter> match > Ancestors of <person> not more than <N> generations away > Ancestors of <person> at least <N> generations away > Parents of <filter> match > People with a common ancestor with <person> > People with a common ancestor with <filter> match > People matching the <name> > People matching the <filter> > Spouses of <filter> match -- -Frode "Reality is that which, when you stop believing in it, doesn't go away". -- Philip K. Dick Petition for "World of Warcraft" on Linux: http://www.blizzpub.net/petition/ |
From: Don A. <don...@co...> - 2005-08-30 04:12:14
|
These should be fixed in CVS now. Don On Mon, 2005-08-29 at 23:45 +0300, Eero Tamminen wrote: > Hi, >=20 > I re-tested these with today's Gramps CVS version. >=20 > On Wednesday 17 August 2005 00:34, Eero Tamminen wrote: > > Bugs: > > > > * It seems that the filter radio button "Exactly one rule must apply" > > doesn't work properly. If I have just one rule (meaning that the > > radio button selection shouldn't affect the selection), switching from > > the other options to the "Exactly one rule must apply" will change what > > is selected. >=20 > This is still broken. For example: > - Create a filter with one rule selecting the ancestors filter > for Edwin Michael Smith > - With all rules apply radiobutton selected > - Get back to filter list and test the filter > -> results look OK > - Change the filter to Exactly one rule must apply radiobutton > - Get back to filter list and test the filter > -> results contain almost all people in the database > Results should be the same. With only one rule the radiobuttons > should have no effect. >=20 >=20 > > * If I use a filter taking another filter as parameter, for example by > > creating following filters: > > 1. One person: with rule "People with <ID>" (with some person)=20 > > 2. His descendents: with rule "Descendants of <filter> match" (with abo= ve > > filter given as parameter) > > And then try either to test or use 2), I get the following backtrace: > > ------- > > Traceback (most recent call last): > > File "/home/eero/garnome/share/gramps/plugins/FilterEditor.py", line > > 423, in test_clicked > > handle_list =3D > > filt.apply(self.db,self.db.get_person_handles(sort_handles=3DFalse)) > > File "/home/eero/garnome/share/gramps/GenericFilter.py", line 2015, i= n > > apply > > rule.prepare(db) > > File "/home/eero/garnome/share/gramps/GenericFilter.py", line 440, in > > prepare > > filt =3D MatchesFilter(self.list) > > File "/home/eero/garnome/share/gramps/GenericFilter.py", line 96, in > > __init__ > > self.set_list(list) > > File "/home/eero/garnome/share/gramps/GenericFilter.py", line 106, in > > set_list > > assert len(list) =3D=3D len(self.labels), \ > > AssertionError: Number of arguments does not match number of labels. > > list: [u'One person', u'1'] > > labels: ['Filter name:'] > > -------- >=20 > This bug is also still there. >=20 >=20 > > Question: > > What's the difference between system filters and custom filters? > > Both of these menu items bring up the same user defined filters > > editor dialog and system filters are not mentioned in the documentation= . > > > > > > Btw. the filter names in the documentation on Gramps site don't anymore > > match the names in Gramps (I think they are the old names without angle > > brackets). > > > > I also noticed that the filter names are a bit misleading. For exampl= e > > filter "Descendant family members of <person>" matches also the > > <person> and his/her spouse, not just their descendents. >=20 >=20 > I noticed also following when I closed the filter editor dialog from the > window titlebar close button: > (gramps:11101): Gtk-CRITICAL **: file gtkcellview.c: line 707=20 > (gtk_cell_view_cell_layout_clear_attributes): assertion `info !=3D NULL'=20 > failed >=20 > (this might be because of my pretty old pygtk version though.) >=20 >=20 > - Eero >=20 >=20 > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practic= es > Agile & Plan-Driven Development * Managing Projects & Teams * Testing & Q= A > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel >=20 --=20 Don Allingham http://don.allingham.org |
From: Charles R. D. <de...@ro...> - 2005-08-30 01:14:11
|
Don Allingham wrote: > We've entered a string freeze for the 2.0.7 release. I've updated the > template.po for translations. Since the goal is to get the release out > on Sunday, please try to have your translations done be Saturday night. I'm looking forward to 2.0.7 for the bug fixes to the great new narrative web site. I've got my new redesigned site ready to go. Just waiting for the bug fix for the bad links to the individuals from the surname page. You people did a fantastic job with this. Thanks for all your hard work. For a comparison, my current gramps 1.x site is at http://www.dennett.org/genealogy. The new 2.x site can be previewed at http://www.dennett.org/genealogy2. Once 2.0.7 is out the new site will be at the original URL. I've made it portable so all I have to do is move the original directory out of the way and put the new one in its place. Charlie |
From: Don A. <don...@co...> - 2005-08-30 00:52:28
|
We've entered a string freeze for the 2.0.7 release. I've updated the template.po for translations. Since the goal is to get the release out on Sunday, please try to have your translations done be Saturday night. Few strings should have changed between 2.0.6 and 2.0.6, so hopefully it won't be too much of an effort. Don --=20 Don Allingham http://don.allingham.org |
From: Don A. <don...@co...> - 2005-08-29 21:43:36
|
Eero, These problems are still there simply because I have not had the time to work on them yet. Right now, we are short handed, since Alex is in the process of moving across the country, and my available time has been reduced lately. The bug list is long, but I am trying to work through the list. Unfortunately, items are being added to the list faster than I can eliminate them. In all honesty, right now, I am completely overwhelmed with bug reports. It would help if you would enter these into the gramps bug tracker at sourceforge. This would help me prioritize the issues and to make sure that they do not fall through the cracks. Don Eero Tamminen wrote: > Hi, > > I re-tested these with today's Gramps CVS version. > > On Wednesday 17 August 2005 00:34, Eero Tamminen wrote: > >>Bugs: >> >>* It seems that the filter radio button "Exactly one rule must apply" >> doesn't work properly. If I have just one rule (meaning that the >>radio button selection shouldn't affect the selection), switching from >>the other options to the "Exactly one rule must apply" will change what >>is selected. > > > This is still broken. For example: > - Create a filter with one rule selecting the ancestors filter > for Edwin Michael Smith > - With all rules apply radiobutton selected > - Get back to filter list and test the filter > -> results look OK > - Change the filter to Exactly one rule must apply radiobutton > - Get back to filter list and test the filter > -> results contain almost all people in the database > Results should be the same. With only one rule the radiobuttons > should have no effect. > > > >>* If I use a filter taking another filter as parameter, for example by >>creating following filters: >>1. One person: with rule "People with <ID>" (with some person) >>2. His descendents: with rule "Descendants of <filter> match" (with above >> filter given as parameter) >>And then try either to test or use 2), I get the following backtrace: >>------- >> Traceback (most recent call last): >> File "/home/eero/garnome/share/gramps/plugins/FilterEditor.py", line >>423, in test_clicked >> handle_list = >>filt.apply(self.db,self.db.get_person_handles(sort_handles=False)) >> File "/home/eero/garnome/share/gramps/GenericFilter.py", line 2015, in >>apply >> rule.prepare(db) >> File "/home/eero/garnome/share/gramps/GenericFilter.py", line 440, in >>prepare >> filt = MatchesFilter(self.list) >> File "/home/eero/garnome/share/gramps/GenericFilter.py", line 96, in >>__init__ >> self.set_list(list) >> File "/home/eero/garnome/share/gramps/GenericFilter.py", line 106, in >>set_list >> assert len(list) == len(self.labels), \ >>AssertionError: Number of arguments does not match number of labels. >>list: [u'One person', u'1'] >>labels: ['Filter name:'] >>-------- > > > This bug is also still there. > > > >>Question: >>What's the difference between system filters and custom filters? >>Both of these menu items bring up the same user defined filters >>editor dialog and system filters are not mentioned in the documentation. >> >> >>Btw. the filter names in the documentation on Gramps site don't anymore >>match the names in Gramps (I think they are the old names without angle >>brackets). >> >>I also noticed that the filter names are a bit misleading. For example >>filter "Descendant family members of <person>" matches also the >><person> and his/her spouse, not just their descendents. > > > > I noticed also following when I closed the filter editor dialog from the > window titlebar close button: > (gramps:11101): Gtk-CRITICAL **: file gtkcellview.c: line 707 > (gtk_cell_view_cell_layout_clear_attributes): assertion `info != NULL' > failed > > (this might be because of my pretty old pygtk version though.) > > > - Eero > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices > Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |
From: Eero T. <eer...@ne...> - 2005-08-29 20:28:04
|
Hi, I re-tested these with today's Gramps CVS version. On Wednesday 17 August 2005 00:34, Eero Tamminen wrote: > Bugs: > > * It seems that the filter radio button "Exactly one rule must apply" > doesn't work properly. If I have just one rule (meaning that the > radio button selection shouldn't affect the selection), switching from > the other options to the "Exactly one rule must apply" will change what > is selected. This is still broken. For example: - Create a filter with one rule selecting the ancestors filter for Edwin Michael Smith - With all rules apply radiobutton selected - Get back to filter list and test the filter -> results look OK - Change the filter to Exactly one rule must apply radiobutton - Get back to filter list and test the filter -> results contain almost all people in the database Results should be the same. With only one rule the radiobuttons should have no effect. > * If I use a filter taking another filter as parameter, for example by > creating following filters: > 1. One person: with rule "People with <ID>" (with some person) > 2. His descendents: with rule "Descendants of <filter> match" (with above > filter given as parameter) > And then try either to test or use 2), I get the following backtrace: > ------- > Traceback (most recent call last): > File "/home/eero/garnome/share/gramps/plugins/FilterEditor.py", line > 423, in test_clicked > handle_list = > filt.apply(self.db,self.db.get_person_handles(sort_handles=False)) > File "/home/eero/garnome/share/gramps/GenericFilter.py", line 2015, in > apply > rule.prepare(db) > File "/home/eero/garnome/share/gramps/GenericFilter.py", line 440, in > prepare > filt = MatchesFilter(self.list) > File "/home/eero/garnome/share/gramps/GenericFilter.py", line 96, in > __init__ > self.set_list(list) > File "/home/eero/garnome/share/gramps/GenericFilter.py", line 106, in > set_list > assert len(list) == len(self.labels), \ > AssertionError: Number of arguments does not match number of labels. > list: [u'One person', u'1'] > labels: ['Filter name:'] > -------- This bug is also still there. > Question: > What's the difference between system filters and custom filters? > Both of these menu items bring up the same user defined filters > editor dialog and system filters are not mentioned in the documentation. > > > Btw. the filter names in the documentation on Gramps site don't anymore > match the names in Gramps (I think they are the old names without angle > brackets). > > I also noticed that the filter names are a bit misleading. For example > filter "Descendant family members of <person>" matches also the > <person> and his/her spouse, not just their descendents. I noticed also following when I closed the filter editor dialog from the window titlebar close button: (gramps:11101): Gtk-CRITICAL **: file gtkcellview.c: line 707 (gtk_cell_view_cell_layout_clear_attributes): assertion `info != NULL' failed (this might be because of my pretty old pygtk version though.) - Eero |
From: Don A. <don...@co...> - 2005-08-28 04:13:19
|
About two weeks ago, we asked if there would be interest in a printed version of the GRAMPS manual. We have been very surprised with the response. We have a large number of people who expressed interest in the manual. We hope to make the manual available in printed form roughly around the time that we make the 2.0.8 release. We want to make this manual as good as possible, so we are asking for your help. We have two people working on making the manual more readable. However, we need your help in making sure that we are covering everything that needs to be covered. I have posted a copy of the manual in OpenOffice format at http://gramps-project.org/files/gramps-manual.sxw We would ask that you review the manual for any information that may be missing. Don't worry about format, spelling, or language. Help us identify topics that are missing from the manual.=20 Thanks. Don --=20 Don Allingham http://don.allingham.org |
From: James A. T. <tr...@de...> - 2005-08-23 00:27:46
|
The Debian package of 2.0.6 was delayed as I was out of town last week. It has been uploaded to the archive and will be available in sid (unstable) sometime tomorrow. For those who are impatient, you can get the package from http://incoming.debian.org/gramps_2.0.6-1_all.deb I hope no one objects to the version number used. Be assured that it uses the correct release of 2.0.6. -- James Treacy tr...@de... |
From: Don A. <don...@co...> - 2005-08-22 14:23:40
|
I will be out of town attending a conference this week. While I will probably be able to get internet access, I will most likely be less available. If you would normally send an email directly to me, please copy the list. Chances are you will get a faster response this way - we have quite a few people on the list just as capable of answering questions. Thanks. Don --=20 Don Allingham <don...@co...> |
From: Julio S. <jul...@gm...> - 2005-08-21 19:56:39
|
2005/8/16, Don Allingham <dal...@us...>: > Now that 2.0.6 is out, I would ask that people attempt to use the > Narrative Web Page generator. 2.0.6 is the first release to include > this, and we want to shake out the bugs. Once we feel confident about > this, we will release 2.0.7 with all the fixes. The alive filter does not work for people recently born. The check is for someone alive some N years ago. Unfortunately, people born after that are marked as not alive at that date and, thus, get leaked. Any fix I can think of is rather intrusive. Julio |
From: Tim A. <ti...@pr...> - 2005-08-21 10:45:46
|
Attached is a patch which addresses a couple of my whinges the other day about the comprehensive ancestors report. I think that making trivial changes to reports is as good a way as any to introduce oneself to the source code base. The changes are: - iff the option to start generations on a new page is selected, the sources list will also start on a new page - for people without photos, we leave the photo box completely blank, no text, no ugly black rectangles I expect the first to be a no-brainer, but perhaps the second may invite debate, since the initial author of this report (was it Tim Waugh?) presumably thought that ugly black rectangles all over the report was a feature, not a bug. Ugliness is in the eye of the beholder, so I'm quite willing to discuss the subject and possibly modify my patch if required. I've done all my testing of the changes with the pdf output option - please let me know if the other options have other subtleties that I've overlooked. Tim |
From: Eero T. <eer...@ne...> - 2005-08-18 18:55:46
|
Hi, On Monday 08 August 2005 19:03, Alex Roitman wrote: > Again, we decided to do it for all reports, but after 2.0.6. The new > progress bar interface is simple, see Utils.ProgressMeter() class for > details. Also see e.g. src/plugins/Check.py for the example use. > > > The typical use is this: > ----------------------------------------------------- > import Utils # already done in all reports, I think > > progress = Utils.ProgressMeter(_('Overall title'),_('Pass title')='') > > progress.set_pass(_('First pass title'),number_of_total_steps) > progress.step() > > progress.set_pass(_('Second pass title'),number_of_total_steps) > progress.step() > > progress.close() > ----------------------------------------------------- Now that 2.0.6 is released, I've added support for this to the Statistics chart. Additionally I made all the barchart texts left aligned in (vain) hope that this would fix the report issues with Gramps font metrics problems, and included the number of persons to each legend item in hope that this clarifies the meaning the charts. I made also several changes to it which require localization changes: - Added the progress meter titles - Added title option for the ReportUtils.draw_legend() and used it with the Statistic Charts - Changed all the StatisticsChart chart type names to singular form (and changed the chart selection tab to say "Charts" instead). This way I could reuse these as legend headings Additionally I added context to "Title" strings in several other files. (This is for Finnish, unfortunately the main problem for this is the glade file containing Edit person dialog where I cannot use localization context. :-/) I haven't updated the template.po yet as I'm assuming that making rest of the reports to use progress indicators will need this too. Bug: There seems to be some problem with Gramps PostScript generation. I get this error from the GhostScript on the Gramps generated PostScript file: ---------- gs ~/statistics_chart.ps ESP Ghostscript 7.07 (2003-07-12) Copyright 2003 artofcode LLC and Easy Software Products, all rights reserved. This software comes with NO WARRANTY: see the file COPYING for details. Error: /undefined in 0,0000 Operand stack: Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1 3 %oparray_pop 1 3 %oparray_pop 1 3 %oparray_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- Dictionary stack: --dict:1057/1417(ro)(G)-- --dict:0/20(G)-- --dict:71/200(L)-- Current allocation mode is local Current file position is 612 ESP Ghostscript 7.07.1: Unrecoverable error, exit code 1 ----------- When looking at the file with less, it looks quite normal PS i.e. the file contents are in right format and not (as far as I could see) e.g. truncated. The generated OO and PDF files worked OK in Xpdf and OO, except that there seems to be some problems (again) with OO output, see the attached OO screenshot: - legend and pie outlines are missing - legend texts are position wierdly (My OpenOffice is 1.1.1 version from SUSE 9.1.) - Eero |
From: Don A. <don...@co...> - 2005-08-17 13:17:57
|
If you want, go ahead and remove it from plugins and move the png file. Don On Wed, 2005-08-17 at 13:45 +0100, Richard Taylor wrote: > That makes sense. However, at the moment, in head, it is in src/ and=20 > src/plugins/. Also the scratchpad.png will need moving to src. >=20 > Richard >=20 > On Wednesday 17 Aug 2005 13:11, Don Allingham wrote: > > For 2.1/2.2 I moved it up to src instead of plugins since it is an item > > on the main menu and not really optional. > > > > Don > > > > On Wed, 2005-08-17 at 10:51 +0100, Richard Taylor wrote: > > > I am a bit confused. > > > > > > We appear to have the scratchpad in two places: > > > > > > src/ScratchPad.py > > > src/plugins/ScratchPad.py > > > > > > Which one should stay? > > > > > > Richard >=20 --=20 Don Allingham <don...@co...> |
From: Richard T. <rjt...@th...> - 2005-08-17 12:45:34
|
That makes sense. However, at the moment, in head, it is in src/ and src/plugins/. Also the scratchpad.png will need moving to src. Richard On Wednesday 17 Aug 2005 13:11, Don Allingham wrote: > For 2.1/2.2 I moved it up to src instead of plugins since it is an item > on the main menu and not really optional. > > Don > > On Wed, 2005-08-17 at 10:51 +0100, Richard Taylor wrote: > > I am a bit confused. > > > > We appear to have the scratchpad in two places: > > > > src/ScratchPad.py > > src/plugins/ScratchPad.py > > > > Which one should stay? > > > > Richard -- You can normally find me on Jabber as Ric...@ja... |
From: Don A. <don...@co...> - 2005-08-17 12:11:43
|
For 2.1/2.2 I moved it up to src instead of plugins since it is an item on the main menu and not really optional.=20 Don On Wed, 2005-08-17 at 10:51 +0100, Richard Taylor wrote: > I am a bit confused. >=20 > We appear to have the scratchpad in two places: >=20 > src/ScratchPad.py > src/plugins/ScratchPad.py >=20 > Which one should stay?=20 >=20 > Richard >=20 --=20 Don Allingham <don...@co...> |
From: Martin H. <Mar...@gm...> - 2005-08-17 10:16:28
|
Hi Richard, you talk about HEAD I guess.. you should better ask Alex about that - he did it about a week ago. His comment was: * src/ScratchPad.py: added But you are right... having two only gives confusion. Cheers, Martin. > Von: Richard Taylor <rjt...@th...> > Betreff: [Gramps-devel] two scratchpads ? > > We appear to have the scratchpad in two places: > > src/ScratchPad.py > src/plugins/ScratchPad.py > > Which one should stay? -- 5 GB Mailbox, 50 FreeSMS http://www.gmx.net/de/go/promail +++ GMX - die erste Adresse für Mail, Message, More +++ |