Uploaded image for project: 'CiviCRM'
  1. CiviCRM
  2. CRM-14233

Use a standard such as BCP-47 for storing contact language preferences.

    Details

    • Type: Improvement
    • Status: Won't Do
    • Priority: Minor
    • Resolution: Won't Do
    • Affects Version/s: 4.4.4
    • Fix Version/s: Unscheduled
    • Component/s: Internationalisation
    • Labels:
      None
    • Versioning Impact:
      Patch (backwards-compatible bug fixes)

      Description

      The current representation of contact language as an enum is a blocker for the Wikimedia Foundation to upgrade from Civi 4.2. If it's convenient to display a select dropdown for most installations, that's one thing... but to constrain the possible languages to a fixed list doesn't make any sense.

      My suggestion is that we go back to free-form data, and adhere to a standard such as BCP-47. I've written a library that we could use to manage this data.

      We will gain: nullability of preferred_language, ability to represent a fallback chain of multiple languages spoken, and script preferences.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              adamw Adam Wight
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: