[DOCU-2059] Ability to support both Java8 and Java7 locale names in configuration Created: 13/Oct/20  Updated: 04/Jan/21  Resolved: 19/Oct/20

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: 6.2.4
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Federico Grilli Assignee: Ashraf Khamis
Resolution: Done Votes: 0
Labels: i18n
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
documentation
documents MAGNOLIA-7897 Provide Compatibility And Documentati... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: 2020 mgnl-staff requests
Sprint: Docu Sprint 79
Story Points: 1

 Description   

The locale names in Java8 replace the ones in Java 7, e.g. en_GB became en-GB

As of MAGNOLIA-7897 Magnolia can seamlessly support both formats in configuration, e.g. property fallbackLocale at https://documentation.magnolia-cms.com/display/DOCS62/Language+configuration#Languageconfiguration-3.Definelocalesinsite.

Probably worth mentioning it in our docu, besides the fact that the new Java8 locale names are preferred anyway.



 Comments   
Comment by Ashraf Khamis [ 19/Oct/20 ]

Added the following note to Available system languages and Define locales in site at https://documentation.magnolia-cms.com/display/DOCS62/Language+configuration:

From Magnolia 6.2.4, both Java 8 and Java 7 locale IDs are supported in configuration.

Replaced all underscores with dashes where appropriate:

All changes reviewed by Rico.

Comment by Jan Haderka [ 04/Jan/21 ]

Shouldn't this be mentioned also in the release notes for 6.2-6.2.3 releases as known issue?

Comment by Ashraf Khamis [ 04/Jan/21 ]

had It's already in the 6.2.4 RN: https://docs.magnolia-cms.com/product-docs/Releases/Release-notes-for-Magnolia-CMS-6.2.4.html#_support_for_java_7_locale_ids

The "Known issues" page typically includes only those that still affect the most recently released version of a given branch.

Generated at Mon Feb 12 01:23:40 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.