Support of RFC 6474 for DEATHDATE

[Vegisto]

Hallo together,

Someone knews if the support of the RFC 6474 for example DEATHDATE is planned?

Format definition:
DEATHDATE-param = DEATHDATE-param-date / DEATHDATE-param-text
DEATHDATE-value = date-and-or-time / text
; Value type and VALUE parameter MUST match.
DEATHDATE-param-date = "VALUE=date-and-or-time" / calscale-param
; calscale-param can only be present when DEATHDATE-value is
; date-and-or-time and actually contains a date or date-time.
DEATHDATE-param-date = "VALUE=text" / language-param
DEATHDATE-param =/ altid-param / any-param
Examples:
DEATHDATE:19960415
DEATHDATE:--0415
DEATHDATE;19531015T231000Z
DEATHDATE;VALUE=text:circa 1800

Import is possible for each on, but the DEATHDATE is only visible for the exmples 1,2,4.

I can insert the deathdate in Cardbook for example 1-3. The death date only shown in the general tab for 1&2.

The same by the way,  i thougt for the birthday field (RFC 6350) which supports (in the RFC) a birth time too.

Thanks & Kind regards

Gerhard

[CardBook]

you mean that this format : DEATHDATE;19531015T231000Z is not handled, right ?

[Vegisto]

Hallo Cardbook-Team,

yes. I thought DEATHDATE;19531015T231000Z is not supported correctly.

BEGIN:VCARD
VERSION:4.0
PRODID:-//Thunderbird.net/NONSGML Thunderbird CardBook V83.7//EN-GB
UID:804f0bf8-70c6-466e-8c95-bed578a0dfea
FN:Three A_RFC
N:A_RFC;Three;;;
DEATHDATE;19531015T231000Z
REV:20230128T130643Z
END:VCARD

Best Regards

Gerhard

[CardBook]

omg, I think there is an error in the RFC, it should be DEATHDATE:19531015T231000Z instead of DEATHDATE;19531015T231000Z

[Vegisto]

Hallo Cardbook-Team,

ok. I don’t know if the RFC is buggy, but this will work.

Now, it would be nice to see the deathday-time and birthday-time on adress-tab and the importfield will support the time in an easilier way.

Thanks and bests Regards

Gerhard

[Author]

Posts