I made today a new GEDCOM with Brothers Keeper for the family tree on my website. After the import of this GEDCOM into database, will some data not shown correct.
the date in BK 15.08.866 shows PhpGedview as 1508866
the date in BK 27.03.972 shows PhpGedview as 2703972
the date in BK 970 PhpGedview shows the correct year 970
BK show this date as correct, but PhpGedview cannot read this date.
Is this a bug in BK or maybe in PhpGedview?
This shows the date in BK:
This shows the date in PGV:
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Otmar
Did you not review the BK 'features' and known bugs?
(new items or items fixed by 6.0.61 are below)
(fixed) Gedcom export will convert all date formats to normal gedcom date format.
So, they admit that their 'date' format is NOT a normal gedcom date format and that using the convert utility is essential for dates to work with other GEDCOM programs. -Stephen
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've seen now it is not a problem of PGV, because BK do not convert all date versions right. See outcut of the GEDCOM:
1 NAME Robert /the Strong/
1 SEX M
1 BIRT
2 DATE 820
-----^ This works fine.
1 DEAT
2 DATE 15.09.866
--------^ This is wrong.
2 PLAC Brissarthe, Neustria
2 CAUS Im Krieg gefallen
1 FAMS @F23740@
0 @I69231@ INDI
The developer of BK will fix that.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I made today a new GEDCOM with Brothers Keeper for the family tree on my website. After the import of this GEDCOM into database, will some data not shown correct.
the date in BK 15.08.866 shows PhpGedview as 1508866
the date in BK 27.03.972 shows PhpGedview as 2703972
the date in BK 970 PhpGedview shows the correct year 970
BK show this date as correct, but PhpGedview cannot read this date.
Is this a bug in BK or maybe in PhpGedview?
This shows the date in BK:
This shows the date in PGV:
Otmar
Did you not review the BK 'features' and known bugs?
(new items or items fixed by 6.0.61 are below)
So, they admit that their 'date' format is NOT a normal gedcom date format and that using the convert utility is essential for dates to work with other GEDCOM programs.
-Stephen
I've seen now it is not a problem of PGV, because BK do not convert all date versions right. See outcut of the GEDCOM:
1 NAME Robert /the Strong/
1 SEX M
1 BIRT
2 DATE 820
-----^ This works fine.
1 DEAT
2 DATE 15.09.866
--------^ This is wrong.
2 PLAC Brissarthe, Neustria
2 CAUS Im Krieg gefallen
1 FAMS @F23740@
0 @I69231@ INDI
The developer of BK will fix that.