On Fri, Jan 28, 2011 at 12:19:30AM +0000, Szemere Szemere wrote:
> I guess this is nothing new, as the following post hints at this:
> http://www.mail-archive.com/barry-devel@lists.sourceforge.net/msg02649.html
>
> but it seems the upldif filters out any contacts with base64 encoding. Is
> that right?
No, ldif.cc supports reading base64 encoding. It is just that the postal
address includes all fields, and splitting them into separate address,
city, country, postal code, etc. fields is not yet implemented in
the ContactLdif::SetWorkPostalAddress() and ContactLdif::SetHomePostalAddress()
functions.
You'll notice that if you pipe ldif fields through bio, fields like notes,
which is often encoded in base64 if there are multiple lines, do come through:
tools/bio -i device -p 3049da6d -d "Address Book" -o ldif | \
tools/bio -i ldif -o dump
> It affects about 5% of my records, so I will take a look at the source
> (sometime) to see about fixing it, if that makes sense.
I look forward to the patch! :-)
Thanks,
- Chris
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel
