[Tickets #11692] Kolab backend: Handling of 'country' field

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/11692
------------------------------------------------------------------------------
  Ticket             | 11692
  Created By         | Thomas Jarosch <thomas.jarosch at intra2net.com>
  Summary            | Kolab backend: Handling of 'country' field
  Queue              | Turba
  Version            | Git master
  Type               | Bug
  State              | Unconfirmed
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Thomas Jarosch <thomas.jarosch at intra2net.com> (2012-11-12 16:23) wrote:

Hi,

I'm currently testing the interoperability between Horde's Kolab  
implementation and other Kolab clients.

Kolab defines the "country" field just as a text field. Other clients  
(like Outlook) write out the full country name. Horde expects a  
country code, so it will hide/lose the country information.

Two ideas to solve this:
1. Do a country name lookup and try to match it to Horde's convention.
     "Germany" -> "DE".

2. Allow custom strings as with the "category" tag:
     Unknown categories from foreign Kolab clients just get imported.


Problem with the first idea is that another client won't be able read  
back Horde's country code.
So essentially, if the contact gets edited in Horde, the country  
information would change.
-> Probably only idea number two makes sense in the long run.

Thoughts?

Cheers,
Thomas