vcard-implementations - Revision history

Lowongankerjalampung at 13:39, 18 February 2017

2017-02-18T13:39:57Z

← Older revision		Revision as of 13:39, 18 February 2017
Line 182:		Line 182:

	== CSV to vCard ==		== CSV to vCard ==
	[http://~~homepage~~.~~mac~~.~~com/phrogz/CSV2vCard_v2~~.~~html~~ CSV to vCard] web service takes CSV (or tab-delimited) contacts and turns them into vCard format. This was originally written to take information from Outlook Express for Mac OS 9 and bring it into the address book in OS X.		[http://tempatservicehpdibandarlampung.blogspot.co.id CSV to vCard] web service takes CSV (or tab-delimited) contacts and turns them into vCard format. This was originally written to take information from Outlook Express for Mac OS 9 and bring it into the address book in OS X.

	== contributors==		== contributors==

Tantek: reformat a bit, move contributors to bottom (consider dropping)

2008-01-07T12:19:18Z

reformat a bit, move contributors to bottom (consider dropping)

@@ Line 1: / Line 1: @@
 <h1> vCard implementations </h1>
+{{TOC-right}}
-In the development of [[hcard|hCard]] and proxies like X2V, we have discovered various behaviors and quirks of vCard implementations.  See also the [[vcard-errata]].
+In the development of [[hcard|hCard]] and proxies like X2V, we have discovered various behaviors and quirks of [[vCard]] implementations.  See also the [[vcard-errata]].
 == Conventions ==
@@ Line 190: / Line 183: @@
 == CSV to vCard ==
 [http://homepage.mac.com/phrogz/CSV2vCard_v2.html CSV to vCard] web service takes CSV (or tab-delimited) contacts and turns them into vCard format. This was originally written to take information from Outlook Express for Mac OS 9 and bring it into the address book in OS X.

Tantek: noted Apple Address Book problem with aim: URLs, and that ONE URL property restriction was only in v3.0 and below, verified works fine in v4.0+.

2007-11-25T03:39:42Z

noted Apple Address Book problem with aim: URLs, and that ONE URL property restriction was only in v3.0 and below, verified works fine in v4.0+.

← Older revision		Revision as of 03:39, 25 November 2007
Line 140:		Line 140:

	=== AAB URL ===		=== AAB URL ===
	'''Non-standard restriction.''' Only ONE URL property value is supported (whereas multiple should be supported, just like EMAIL).		'''Lack of support for aim protocol'''. URLs starting with "aim:" are imported but then when clicked, Address Book prepends them with <nowiki>http://</nowiki> before "activating" them thus rendering them non-functional.

			'''Non-standard restriction to one value.''' (Version 3.0 and below only. Works fine in v4.0+): Only ONE URL property value is supported for vCard import (whereas multiple should be supported, just like EMAIL).

	=== AAB ADR ===		=== AAB ADR ===

Tantek: added CSV to vCard

2007-10-30T01:27:23Z

added CSV to vCard

← Older revision		Revision as of 01:27, 30 October 2007
Line 185:		Line 185:
	=== PD414 vCard import ===		=== PD414 vCard import ===
	Palm Desktop 4.1.4 appears to fail importing a vcard if it has a NAME specified in the vcard.		Palm Desktop 4.1.4 appears to fail importing a vcard if it has a NAME specified in the vcard.

			== CSV to vCard ==
			[http://homepage.mac.com/phrogz/CSV2vCard_v2.html CSV to vCard] web service takes CSV (or tab-delimited) contacts and turns them into vCard format. This was originally written to take information from Outlook Express for Mac OS 9 and bring it into the address book in OS X.

BluesMoon: /* Evolution */ add note about PGP key support in evolution

2007-09-18T10:53:19Z

Evolution: add note about PGP key support in evolution

← Older revision		Revision as of 10:53, 18 September 2007
Line 167:		Line 167:
	'''Unsupported.'''		'''Unsupported.'''
	* ichigo, Frederic to fill in details		* ichigo, Frederic to fill in details

			=== Evo KEY ===

			Evolution uses GnuPG to manage GPG/PGP keys

	== Nokia series 60 address book ==		== Nokia series 60 address book ==

Tantek: added photo downsampling suggestion

2007-08-31T23:45:55Z

added photo downsampling suggestion

← Older revision		Revision as of 23:45, 31 August 2007
Line 18:		Line 18:
	# Support <em>subscribing</em> to vCard URLs on the Web in addition to importing so that your local address book can have automatically current (fresh) information of the contacts that you've added from the Web.		# Support <em>subscribing</em> to vCard URLs on the Web in addition to importing so that your local address book can have automatically current (fresh) information of the contacts that you've added from the Web.
	# Use a rendering engine (e.g. Trident, Gecko, Webkit) to render PHOTO URLs and other properties which have URL values live from the Web for similar freshness.		# Use a rendering engine (e.g. Trident, Gecko, Webkit) to render PHOTO URLs and other properties which have URL values live from the Web for similar freshness.
			# When syncing to another device that supports contact information (iPod, iPhone, BlackBerry etc.), downsample PHOTOs (and other images or binary data) to whatever small size works best on those devices so as to not bloat the space on those devices. Note that such downsampling is best done closest to the point of synchronization, e.g. by the Address Book application when syncing, instead of upfront by a web service like X2V, so that maximum data fidelity is maintained until the last minute when the data can be compressed for the specific device purely for efficiency reasons.

	== Microsoft Outlook ==		== Microsoft Outlook ==

Tantek: added General Suggestions section

2007-08-31T23:43:03Z

added General Suggestions section

← Older revision		Revision as of 23:43, 31 August 2007
Line 10:		Line 10:
	* Steve Robillard		* Steve Robillard

	== ~~conventions~~ ==		== Conventions ==
	~~List~~ implementation as the header including minimal version information. Provide an abbreviation of the implementation name (in parantheses) for use in subheadings for property names and other general subsections. Prefix subheadings with aforementioned abbreviation followed by vCard property name (if applicable) in ALL CAPS as vCard properties are typically fully uppercased in both vCard files and implementations (but are actually case-insensitive per RFC 2426).		'''Conventions for this page.''' When documenting a specific implementation, use the name of the implementation as the header including minimal version information. Provide an abbreviation of the implementation name (in parantheses) for use in subheadings for property names and other general subsections. Prefix subheadings with aforementioned abbreviation followed by vCard property name (if applicable) in ALL CAPS as vCard properties are typically fully uppercased in both vCard files and implementations (but are actually case-insensitive per RFC 2426).

			== General Suggestions ==
			General implementation guidelines and suggestions for vCard implementations. (Note: it might be useful to separate the more generic aspects of of these general vCard implementation suggestions into a "contact application" section on the [[user-interface]] page.)
			# Fully implement RFC 2426, including all properties, sub-properties, and type values for properties, on both import and export with 100% roundtrip fidelity.
			# Support <em>subscribing</em> to vCard URLs on the Web in addition to importing so that your local address book can have automatically current (fresh) information of the contacts that you've added from the Web.
			# Use a rendering engine (e.g. Trident, Gecko, Webkit) to render PHOTO URLs and other properties which have URL values live from the Web for similar freshness.

	== Microsoft Outlook ==		== Microsoft Outlook ==

Tantek at 23:22, 31 August 2007

2007-08-31T23:22:21Z

← Older revision		Revision as of 23:22, 31 August 2007
Line 130:		Line 130:

	=== AAB PHOTO ===		=== AAB PHOTO ===
	'''~~Parital~~ support.''' The PHOTO property is only supported when it has inline encoded data. URL values appear to be ignored.		'''Partial support.''' The PHOTO property is only supported when it has inline encoded data. URL values appear to be ignored.

	=== AAB URL ===		=== AAB URL ===

Tantek: fix up headings for better permalinkability, scope to product/app, remove status

2007-08-31T23:21:55Z

fix up headings for better permalinkability, scope to product/app, remove status

Show changes

Tantek: Apple Address Book clarifications. en-US.

2007-08-31T22:48:27Z

Apple Address Book clarifications. en-US.

← Older revision		Revision as of 22:48, 31 August 2007
Line 6:		Line 6:

	== Contributors==		== Contributors==
	* Tantek Çelik		* [[User:Tantek\|Tantek Çelik]]
	* Brian Suda		* Brian Suda
	* Steve Robillard		* Steve Robillard
Line 115:		Line 115:
	=== general comments ===		=== general comments ===
	* There are issues with importing UTF-8 vCards. Apple Address Book appears to treat .vcf files in the file system NOT as UTF-8, but rather perhaps Mac Roman?		* There are issues with importing UTF-8 vCards. Apple Address Book appears to treat .vcf files in the file system NOT as UTF-8, but rather perhaps Mac Roman?
	** Workaround: Explicitly specify the UTF-8 charset for vCard properties/fields that have non-ASCII-7 characters.		** Workaround: Explicitly specify the UTF-8 charset for vCard properties/fields that have non-ASCII-7 characters. This is allowed per [[vcard-errata]], and encouraged to enable higher fidelity character set handling.
	* Importing multiple vCards with the same fn/n results in duplicate entries in the Address Book. Basically, Address Book assumes that every vCard present in a single .vcf file represents a different person, even if the fn/n are the same etc.		* Importing multiple vCards with the same fn/n results in duplicate entries in the Address Book. Basically, Address Book assumes that every vCard present in a single .vcf file represents a different person, even if the fn/n are the same etc.
	** Workarounds:		** Workarounds:
Line 121:		Line 121:
	*** Have the converting application/service (e.g. X2V), do automerging of hCards with the same fn/n and generate a .vcf stream with one vCard per unique fn/n.		*** Have the converting application/service (e.g. X2V), do automerging of hCards with the same fn/n and generate a .vcf stream with one vCard per unique fn/n.
	* Apple Address Book 4.0.4 (Mac OS X 10.4) exports vCard files as UTF-16 big endian with no BOM and Mac (CR) line endings, if the vCard record contains any non-ASCII data (for example Japanese characters). If the entire vCard record can be represented in ASCII, it is exported as an ASCII encoded file with Windows (CR+LF) line endings.		* Apple Address Book 4.0.4 (Mac OS X 10.4) exports vCard files as UTF-16 big endian with no BOM and Mac (CR) line endings, if the vCard record contains any non-ASCII data (for example Japanese characters). If the entire vCard record can be represented in ASCII, it is exported as an ASCII encoded file with Windows (CR+LF) line endings.

			Several properties appear to have no or limited support, see below for specifics.

	=== organization vs. individual ===		=== organization vs. individual ===
Line 142:		Line 144:
	The LOGO property is totally ignored and not even saved as part of the NOTE.		The LOGO property is totally ignored and not even saved as part of the NOTE.

	=== photo (~~limitations~~) ===		=== photo (limited support) ===
			The PHOTO property is only supported when it has inline encoded data. URL values appear to be ignored.
	The PHOTO property ~~can~~ only ~~take~~ inline encoded data. URL values ~~for are~~ ignored.

	=== url (limitations) ===		=== url (limitations) ===

	Only ONE URL property value is supported (whereas multiple should be supported, just like EMAIL).		Only ONE URL property value is supported (whereas multiple should be supported, just like EMAIL).

	=== adr (~~behaviour~~) ===		=== adr (behavior) ===
			If you do NOT specify which type of address information it is (like HOME or WORK) it is assumed to be a WORK address, whereas [[vcard\|vCard]] specifies that the default type for adr is all of: INTL, POSTAL, PARCEL, WORK.
	If you do NOT specify which type of address information it is (like HOME or WORK) it is assumed to be a WORK address.

	~~=== categories (behaviour) ===~~

			=== categories (behavior) ===
	Behavior confirmed on versions:		Behavior confirmed on versions:
	* default on OSX.3		* default on OSX.3
Line 171:		Line 169:

	== Evolution ==		== Evolution ==

	On Linux.		On Linux.

	=== geo (lack of support) ===		=== geo (lack of support) ===

	* ichigo, Frederic to fill in details		* ichigo, Frederic to fill in details

	== Nokia series 60 address book ==		== Nokia series 60 address book ==

	=== Line endings ===		=== Line endings ===

	The Contacts application on Nokia series 60 handsets will only open vCards with Windows (\r\n) line endings. Any other line ending styles will cause an error message.		The Contacts application on Nokia series 60 handsets will only open vCards with Windows (\r\n) line endings. Any other line ending styles will cause an error message.

	This is actually reasonable ~~behaviour~~ because the vCard spec explicitly states \r\n should be used, but many applications will accept \n delimited vCards without complaint, and may microformat services produce \n delimited output.		This is actually reasonable behavior because the vCard spec explicitly states \r\n should be used, but many applications will accept \n delimited vCards without complaint, and may microformat services produce \n delimited output.

	== Palm Desktop 4.1.4 ==		== Palm Desktop 4.1.4 ==

	=== vCard import ===		=== vCard import ===

	Palm Desktop 4.1.4 appears to fail importing a vcard if it has a NAME specified in the vcard.		Palm Desktop 4.1.4 appears to fail importing a vcard if it has a NAME specified in the vcard.