Re: [Gramps-bugs] v101-1 Disconnected people, gedcom & non-ASCII, merge dupes

[Alex R. <sh...@al...>]

Hi,

Thanks for your reports!

On Sun, Feb 22, 2004 at 05:43:28PM -0500, cariboupronk wrote:
>=20
> USING VER 1.0.1-1
>=20
> DISCONNECTED PEOPLE
> - in People view, used filter to get list of disconnected individuals
> - default opened to disconnected people with surname beginning with "L"
> - right click to delete person, no problem
> - this was done for several people, move on to other tabs for surnames=20
> beginning with other letters
> - a blank screen appears after individual deleted and goes to original=20
> "L" surname tab which is now empty
> - must click on a tab and wait
> - empty tabs still shown
> Suggestions:
> - once an individual is deleted, program highlights next person on list
> - empty tabs disappear

This is a known issue: the current tab does not disappear after deleting th=
e=20
last person. Not that this is correct, but we know about it and correct it
when we can :-)

> NON-ASCII CHARACTER AND GEDCOM ISSUE
> - imported a gedcom produced by The Master Genealogist ver 5
> - Gramps gave no problems and data seemed fine
> - saved Gramps database
> - when try to re-open, it failed partially through
> - upon re-importing the gedcom, then exporting it as a gedcom from=20
> Gramps and re-importing again to Gramps, same error received
> - ran Gramps from a terminal, found there were errors reported in database
> - examined data.gramps file and in each place where there was an error,=
=20
> there was a non-ASCII character (vertical rectangle with 0 0 in top row=
=20
> and a 0 1 in bottom row) with an "R" after
> - deleted non-ASCII characters and gramps would load its own database=20
> file after that
> - this means that Gramps imported the non-ASCII characters and saved=20
> them in its own database, but was unable to load its own database with=20
> the characters still there

The most likely problem is that your gedcom has non-ascii chars in=20
one charset, while it announces a different charset in its header.
The CHAR line in the header has to correspond to the actual charset used.
Most problems come when the GEDCOM uses UTF8 charset and writes ANSI
in the header. Changing ANSI to UTF8 should fix these problems.=20

If it does not fix the problem, is there any chance you can send a little
portion of your gedcom which can reproduce the error? There has to be a=20
header and the portion with non-ascii characters. You can send it personally
to me if you don't wish to share it with the whole list.

> ERROR WHEN TRY TO MERGE DUPLICATE INDIVIDUALS
> - this error was received numerous times for about 1/3 to 1/2 of=20
> individuals on list generated by search for duplicates to merge:
>=20
> Traceback (most recent call last):
>  File "/usr/share/gramps/MergeData.py", line 354, in on_merge_clicked
>    self.update(self.p1,self.p2,old_id)
>  File "/usr/share/gramps/plugins/Merge.py", line 268, in on_update
>    self.redraw()
>  File "/usr/share/gramps/plugins/Merge.py", line 243, in redraw
>    list.append((c,p1,p2.getId()))
> AttributeError: 'unicode' object has no attribute 'getId'

This looks like a bug. Again, if you could provide a way to reproduce it,
it would be of great help. You can send a gedcom (or a portion thereof)
and directions on whom to merge to get this error. If you can reproduce
it with the example database (can be opened via Help->Open example database)
then just send directions.

Thanks,
Alex

--=20
Alexander Roitman   http://ebner.neuroscience.umn.edu/people/alex.html
Dept. of Neuroscience, Lions Research Building
2001 6th Street SE, Minneapolis, MN  55455
Tel (612) 625-7566   FAX (612) 626-9201