Log in
Sign up
View all  |  Close all
#
Subject
Posted by
Actions
1
ERROR in pre-1752 date processing in FTB4
Mark Morgan
- Close

Using Windows FTB 4.0.0.916.

I need to enter a date of burial of 28 Jan 1587/8 to correctly represent an old form and new form date before the start of the year was changed in 1752 in the UK.

When I enter the date as 28 Jan 1587/8 or 28 Jan 1587/88 or even 28 Jan 1587/1588 it incorrectly converts it to 28 Jan 1585/86.

Thanks,

Mark. 

Mark Morgan
United Kingdom
- Reply
2
RE: ERROR in pre-1752 date processing in FTB4
Noam
- Close

Hi Mark,

you can enter it as free text, like this:

 

28 Jan 1587 - 1588

 

Regards,

Noam \ MyHeritage Team 

Noam
Israel
- Reply
3
RE: ERROR in pre-1752 date processing in FTB4 [2]
Mark Morgan
- Close

Noam, 

Many thanks for the temporary work around.

One other thing with my example above, having entered 28 Jan 1587/88 and FTB converting it to 28 Jan 1585/86, for some unknown reason, then when you export the GEDCOM file it comes out as 28 Jan 1586/87.

The date I entered is a perfectly valid date according to the GEDCOM 5.5 standard and should be accepted as-is.

Is FTB attempting to convert the date to New Style assuming that I'd entered an Old Style or vice-versa?

With regard to your work around, when entering a free text date, a date phrase in GEDCOM terms, the GEDCOM file export is not enclosing the date in the parenthesis required by the standard.

DATE_PHRASE:

(<TEXT>) 

Any statement offered as a date when the year is not recognizable to a date parser, but which gives information about when an event occurred. The date phrase is enclosed in matching parentheses. 

Of course, there is nothing stopping me from putting the parenthesis in the free text myself. 

Mark. 

Mark Morgan
United Kingdom
- Reply
4
RE: ERROR in pre-1752 date processing in FTB4 [3]
Mark Morgan
- Close

Noam,

I've spotted another work around using the free text date option.  I can enter it as an 'interpreted' date as INT 28 Jan 1587/88 without the parenthesis date phrase following it.  This exports in GEDCOM correctly although it does appear that a date phrase is required to follow an interpreted date by the GEDCOM standard.

Thanks,

Mark. 

Mark Morgan
United Kingdom
- Reply
5
RE: ERROR in pre-1752 date processing in FTB4 [4]
Noam
- Close

Nice discovery! thank you for sharing it.

I will talk to our Development team about this issue.

 

Regards,

Noam. 

Noam
Israel
- Reply
 
Loading...
Loading...