Committed, thanks! I tweaked the handling of workAddress and 
homeAddress in ldif.php, let me know if you have any questions about 
that. As I said to Matt on IRC I'd like to see a test for this so we 
can verify that at least the basic case works (just transform a piece 
of data and make sure it comes out right, not worrying about saving to 
Turba).

I moved the LDIF class to turba/lib/Data to avoid the BC issue.

Done.
Done.
Done.
Should this be moved to a Turba_Data package since it is very Turba specific?

I have still have a few things I would like to see changed:

- Please use "Copyright 2007 The Horde Project 
(http://www.horde.org/)" for the file header.

- Add a BC check in Turba so that the LDIF features will only be used 
with an recent enough Horde version.

- Always use curly braces.

- Is it possible to reduce the large "case" lists, i.e. by making them 
the "default" case, using in_array(), or similar?

We now support all elements from config/attributes.php that have 
counterparts in LDIF.

If addresses in Turba are split out, there is a one-to-one mapping to 
LDIF.  If they are not split out, the address is stored in one field, 
mozillaWorkStreet2 or mozillaHomeStreet2.

Needed? I don't know, I don't even need LDIF import. ;-) Some people 
might find it is useful, for example to migrate an addressbook from 
SQL to LDAP.

Anyway, the default Turba SQL scheme is only one of many possible, and 
we should at least support all elements from config/attributes.php 
that have counterparts in LDIF. Addresses don't necessarily have to be 
in one large text field.

Here is the first cut of the patch that supports import and export.   
It only works with mozilla LDIF files.  When exporting turba to LDIF, 
the homeAddress value is put into the homeStreet attribute without any 
attempt to break up the components of the address.  The same holds 
true for the workAddress and street attributes.  Is export actually 
needed given that export is not supported for pine and mulberry 
address books?

Bounty added:

http://horde.org/bounties/details.php#turba_ldif

Some links and code for implementation pointers.



http://www.phpclasses.org/browse/package/2360.html

http://phpldapadmin.cvs.sourceforge.net/phpldapadmin/phpldapadmin/lib/ldif_functions.php?view=markup

Moving to the Turba queue (we may end up implementing this in the 
Horde_Data package, but even that would be Framework, not Horde Base. 
anyway logically it makes sense to me with Turba).

I support that one. It's a pain to import from csv. There has to be a 
easier of getting a decent address book on the server (with phone 
numbers, addresses, web pages and so on). Thunderbird's address book 
exports in ldif, so it would be very useful to import that into turba.

I would be wonderful if the Horde Address Book would be able to import 
an LDIF file, like the kind Thunderbird will export for its address 
book. I believe such a feature would provide greater reliability in 
the importing of such information.



Of course, exporting to LDIF would be nice as well.