Hi @ammbra ,
Can you try adding your content fragment by using the Content Fragment component of the General Category and confirm whether that is working fine?
I have tried using the general Content fragment component and then select the content fragment path inside that and it works well for me. It is sending the corresponding CF to translation.
The Content Fragment component is used to hold a reference to a content fragment asset (effectively enhanced text assets).
- The resource type for the content fragment is: dam/cfm/components/contentfragment/contentfragment
- The reference is defined in the property: fileReference
So below translation_rule for this one is used to fetch the corresponding asset.
assetNode assetReferenceAttribute="fileReference" resourceType="dam/cfm/components/contentfragment"/>
Also, you can add just the CF in your translation job and check if that is going successfully for translation, and that way you can be sure that the translation of CF is working fine and the issue in your custom component when you refer the CF.
You can refer the OOB component located at /libs/dam/cfm/components/contentfragment if you want to achieve something like that as it contains some additional property like element, variation to recognize the content fragment.
Also, you might need to change your resource type in translation rules if you are not using the OOB component.