Uploaded image for project: 'Identity Provider'
  1. Identity Provider
  2. IDP-1464

Do we need to rationalize language & locale handling

    XMLWordPrintable

    Details

      Description

      The way that language and locales are handled differs in code (if not much in result) between MDUI and attributes.

      Attribute handling uses Locales driver by getXMLLangAsLocale in AttributeSupport. This strips the location and just gives what should be a the two letter language

      MDUI uses the language string which comes from org.opensaml.core.xml.Langbearing and does full string comparison (so if you order things correctly you will see a difference between "en" "eb-gb" and "en-us").

      Neither are consistent, nor necessarily correct. The Locale provides what looks like reasonable methods for handling these things. Do we want to ratiinalize this.
      Such ratinalization might

      • make LangBearing return a Locale, not a string
      • make fuller use of Locale#forLanguageTag()
      • make fuller use of the (standards following) Locale#filter() methods.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              rdw@iay.org.uk Rod Widdowson
              Reporter:
              rdw@iay.org.uk Rod Widdowson
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 2 days, 1 hour, 20 minutes
                  2d 1h 20m