Expand my Community achievements bar.

SOLVED

Having trouble creating language copy translations for custom cq dialog component

Avatar

Level 1

I am new to AEM, and have been working on creating a spa using angular. I have created a custom dialog content component to enter data into, which is then injected into the angular component via sling mode json. The issue I am having is that I am trying to create automated translations using language copies and ms translator, but have been completely unsuccessful in actually getting the content to translate from english to any other language I select. My setup and process looks something like the below. Thanks in advance for any help.

 

1. I have a custom cq:dialog component at a path like this "/apps/my-project/components/my-app-content-dialog-component", that is used to populate the data model for the angular app.

2. I have a page that loads my angular app component at a path like this http://localhost:4502/editor.html/content/my-project/us/en/my-app-component.html

3. I have populated content which I have entered for the english version at "/content/my-project/us/en/my-app-component"

4. I have then "en" page set as the root language page

5. I created a new language copy based on "/content/my-project/us/en/my-app-component", using ms translate, which I have setup with my account id.

6. After selecting a non english language to be created I select "Create structure only" 

7. I create the new page successfully, select it and see that the content for the custom dialog component has been transferred, but has not been translated.

8. I have no clue how to get the content to translate via the api.

 

Any ideas on what I am missing here? I have read about creating translations rules, etc, but I am either failing to set that up properly, or it is a red herring, and I'm missing something else.

 

 

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

SPA
1 Accepted Solution

Avatar

Correct answer by
Community Advisor

@CIsForCole for all the custom fields, you may need to setup translation rules on what properties to be included and what not.

 

Please refer to this explanatory video article on how to do that.

 

https://docs.adobe.com/content/help/en/experience-manager-learn/sites/translation/translation-rules-...

View solution in original post

2 Replies

Avatar

Correct answer by
Community Advisor

@CIsForCole for all the custom fields, you may need to setup translation rules on what properties to be included and what not.

 

Please refer to this explanatory video article on how to do that.

 

https://docs.adobe.com/content/help/en/experience-manager-learn/sites/translation/translation-rules-...