[SLING-7582] Configuration for dictionary load order behaviour

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: i18n 2.5.12
• Component/s: i18n
• Assignee: Unassigned
• Reporter: Andreas Haller
• Created: 16/Apr/18 06:09
• Updated: 16/Apr/18 06:09

Description

Like stated in the documentation and the source code the load order of i18n dictionaries follows the ResourceResolvers search paths and is: /<others>, /libs, /apps which means /libs overrides /<others> and /apps overrides /libs. While I like the idea of using the search paths for loading dictionaries we have regularly the requirement of maintaining i18n dictionaries outside of /apps, see also https://issues.apache.org/jira/browse/SLING-4344?focusedCommentId=14297818&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-14297818

Considering this, in my opinion it would make sense to have a configuration option to load /<others> after /libs and /apps and having the possibility to override the applications out-of-the-box translations by dictionaries outside of the search path. My proposal is to extend the configuration of JcrResourceBundleProvider giving paths not on the search path (e.g. /content) priority over /libs and /apps.