Uploaded image for project: 'Service Packs and Hot Fixes'
  1. Service Packs and Hot Fixes
  2. MNT-5446

Customized Alfresco Share i18n properties do not handle 'short' locales

    Details

    • Type: Bug
    • Status: Closed
    • Resolution: Fixed
    • Affects Version/s: 4.0
    • Fix Version/s: 4.1.1
    • Component/s: Share Application
    • Labels:
      None
    • Environment:
      Alfresco Community 4.0.d, CentOS 6.2
    • Bug Priority:
      Category 2

      Description

      I tried to customize Web Script i18n as described on http://blogs.alfresco.com/wp/ddraper/2011/08/03/customizing-alfresco-share-i18n-properties/ and encountered strange extension behaviour.

      I'm using Alfresco 4.0.d and I tried to support two locales - English and Russian. The issue arises if the browser sends 'short' locales ('en', 'ru', etc) instead of 'long' ones ('en-US', 'ru-RU', etc).

      Test case #1:

      • I have only *_en.properties and *_ru.properties in extension, Share server is started with en_US.UTF-8 locale.

      Test case #1 results:

      • en-US browser locale - custom en message
      • ru-RU browser locale - custom ru message
      • en browser locale - default message - smth bad here
      • ru browser locale - custom en message - smth bad here

      Test case #2:

      • I have only *_en.properties and *_ru.properties in extension, Share server is started with ru_RU.UTF-8 locale.

      Test case #2 results:

      • en-US browser locale - custom en message
      • ru-RU browser locale - custom ru message
      • en browser locale - custom ru message - smth bad here
      • ru browser locale - default message - smth bad here

      Test case #3:

      • I have *_en.properties, *_ru.properties plus *.properties in extension, Share server is started with en_US.UTF-8 locale.

      Test case #3 results:

      • en-US browser locale - custom en message
      • ru-RU browser locale - custom ru message
      • en browser locale - custom en message
      • ru browser locale - custom en message - smth bad here

      Test case #4:

      • I have *_en.properties, *_ru.properties plus *.properties in extension, Share server is started with en_US.UTF-8 locale.

      Test case #4 results:

      • en-US browser locale - custom en message
      • ru-RU browser locale - custom ru message
      • en browser locale - custom ru message - smth bad here
      • ru browser locale - custom en message - smth bad here

        Attachments

          Structure

            Activity

              People

              • Assignee:
                closedbugs Closed Bugs (Inactive)
                Reporter:
                avasyukov Alexey Vasyukov (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Structure Helper Panel