29th January 2023 at 14:52 #3736
Someone knews if the support of the RFC 6474 for example DEATHDATE is planned?
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
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
25th May 2023 at 22:19 #3744CardBookKeymaster
you mean that this format :
DEATHDATE;19531015T231000Zis not handled, right ?
26th May 2023 at 08:53 #3748
yes. I thought
DEATHDATE;19531015T231000Zis not supported correctly.
PRODID:-//Thunderbird.net/NONSGML Thunderbird CardBook V83.7//EN-GB
26th May 2023 at 09:12 #3749CardBookKeymaster
omg, I think there is an error in the RFC, it should be
26th May 2023 at 09:44 #3750
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
- You must be logged in to reply to this topic.