Improvements of vcf import

[peter.macej]

I have many vCard contacts saved from other applications in the .vcf file. MPE imports them almost fine. There are some minor problematic fields:

• Sometimes the phone numbers are not imported correctly. Please allow more flexibility during import. For example Mobile field expects the
  TEL;CELL;VOICE:
  in vcf file. If it is anything else, it is not imported. However, other programs may use
  TEL;HOME;CELL:
  or something similar. The HOME, and VOICE are optional parameters. If they are or are not present, please, always take it as Mobile number. These parameters are described in RFC 2426 in section 3.3.1.
• The same applies to Work number. You expect it to be
  TEL;WORK:
  in vcf file. It may be also
  TEL;WORK;CELL:
  Again. The WORK is important here. So ignore CELL or VOICE.
• Birthday date is only imported if it is of the form:
  BDAY:YYYYMMDD
  My vcf files contain also
  BDAY:YYYY-MM-DDT, e.g. BDAY:1999-02-12T
  Please parse also this format. It is described in RFC 2426 in section 3.1.5.
• MPE imports main email only if the field looks like:
  EMAIL;INTERNET;PREF:
  Usually, vcf contains only
  EMAIL;INTERNET:
  In this case MPE imports this email into 2. email field and the main email is empty. This is incorrect. Please, place it into main email and use PREF parameter only if there are multiple emails. See RFC 2426 in section 3.3.2.

[FJ]

The import is optimized to the datalayout in the phone.

TEL;HOME;CELL:
The HOME, and VOICE are optional parameters. If they are or are not present, please, always take it as Mobile number.

In this case "CELL" should take affect.

TEL;WORK;CELL:
Again. The WORK is important here. So ignore CELL or VOICE.

And here should be WORK important ? This gives no sense for me.

BDAY can be fixed easily.

EMAIL: Can you tell me please whats the problem ? Its absolutly not interesting if its in the first or the second line.

At last take care of referencing to RFC's. I has cost me hours to make the import compatible to other apps like Sunbird only cause they do not strict work to the RFC's.

[peter.macej]

TEL;HOME;CELL:
The HOME, and VOICE are optional parameters. If they are or are not present, please, always take it as Mobile number.

In this case "CELL" should take affect.

I agree. But MPE doesn't recognize this.

TEL;WORK;CELL:
Again. The WORK is important here. So ignore CELL or VOICE.

And here should be WORK important ? This gives no sense for me.

Well, I'm not expert for vCard. But what else should be important here then? The Work field can contain work mobile or work phone. So we cannot rely on CELL nor VOICE. The WORK seems to be the only common parameter here.

EMAIL: Can you tell me please whats the problem ? Its absolutly not interesting if its in the first or the second line.

I agree that's only cosmetic problem. I just found strange to have 2. email when there is no 1. email.

At last take care of referencing to RFC's. I has cost me hours to make the import compatible to other apps like Sunbird only cause they do not strict work to the RFC's.

I didn't want to offend you in any way. I just thought you will find RFC links useful. I understand your problems with compatibility. The only reason for my post was the fact that the following vCard (which I find valid) didn't import correctly:

BEGIN:VCARD
VERSION:2.1
N:Smith;John
FN:John Smith
TEL;WORK;CELL::1234
TEL;HOME;VOICE:3456
TEL;HOME;CELL::2345
EMAIL;INTERNET:john@smith.com
BDAY:1999-02-12T
END:VCARD

Only home phone 3456 was imported. The personal mobile 2345 and work mobile 1234 were ignored.