| Request for Feature Enhancement (RFE) Summary: |
Currently, the list of available languages displayed in the Language Copy dropdown is sourced from the out‑of‑the‑box definitions located in /libs/wcm/core/resources/languages. To add or customize languages (such as adding Kazakhstan using ISO code “kk” or “kk‑KZ”), customers must overlay this resource to /apps/wcm/core/resources/languages. This enhancement proposes introducing a configurable authoring dialog (or admin interface) that allows administrators to manage the languages list in the Language Copy feature without the need to overlay OOTB files.
Problem Statement:
- Current Behavior:
- The list of supported languages is static and defined in the repository under
/libs/wcm/core/resources/languages.
- Customizations require creating an overlay (
/apps/wcm/core/resources/languages), which is manual, error‑prone, and requires technical expertise.
- Impact:
- Customers who need to add or update language definitions (for example, when a new language like Kazakhstan is needed) must rely on a technical workaround.
- This process prevents non‑technical users (or content administrators) from easily managing the list and can lead to inconsistencies.
Proposed Solution:
Develop a new configuration dialog or admin interface that:
- Provides a user-friendly interface for managing the list of locales available in the Language Copy dropdown.
- Allows administrators to:
- Add new language entries (e.g., defining the ISO code, display name, and any associated metadata).
- Edit or remove existing entries.
- Reorder the languages as needed.
- Integrates seamlessly with the existing language copy functionality so that any changes in the dialog take immediate effect in the target dropdown.
- Uses a persisted configuration, such as an OSGi configuration or JCR node under
/apps, ensuring that changes remain consistent across updates and do not rely on repository overlays of OOTB files.
Benefits:
- Improved Usability: Authors and administrators can manage language definitions in a straightforward, non‑technical manner without editing repository files.
- Flexibility: The languages list becomes easily configurable, allowing for quick adaptations (e.g., new language support, corrections to existing definitions).
- Reduced Maintenance Overhead: Eliminates the need to overlay and maintain duplicate resources, reducing the risk of misconfiguration after updates.
|
