On Fri, 2006-01-13 at 18:15 -0500, Gary Walsh wrote:
> I have been trying out PhpGedView this week and have come across a
> problem with GEDCOM files exported from GRAMPS. Some of the person ID's
> in my GRAMPS database have underscores in them. This seems to cause
> problems in PhpGedView. In the person view in that program the
> underscores seem to get stripped, giving a wrong id and so no data
> displays for that person. =20
> The developer that I am communicating with is wondering why GRAMPS uses
> underscores, though he says that the GEDCOM 5.5 standard permits them.
> Apparently, they are causing a lot of trouble in PhpGedView 4.0 beta 4.
> (I am using stable version 3.3.8). =20
> Are any other GRAMPS users on this list also using PhpGedView? Has
> anyone else come across this problem?
GRAMPS does not normally generate underscores in its IDs that it
generates. The user can define the naming scheme we use, and the default
is Ixxxx for people (where xxxx is a number). In the settings, you will
see that our template is "I%04d", indicating an I followed by a 4 digit
number. For us to generate underscores, the user will have to change
this template to include undercores.
That being said, GRAMPS will preserve any IDs it sees on import. So, if
you import into GRAMPS from a GEDCOM that uses underscores, we will keep
But, what it really boils down to is that PhpGedView needs to make sure
that it accepts any valid ID value. Otherwise, they are not GEDCOM