| commit | b608bea0b51b0f24fbf1fada87d3ad7abbb9a07b | |
| author | Chris Frey <cdfrey@foursquare.net> | |
| Mon, 19 Apr 2010 22:54:05 +0000 (19 18:54 -0400) | ||
| committer | Chris Frey <cdfrey@foursquare.net> | |
| Mon, 19 Apr 2010 22:57:57 +0000 (19 18:57 -0400) | ||
| tree | 5df778a9e3a4b004b21e235bc20ec6fa646b3a3d | treesnapshot (tar.gz zip) |
| parent | bb079c374d98a1561c977b7da39260e78895821d | commitdiff |
lib: added LDIF mapping support for Contact::Image fields
Note that jpegPhoto looks like the only LDIF field for photo images... it
is unknown which format will come from the BlackBerry in the Image field,
so we can't guarantee that "Image" will be in JPG format.
Therefore the LDIF mapping of "jpegPhoto" to "Image" is not done
automatically.
The LDIF mapping can be done manually from the btool command line
with "-m jpegPhoto,Image,Image" and hope that your LDAP software
and your BlackBerry uses JPG.
Reading photos from LDIF should be fine, since the BlackBerry
seems to handle most formats, when going in the LDIF -> BlackBerry
direction.
Note that jpegPhoto looks like the only LDIF field for photo images... it
is unknown which format will come from the BlackBerry in the Image field,
so we can't guarantee that "Image" will be in JPG format.
Therefore the LDIF mapping of "jpegPhoto" to "Image" is not done
automatically.
The LDIF mapping can be done manually from the btool command line
with "-m jpegPhoto,Image,Image" and hope that your LDAP software
and your BlackBerry uses JPG.
Reading photos from LDIF should be fine, since the BlackBerry
seems to handle most formats, when going in the LDIF -> BlackBerry
direction.
| src/ldif.cc | diffblobblamehistory | |
| src/ldif.h | diffblobblamehistory |