GDBI 13.5 is unable to handle date entries of the form
"BEF xxxx", "AFT xxxx" or "ABT xxxx" (before, after and
about xxxx). It gives the error 'PARSE ERROR:
Unparseable date: "BEF 1938"'
Yeah, I have been meaning to add that for years. I was
never sure how best to parse the string. If you look for
a 3-letter word, then you catch "JAN 1999", and you
miss "About xxxx", which I saw in a GEDCOM.
I could do it in 2 steps. I can try parsing the whole
string as a date, and if that fails and it starts with a
letter, strip off the first word and reparse the rest as a
date.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
At least phpgedview does not recognize "About", only "ABT".
The GEDCOM standard does not support these, too. I think it
would be enough to parse for the abbreviations defined in
the GEDCOM standard (ABT, EST, CAL, BET ... AND, AFT, BEF,
FROM ... TO). See http://homepages.rootsweb.com/~pmcbride/gedcom/55gcch2.htm#DATE
Stripping off the first word will not help with dates like
"BET 1938 AND 1940" (between ...).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
These parse errors actually come from a separate package, Taurus FamilyTree, which is integrated for the Ancestor button. I did not want to fix my copy because I have an out of date version. I tried upgrading, but I had trouble re-integrating it. I have not been actively working on GDBI, and stuggling with this integration is not fun, so I postponed updating the code and fixing this parse error.
This error is very visible because it prints to STDERR, but if you are not using the FamilyTree window, you can ignore it.
What is more important is if these dates keep BKEdit from determining the age. That seems to be the only thing BKEdit uses the dates for. It should do more, like have better input checking.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=987779
GDBI cannot handle incomplete date entries like:
PARSE ERROR: Unparseable date: "MAY 1982"
which are perfectly ok in phpgedview.
Logged In: YES
user_id=325184
Yeah, I have been meaning to add that for years. I was
never sure how best to parse the string. If you look for
a 3-letter word, then you catch "JAN 1999", and you
miss "About xxxx", which I saw in a GEDCOM.
I could do it in 2 steps. I can try parsing the whole
string as a date, and if that fails and it starts with a
letter, strip off the first word and reparse the rest as a
date.
Logged In: YES
user_id=987779
At least phpgedview does not recognize "About", only "ABT".
The GEDCOM standard does not support these, too. I think it
would be enough to parse for the abbreviations defined in
the GEDCOM standard (ABT, EST, CAL, BET ... AND, AFT, BEF,
FROM ... TO). See
http://homepages.rootsweb.com/~pmcbride/gedcom/55gcch2.htm#DATE
Stripping off the first word will not help with dates like
"BET 1938 AND 1940" (between ...).
Logged In: YES
user_id=325184
Originator: NO
These parse errors actually come from a separate package, Taurus FamilyTree, which is integrated for the Ancestor button. I did not want to fix my copy because I have an out of date version. I tried upgrading, but I had trouble re-integrating it. I have not been actively working on GDBI, and stuggling with this integration is not fun, so I postponed updating the code and fixing this parse error.
This error is very visible because it prints to STDERR, but if you are not using the FamilyTree window, you can ignore it.
What is more important is if these dates keep BKEdit from determining the age. That seems to be the only thing BKEdit uses the dates for. It should do more, like have better input checking.