Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-3103

Encoding issue - Norwegian char in user name

XMLWordPrintable

      We have set up our Confluence using AD-integration for authentication. Several users have norwegian characters (æøåÆØÅ) in their user names.

      There seems to be an encoding issue when creating links to users profile pages. For instance with the user name 'øystein test':

      Create profile link:
      øystein test

      The resulting URL turns out to be:
      https://.../confluence/display/~%25C3%25B8ystein%2Btest

      Seems the character 'ø' is double encoded to %25C3%25B8, while it should be %F8. The correct url would be something like this (which works):
      https://.../confluence/display/~%F8ystein%2Btest

      Regular pages in confluence with Norwegian chars in names work fine. The problem only occurs with user names.

      There is also an issue with the search box. When entering 'øystein test' in the search field and pressing the search button, no results are found and the name has been changed to 'øystein test'. The inline search works fine, for example:

      {search:query=øystein test}

      .

          Form Name

            [CONFSERVER-3103] Encoding issue - Norwegian char in user name

            Jeremy Higgs added a comment -

            Hi Eivind,

            We have fixed a bunch of bugs relating to UTF-8 encoded characters (such as the Norwegian ones you mentioned), and this seems to have been fixed in the process. It'll be fixed in the upcoming 1.5 release.

            Jeremy.

            Jeremy Higgs added a comment - Hi Eivind, We have fixed a bunch of bugs relating to UTF-8 encoded characters (such as the Norwegian ones you mentioned), and this seems to have been fixed in the process. It'll be fixed in the upcoming 1.5 release. Jeremy.

            Nick Faiz [OLD] (Inactive) added a comment -

            Scheduling this for 1.4.1 - it will probably become part of our greater i18n issue, however, and, in that case, might be pushed back.

            Nick Faiz [OLD] (Inactive) added a comment - Scheduling this for 1.4.1 - it will probably become part of our greater i18n issue, however, and, in that case, might be pushed back.

            jens added a comment -

            Eivind,

            Thank you for letting us know about this. We will investigate this issue further.

            Cheers,
            Jens

            jens added a comment - Eivind, Thank you for letting us know about this. We will investigate this issue further. Cheers, Jens

              8d92d19feb5e Jeremy Higgs
              22fbd71139de Eivind Waaler
              Affected customers:
              1 This affects my team
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: