Authoring UI for I18N items

mikeetiuPH · 2022-07-26T17:10:26+00:00

Request for Feature Enhancement (RFE) Summary: There should be a UI accessible to authors that will allow them to manage dictionaries Use-case: Translation management Current/Experienced Behavior: The current UI is not accessible to authors (and probably not available in Cloud) which means, updating this will require authors to be dependent on admins or developers to make changes https://<hostname>:<port-number>/libs/cq/i18n/translator.html Improved/Expected Behavior: A UI within the Authoring console is available AEnvironment Details (AEM version/service pack, any other specifics if applicable): AEMaCS Customer-name/Organization name: Proquire Screenshot (if applicable): N/A Code package (if applicable): N/A

Forum|Forum|3 years ago
July 26, 2022
12 replies
1577 views

Request for Feature Enhancement (RFE) Summary:	There should be a UI accessible to authors that will allow them to manage dictionaries
Use-case:	Translation management
Current/Experienced Behavior:	The current UI is not accessible to authors (and probably not available in Cloud) which means, updating this will require authors to be dependent on admins or developers to make changes `https://<hostname>:<port-number>/libs/cq/i18n/translator.html`
Improved/Expected Behavior:	A UI within the Authoring console is available
AEnvironment Details (AEM version/service pack, any other specifics if applicable):	AEMaCS
Customer-name/Organization name:	Proquire
Screenshot (if applicable):	N/A
Code package (if applicable):	N/A

daniel-strmecki

New Participant

I definitely support this idea, and it should not require a separate, 3rd pary package.

Also, I don't see a need to store i18n dictionaries in /apps, it should be in /content.

narendiran_ravi

New Participant

Hi @justinta2 ,

Did you check this custom solution -https://github.com/orbinson/aem-dictionary-translator

J

justinta2

New Participant

@mathias_siegel any other updates on this issue from the Adobe side?

mikeetiuPHAuthor

New Participant

Cool, I think a product that can be used without the need for doing any customizations is always better

daniel-strmecki

New Participant

Just wanted to mention we've been using i18n dictionaries stored in /content for a long time now on AEMaaCS and it works fine. However we use the AEM translation management workflows, but a custom solution from the translation provider Languagewire.

M

Mathias_Siegel

Employee

Work in progress is to allow storing dictionaries in a new path under /content where they will be translatable with existing AEM translation management workflows, projects/jobs and ISV integration. Target is Q4'24, latest Q1'25.