Re: Importing issue within AddressManager

Hi Riccardo,

On 2025-10-31 10:19:19 +0100 Riccardo Mottola <[email protected]> wrote:

> 
> 
> Forrest Gump should now import with correct Home and Work phone number. I had 
> to re-read the RFC. It says:

I confirm Forrest Gump was successfully imported as expected. Birth day is good too.

> 
> These type parameter values can be  specified as a parameter list (e.g., 
> TYPE=text;TYPE=voice) or as a   value list (e.g., TYPE="text,voice").
> 
> So had to implement parsing of both versions.
> 
> 
> I also found a bug that could cause exceptions with extended (e.g. UTF-8) 
> characters. If you wish, test with your favorite files.

Accented letters in firstnames were imported without issue in my case.
And all expected birthdays are also there.

> 
> May you also try to export-import again your files and see how it fares now? 
> But possibly we need further tweaking there

While importing a vcard with version 4.0, all fields are ok.
Exporting still produce a vcard with version 2.1.
This regressing version could explain some data loss: FN, PHOTO and the BDAY date altered:
So 'BDAY:19620709' (in vcard 4.0) becomes: 'BDAY:1962-09-07' in the vcard 2.1 exported.
And then, while reimporting this vcard 2.1:
- We have a bad Birth day: 07/09/1962 (month and day are inverted)
- We are loosing home type. 

So we can say now:
- Importing recent vcard format (4.0) is ok.
- Saving an address base with exporting is not reliable, because some data will be lost or altered while reimporting from this vcard 2.1.

Cheers,
Patrick

-- 
Patrick Cardona - Pi400 - GNU/Linux aarch64 (Debian 13.1) 
Xorg (1:7.7+24) - libcairo2 (1.18.4-1+rpt1 arm64)
Window Maker (0.96.0) - GWorkspace (1.1.0 - 02 2025) - Theme: AGNOSTEP - MUA: GNUMail (1.4.0)