Re: Importing issue within AddressManager

Hi,

I found some other nasty bugs. E.g. date export and import had *both* 
inversion of month and day. Thus export-import in AddressManager seemed 
consistent, but failed when importing or exporting to e.g. Apple!

Furthermore, our export contained custom types to fields which confused 
Apple. I re-read the RFC, looked into forums.. and I think they are not 
really supported that way. They were not read back either.
To add custom properties (e.g. apple may classify a number as iPhone) a 
whole more complex thing is done which AddressManager does not support.


Patrick Cardona wrote:
>
> Accented letters in firstnames were imported without issue in my case.
> And all expected birthdays are also there.

Good, import was fixed, but export not. So given case, you may need to 
retest.


>> 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.

True. Actually I raised it to level 3.0 or apple would not recognize all 
types properties (home, work, mobile...) for TEL, ADR, EMAIL

> 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.

Both should be fixed in import-export. I tested here locally. Please try 
yourself. You need to rebuild Addresses Framework.



Riccardo