On Monday 15 August 2005 03:46, Alex Roitman wrote:
> > This was because Gramps hadn't installed itself properly as
> > gconftool-2 wasn't in the root's path on SUSE 9.3.
> > In SUSE gconftool-2 is in:
> > /opt/gnome/bin/gconftool-2
> > Installation should stop if:
> > [ -z $(which gconftool-2) ]
> > unless it's run in packager mode.
> This should be fixed, as I said earlier. Please confirm when you can.
This works (now) on my (SUSE 9.1) machine.
However, this happened on a (SUSE 9.3) machine >1h drive away, so final
verification might take a few weeks until I do a new visit there.
> > Failed to import preferences from the 1.0.x version.
> This is because all gramps keys were removed.
> > /usr/local/share/gramps/DbPrompter.py:185: GtkWarning:
> > gtk_file_system_unix_get_folder: assertion `g_path_is_absolute
> > (filename)' failed
> > choose.set_current_folder(default_dir)
> This is harmless.
> > * What was more urgent, was that Gramps didn't show *any* dates in any
> > other than English locale, regardless of whether I directly opened the
> > Gramps 1.x XML data file or imported it first into an empty GRDB
> > database. In the old data.gramps XML file dates are stored in ISO
> > format, like this: ---
> > <event type="Birth">
> > <dateval val="1940-05-24"/>
> > <place ref="P0007"/>
> > </event>
> > ---
> > Same happened also when I used a locale with a data parser (e.g.
> > French). When I debugged this, the 'display' method wasn't called for
> > those languages. Only in English locale the english date 'display'
> > method was called. This is a serious bug/regression.
> > Reversing this change fixed the problem:
> > -------------
> > --- test1/src/ReadXML.py 2005-07-12 23:58:35.000000000 +0300
> > +++ test2/src/ReadXML.py 2005-08-07 22:55:34.000000000 +0300
> > @@ -596,7 +596,10 @@
> > def start_event(self,attrs):
> > self.event = RelLib.Event()
> > self.db.add_event(self.event,self.trans)
> > - self.event_type = const.save_event(attrs["type"])
> > + if self.family:
> > + self.event_type = const.display_pevent(attrs["type"])
> > + else:
> > + self.event_type = const.display_fevent(attrs["type"])
> > if attrs.has_key("conf"):
> > self.event.conf = int(attrs["conf"])
> > else:
> > ------------
> > But I don't see how it could affect the showing of dates...
> This is fixed, using the aboe patch (+ <=> -). The problem was that
> the event types were not properly set, so that the Birth events were
> not recpgnized as such. Dates were OK under the Events tab.
> > * After adding a patronymic to a Person's name in the name editor
> > everything was ok (name showed both in the people list and name editor)
> > until I quit Gramps. However, after restarting Gramps, the UI didn't
> > show the patronymic, not even in the name editor. It was still in the
> > database like this though:
> > ---
> > <name type="Birth Name">
> > <first>Matias</first>
> > - <last prefix="Juhonpoika">Mattila</last>
> > + <last>Mattila</last>
> > + <patronymic>Juhonpoika</patronymic>
> > ---
> > This can be repeated with the example database by doing following:
> > 1. Open Home person
> > 2. Open name editor
> > 3. Move Michael from the first name to patronymic, ok the changes
> > (re-open the person dialog and then name dialog to verify the
> > change)
> > 4. Quit Gramps
> > 5. Restart Gramps
> > 6. Open the person dialog and then name dialog and see that patronymic
> > is not anymore shown
> I cannot reproduce it following these steps, neither under English nor
> Russian locale.
I can reproduce it also using:
LANG=ru_RU.utf-8 garnome.sh gramps
(garnome.sh is a script that setups necessary environment vars for running
Gramps from my home directory. On the SUSE 9.3 machine such a script was
not used and Gramps was installed under /usr/local/.)
After the step 4), the example database has changed to contain this:
<name type="Birth Name">
On restart the patronymic field is empty.
Were you using XML version from the CVS of the test database?
> > * There are also problems with the narrative www-page report:
> > - Report doesn't save the filter selection nor use it
> Again, I cannot reproduce this. For me, the filter is remembered.
> It does seem that it is not used, although I need to look further.
> > - Report doesn't show patronymes (e.g. instead of surname,
> > if that is missing)
> It does show patronymic if I follow your example (move Michael from
> firstname to Patronymic). It seems to have problems when lastname
> is missing though.
In my test database people having patronymics didn't have last names.
It would be even OK if the patronymic were shown after the forename.
> > - Gramps shows only one of the people in the sources references
> > section
> Probably Don is better suited to look at tha NavWebPage problems :-)
> The rest looks OK to me now,
* In the person edit dialog, the last name field is not anymore combobox
from which I could select an already existing last name. It was very
handy in Gramps 1.x, please add it back.
* In the name editor dialog, the last name field combobox doesn't contain
any last names (with the example database), the popup is empty.
Both of above happen with my SUSE 9.1 (using old Garnome) and on SUSE 9.3.
* If the data.gramps XML file is read-only, Gramps gives an error dialog,
but still tries to open it, producing the following Traceback:
GRAMPS : 2.0.6-1
LANG : fi_FI.utf-8
Python : 2.3.3 final
GTK : 2.4.9
PyGTK : 2.3.91
OS : SuSE Linux 9.1 (i586)
Traceback (most recent call last):
File "/home/eero/garnome/share/gramps/ReadXML.py", line 115, in importData
File "/home/eero/garnome/share/gramps/ReadXML.py", line 477, in parse
File "/home/eero/garnome/share/gramps/ReadXML.py", line 1348, in
File "/home/eero/garnome/share/gramps/ReadXML.py", line 839, in
handle = obj.get_handle()
AttributeError: 'NoneType' object has no attribute 'get_handle'
After this Gramps shows an empty database (although it's not) with name of
the read-only file name appended with "(kirjoitussuojattu)" (in Finnish).
(If I close and restart Gramps it returns me to this state too.)
I would have expected the open operation to be canceled and UI to return
to the previous database.