<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="https://dev.horde.org/themes/horde//default/feed-rss.xsl" type="text/xsl"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 
 <channel> 
  <title>sync data corruption in firstname with spaces</title> 
  <pubDate>Fri, 10 Apr 2026 14:48:34 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/7895</link> 
  <atom:link rel="self" type="application/rss+xml" title="sync data corruption in firstname with spaces" href="https://bugs.horde.org/ticket/7895/rss" /> 
  <description>sync data corruption in firstname with spaces</description> 
 
   
   
  <item> 
   <title>Hi,



I setup my Nokia N85 to sync to my horde Addressbook.</title> 
   <description>Hi,



I setup my Nokia N85 to sync to my horde Addressbook.

For the addressbook, I use an LDAP backend with a schema of nokiaperson I created myself.



When I loaded my N85 users to the empty LDAP addressbook, I had one major problem. In case of spaces in the first name like in this data example:



Firstname = Core Mattias

Lastname = Verbruggen



in LDAP this became



cn = Core

sn = Mattias



and the data for lastname was gone.

This only happens when syncing because the LDAP address book from within Turba handles spaces in the firstnames just fine.



When I resynced afterwards (but changing the protocol from 1.2 to 1.1 on the phone), this doubled the number of addressbook entries in my phone.  Syncing again started tripling the data.

In horde on the other hand, only 10 entries were added unwanted compared to 500 in my phone.



Spaces in address entries did not cause troubles.



Now that I cleaned up my data without having any more spaces in firstnames, everything works fine.

I would love to help you testing this problem out by adding spaces again to my firstname fields.



gr,



Willem </description> 
   <pubDate>Mon, 26 Jan 2009 17:42:35 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7895#t51970</link> 
  </item> 
   
  <item> 
   <title>This almost sounds like the automatic last-name-detection in</title> 
   <description>This almost sounds like the automatic last-name-detection in Turba is triggered somewhere, even though that shouldn&#039;t happen if both Turba and the phone use separate fields for first name and last name. Can your post your sources.php and a data.txt from such a sync session?</description> 
   <pubDate>Thu, 29 Jan 2009 10:56:59 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7895#t52059</link> 
  </item> 
   
  <item> 
   <title>Hi,



data.txt contains (display from vi editor):



Input </title> 
   <description>Hi,



data.txt contains (display from vi editor):



Input received from client (text/x-vcard):

BEGIN:VCARD^M

VERSION:2.1^M

REV:20090129T135120Z^M

N:Verschueren;Test geert;;;^M

X-CLASS:private^M

TEL;CELL;HOME:0032477256138^M

END:VCARD



Result in LDAP attached in screenshot too.

Just let me know if you want more info from this session.

(It seems I can only attach one file at the time?)



gr,



Willem</description> 
   <pubDate>Thu, 29 Jan 2009 14:02:31 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7895#t52082</link> 
  </item> 
   
  <item> 
   <title>And here is the sources.php</title> 
   <description>And here is the sources.php</description> 
   <pubDate>Thu, 29 Jan 2009 14:08:32 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7895#t52083</link> 
  </item> 
   
  <item> 
   <title>That all looks fine. Does it also happen when importing that</title> 
   <description>That all looks fine. Does it also happen when importing that vCard manually into the address book?</description> 
   <pubDate>Thu, 29 Jan 2009 15:54:09 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7895#t52091</link> 
  </item> 
   
  <item> 
   <title>Yes it does.

Same error when importing manually.

</title> 
   <description>Yes it does.

Same error when importing manually.

</description> 
   <pubDate>Thu, 29 Jan 2009 17:57:14 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7895#t52101</link> 
  </item> 
   
  <item> 
   <title>Maybe some of our LDAP folks can take a look at it.</title> 
   <description>Maybe some of our LDAP folks can take a look at it.</description> 
   <pubDate>Thu, 29 Jan 2009 18:23:43 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7895#t52103</link> 
  </item> 
   
  <item> 
   <title>I just had the same problem today. I&#039;m running the Kolab Bun</title> 
   <description>I just had the same problem today. I&#039;m running the Kolab Bundle 2.2.1-beta1 under ubuntu 8.10. I synced my Nokia E71 via SyncML, and the same thing happened with last names with spaces. I have almost 200 last names with spaces as I have first and last names stored in there, because an older phone didn&#039;t support them separately.  Please let me know what I can do to help track down the problem.



Thanks, Nils

</description> 
   <pubDate>Wed, 04 Feb 2009 21:28:25 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7895#t52271</link> 
  </item> 
   
  <item> 
   <title>This is not LDAP related. Turba always cut the &quot;N&quot; field in </title> 
   <description>This is not LDAP related. Turba always cut the &quot;N&quot; field in vCard at the blanks so if you have any name with blanks it get split to VName MiddlName LastName. According to the RFC 2426 Turba import should only split at &quot;;&quot; as far as i can see.

Export works fine BTW, but import fails with SyncML and import by file.

If you have any device which have no concept of &quot;MiddlName&quot; then part of the name get lost.</description> 
   <pubDate>Tue, 01 Sep 2009 15:11:43 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7895#t55634</link> 
  </item> 
   
  <item> 
   <title>That sounds like a bug that had been fixed in CVS already. C</title> 
   <description>That sounds like a bug that had been fixed in CVS already. Can you try a snapshot?</description> 
   <pubDate>Fri, 04 Sep 2009 10:43:12 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7895#t55657</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
