Hi!
Sure, I will help you don’t worry.
So after one quick peek I already see the problem. After changing to that language, the search ajax response is altered (very likely by the translator plugin), which is causing the problem. The original response should start with this, but on the translation it is altered like this.
Those are basically special delimiters to filter the ajax request before showing the results. If they are changed, then the plugin can’t fetch the data.
Optimally XHR requests should not be altered, that is a very bad idea. However if you can somehow add these delimiter words to the translation exception list, that may work as well:
___ASPSTART_HTML___
___ASPEND_HTML___
___ASPSTART_DATA___
___ASPEND_DATA___Unfortunately I don’t know how the translator works, but if you can add exceptions, then this could very likely solve the issue.