Authoring UI for I18N items - Status changed to: New

[#1]

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

[#2]

@hofftj  - FYI

[#3]

@mikeetiuPH 

Thanks for proposing this idea

This has been reported to the engineering under the internal reference SITES-7826. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to the Jira request status.

[#4]

@mikeetiuPH This has been accepted. 

[#5]

@mikeetiuPH This is in the development stage. It should be available by h2 24.

[#6]

@kautuk_sahni is there any updated status on the fix for this?

[#7]

@justinta2 Let me check and get back to you. 

[#8]

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. 

[#9]

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.

[#10]

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