Details
-
Type: Improvement
-
Status: Done/Fixed
-
Priority: Trivial
-
Resolution: Won't Fix
-
Affects Version/s: 4.0.7
-
Fix Version/s: Unscheduled
-
Component/s: Core CiviCRM
-
Labels:None
-
Versioning Impact:Patch (backwards-compatible bug fixes)
-
Documentation Required?:None
-
Funding Source:Needs Funding
Description
Create a new issue following this one http://issues.civicrm.org/jira/browse/CRM-3166
People don't use the proper iso code. They use UK instead of GB, USA instead of US and so on. I've spent way to many hours fixing that because my users can't import "and civicrm doesn't work". Either my users are dummer than the average civi user or are the only ones dealing with countries, or I'm the only provider that's getting vocal on that one?
Anyway, can we agree that Civi as a community doesn't have as a main goal to teach users ISO 3166 alpha-2 ?
I have 3 options:
1) quick and easy:
modify the import code to hard code the two cases that are a pita for me (UK->GB, USA->US) and call it a day
2) or add a new option list "country aliases" where we can populate some "translations", and end users can add more if they want (eg some of the official names are way not the names that are used, and I've never heard someone going to "Tanzania, United Republic" for a safari
3) I maintain my patch for 1 as my "vendor branch" and stop bothering you with that
Pick up your poison
X+