Question about Dutch translation of front-end labels in ChatGPT Assistant Pro

Hello,I am setting up ChatGPT Assistant Pro for a Dutch website. I created a Dutch translation file at: The site default language is set to nl-NL and the Dutch language pack is installed and active.However, the chat interface labels (Send button, placeholder text "Type your message here...", etc.) remain in English, despite cache being cleared on all levels (Joomla, JCH Optimize, YOOtheme Pro, browser).To diagnose, I also tried modifying the en-GB file directly with a test value, but that change is also not visible on the front-end. This suggests the labels are not loaded from the .ini file at runtime, but might be hardcoded in JavaScript or compiled into an asset.Could you confirm:

1. Are the chat interface labels (PLACEHOLDER, SEND_BUTTON, CLOSE, etc.) loaded from the .ini language file at runtime, or are they baked into JavaScript?
2. If from .ini, is there a specific way to clear a translation cache that I might be missing?
3. If from JavaScript, what is the recommended way to translate these labels for non-English sites?

Thank you for your help.Kind regards, Nico

Hello Nico and thank you for posting!

Generally speaking, all of our extensions are 100% translatable. Sometimes we add text options for more commonly changed texts, but this is not such a case.

The labels you refer to are indeed loaded from the file you mentioned. That is, if you are using the module interface. If you are using a menu item, you should translate
Sometimes, even if your content is actually written in Dutch, your Joomla content language in the settings is English. This may also be true for the module's specific setting (it may be set to English).
It was very smart to test the English file as well. It should have worked. Perhaps something was cached at the moment that you were trying to change the English file?

I'm wondering if a combination of settings caused both files to be loaded.

We do have clients who use ChatGPT Assistant Pro in multilingual websites, and we haven't had an issue with that before, as far as I can remember.
It's hard to say anything more specific without more details, but I confirm that this is the expected behavior.