| Request for Feature Enhancement (RFE) Summary: |
Remove Content Fragment jcr:title from being included for translation by default when using option "Enable Model Fields for Translation" |
| Use-case: |
For translation rules for CF I don't want to maintain rules in the translation_rules.xml file, instead I want to give just the creator of the CF Model the chance to define which fields should considered for translation by setting the field "translatable".
With current situation creator of CF Model does in fact have NO full control as jcr:title is always translated (creating costs for translation that I do not want to pay. Hence feature is useless as I need to maintain my translation rules manually.
|
| Current/Experienced Behavior: |
Even if I use the option "Enable Content Model Fields for Translation" to use the Translatable field of the Content Fragment Model in order to control which fields should be translated, the jcr:title of the CF is in by default. I can not exclude it and therefore is creates unnecessary costs. This makes no sense, as on the one hand you handover the control for translatable fields on creator of the Content Fragment Model, on the other hand you define the jcr:title to be translated by default with no option to control.
See: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/sites/administer...
|
| Improved/Expected Behavior: |
Remove CF jcr:title from being translated by default and give creator of CF Models FULL control over fields to be translated. Actually it makes no sense to translate the jcr:title of a CF as it makes more sense to keep this in one language (English) for common readability in AEM UI. |
| Environment Details (AEM version/service pack, any other specifics if applicable): |
|
| Customer-name/Organization name: |
Carl Zeiss AG |
| Screenshot (if applicable): |
|
| Code package (if applicable): |
|
