Handle multilingual for dropdown label in content fragment

[afiq_zulkeflee]

Hi all hope you guys have a good day,

As the subject mention, currently in our AEM we have a content fragment template with an English dropdown label, and we would want to cater for other language (Mandarin for this case) without changing the original label. The reason for this is that we already have a lot of content fragment assets based on this template and manually change it would be a hassle. 

[EstebanBustamante · Accepted solution]

Hi, 

I am not sure if I understood correctly, but if you meant to translate "Park Name" from your dialog, you could use i18n to achieve that, here is a good resource explaining this: https://www.nextrow.com/blog/adobe-experience-manager/usecase-il8n-converting-components-based-userp... 

Hope this helps.

[kautuk_sahni]

@afiq_zulkeflee Did you find the suggestion helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!

[MonalikaKapoor]

Hi,

To address the need for multilingual support in your AEM Content Fragment templates without changing the original labels, let's explore the options available:

1. Custom Multifield with Language Support: Implement a custom multifield component that supports multiple languages. This would involve creating a custom dialog in your Content Fragment template where you can define labels for different languages.
2. Overlaying the Template Dialog: Overlay the existing Content Fragment template dialog to include language-specific fields. For example, add a dropdown for English and another for Mandarin within the same dialog.
3. Using AEM Translation Integration: Utilize AEM's translation integration [1] [2] capabilities to manage multilingual content. This involves using translation projects and connectors to automate the translation process. This provides a scalable and automated solution for managing multilingual content. It also integrates well with AEM's existing translation workflows.
4. Customizing the Content Fragment Model: Extend your Content Fragment model to include language-specific fields. For example, create separate fields for English and Mandarin labels within the same model. [3][4] 

I hope this helps!

Regards,
Monalika Kapoor

[1] https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/headless/journey...
[2] https://experienceleague.adobe.com/en/docs/experience-manager-65/content/sites/administering/introdu...
[3] https://experienceleague.adobe.com/en/docs/experience-manager-65/content/assets/content-fragments/co...
[4] https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/developing/ext...
[5] https://www.nextrow.com/blog/adobe-experience-manager/usecase-il8n-converting-components-based-userp...