platform_frameworks_opt_vcard/java, branch tools_r22

Store encoding in upper case.

2012-11-13T00:47:40+00:00

Instead of checking for up case each time or using equalsIgnoreCase.

Bug: 7292017
Change-Id: I3954a2e0fdb757d157bcf3dff77ed2749a9577d8

Allow importer to handle missing encoding attribute for FN.

2012-11-09T23:35:35+00:00

- Removed separators from FN properties.
- Adding fix on importer side since we cannot fix exporters that already exist.

Bug: 7292017
Change-Id: I61c691c24828e63aac1920384e16461da7a03881

Fix missing encoding attribute on FN field.

2012-11-09T00:33:21+00:00

When FN field is built from display name, the encoding attribute is missing.
Created common method to build N and FN fields so they will not be out of
sync in the future.

Bug: 7292017
Change-Id: I7faceb316b639d626a54bdd455df1e748b22face

Allowing multiline addresses to support microsoft vCard.

2012-08-24T20:50:31+00:00

Multiline addresses are not allowed in vCard 2.1 but it has been encountered
in microsoft mobile vCard. This adds support for this by checking the next
line.  If the next line contains a colon, we assume it's a new property.
Otherwise, we assume it's a continuation.

Bug: 5188556
Change-Id: I4607eda901a1d535c759b5026f6702eb47290cb8

Making vcard photo parsing more robust to decode errors.

2012-08-15T21:20:18+00:00

Base64.decode throws IllegalArgumentException which is not handled
and results in crash reports for users. Switching to VCardException
which should have better UI handling.

Change-Id: I3fa12b8a703c3eed181caade0bfda2271435b377

Fix for malformed photo entry.

2012-08-15T18:38:32+00:00

Blackberry vcard photo entry is not terminated with standard vcard 2.1
terminator. The vcard code is suppose to handle this irregularity already
but there was a bug where it would not work unless the next entry contained
a ':' right after the property name (i.e. "END:VCARD").  Cases with next
entries such as "TEL;TYPE=CELL:" was missed. Note the ":" is not right after
TEL.

Bug: 6979337
Change-Id: Ifa3dbb377b9da97ef7570c0f8eca8a1cb5e727a9

Handle "VOICE" type as OTHER on Android

2011-11-28T19:38:57+00:00

vCard's "VOICE" type is the default type used in the format, while
OTHER is the default type on Android. Our exporter treats Android's
OTHER type as vCard's "VOICE", while our importer accepts
the default type "VOICE" as Android's CUSTOM type with "VOICE" label,
which confuses users: when they transfer phone numbers with OTHER type
those numbers become "VOICE" on receiver sides.

Bug: 5600504
Change-Id: Id30d2ca9b67b81798565224b881a734e8ee76516

Allow vCard users to format phone numbers by themselves

2011-09-21T18:59:22+00:00

Bug: 5348938
Bug: 4177894
Change-Id: Iff9461d8c71c5800b0731c3708867003d75bb395

Add API for setting the raw contacts URI.

2011-09-15T20:27:44+00:00

Needed for when we are building vcards for a profile contact.

Bug: 5300714
Change-Id: Ib4adc54d525ffaffe4d8955f4ba894d1a315099d

Bluetooth : Modify build & parse vcard

2011-08-24T21:36:57+00:00

If the contacts have "p"or "w" instead of "," or ";" when some carkits
are receiving them from andro id OS, some catkits cannot parse the
contacts.

Bug: 5178723
Change-Id: I536ca57aff561fb0637448bcddfd53a6ba8b28ef