Description of Problem:

The evolution vcard import requires that a work and facsimile telephone no
be encoded in a certain manner that is not following the vcard RFC.

Steps to reproduce the problem:
1.  Create a vcard in a text file with a work and fax no such as:

TEL;WORK:123-123-1234
TEL;FAX:123-123-1234

2. Import the vcard via File-->Import

Actual Results:

Examine the resulting contact to see that the telephone numbers were not
imported.  

Expected Results:

It should have been imported according to the vcard RFC, but instead
evolution requires the telephone numbers to be encoded as follows:

TEL;WORK;VOICE:123-123-1234
TEL;WORK;FAX:123-123-1234

How often does this happen? 

Every Time.

Additional Information:

http://www.imc.org/pdi/vcard-21.ps

According to the RFC, the telephone type can be BBS, CAR, CELL, FAX, HOME,
ISDN, MODEM, MSG, PAGER, PREF, VIDEO, VOICE, WORK, or ANY combination of
those types.  There is no specification that WORK requires VOICE, MESSAGE,
or FAX, and so on...