Hi @ana-mariam85621,
@ArpitVarshney is right about the way you can include the CF in a translation if you use the OOTB component for including content fragments:
assetNode assetReferenceAttribute="fileReference" resourceType="dam/cfm/components/contentfragment"/>
But keep in mind that this works properly for AEM 6.4 only if you have a service pack grater or equal to 6.4.6. (See this one for details: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/unable-to-translate-conten...)
If you use a custom component, you must add the resource type of you custom component as the assetNode resourceType (not the resource type of the field that you use for including the CF, and not the model of the CF), and the name of the property that holds the reference to the CF as your assetNode assetReferenceAttribute value (in your case, the fieldname of the pathbrowser)
assetNode assetReferenceAttribute="promoTooltipCFReference" resourceType="resource_type_of_your_custom_component"/>
After adding this, all the default properties of that CF will be translated.
Since your CF has a custom model, make sure that you add all your custom fieldnames under the /content/dam path:
<node path="/content/dam">
<property name="tooltipName"/>
</node>