Hello,
Thank you for the detailed questions! I will be happy to go through them one by one.
1.Is the “Exclude selectors only from automatic translation” feature available in the free version, or is it only available in the Pro version?
2. When using Google Cloud Translation API, can I exclude specific HTML elements (for example, by CSS selector or HTML attribute) from automatic translation so they are never sent to Google for translation?
4.Does this exclusion work correctly with dynamic content generated by plugins such as Directorist and BuddyPress, provided the content is wrapped in a specific HTML class or selector?
I can confirm that you can exclude these elements from automatic and dynamic translation, or exclude them from translation entirely, using the exclusion options described in our documentation here: https://translatepress.com/docs/developers/exclude-certain-text-or-element-from-being-translated/.
These exclusion features are also included in the free version.
Please make sure you have excluded all the desired elements before enabling automatic translation on your site.
3.If an element is excluded from automatic translation, can it still be translated manually later using the TranslatePress visual editor?
You can exclude the string or selector only from automatic translation, which will allow you to translate that element manually at any time from the Translation Editor.
If you exclude it from translation, this will apply to both automatic and manual translation, and you will need to remove this exclusion when you later decide to translate it manually – excluding it only from automatic translation instead, so that it is not translated automatically while automatic translation is active.
5.When using Google Cloud Translation API, are only new or modified texts sent for translation, or are previously translated texts sent again whenever a page is updated?
Automatic translation translates any untranslated content once it is viewed in the additional language.
Strings that are modified in the default language after they have been translated will lose their translations as a result of the changes, because the newly modified strings no longer match the ones stored in the database that have translations attached – even if the changes are minor. As a result, the modified strings (not the entire page) will lose their existing translations.
In this case, any untranslated content – whether newly added, or modified in the default language and therefore having lost its translation – will be re-translated by automatic translation when the page is viewed in the additional language by the admin, any user, or crawlers, if the Block Crawlers option in Settings → TranslatePress → Automatic Translation tab is unchecked.
Let me know if you have any further questions.
Kind regards,
Anca
