search

Mibew / mibew

Mibew Messenger - open-source live support application
https://mibew.org
Other
473 stars 204 forks source link

Non-localizable strings #240

Closed tilkov closed 5 years ago

tilkov commented 5 years ago

Environment

Expected behavior

When switching the language of Mibew, all translated strings should work.

Actual behavior

On Visitors and on the client chat the localized text is still in English. I have three languages installed, besides English: bg, ro and el. The strings in question are translated in all of them, but are not used. Here are the non-localizable strings in the following screenshots: screenshot_20190116_083926 screenshot_20190116_084008 screenshot_20190116_084142

Steps to reproduce the behavior

Switch Language, The above items remain in English.

faf commented 5 years ago

As far as I understand all non-translated values comes from the client-side part of Mibew. That part gets localized strings from /locales/XX/translation.js where XX stands for two-lettered code of a locale.

So, let's start with the simpliest test. Just manually open the aforementioned file for any locale in question in your Mibew installation. What will you get?

tilkov commented 5 years ago

Hi,

I don't have that file in any translation, even in English. In every /locales/XX/ i have:

button canned_messages.yml config.yml mail_templates.yml translation.po

faf commented 5 years ago

Sure, there are no such file in the filesystem. It's generated by Mibew for a browser on demand.

By "open" I meant "open in browser".

tilkov commented 5 years ago

It must be the Nginx config then.

I just found you explaining it here

Thank you for pointing me at the right direction.

If possible, please include example nginx config in the documentation.

faf commented 5 years ago

Yeah, now I remember, there were a number of issues related to nginx and client-side translation back then in 2015. :)

As of documentation... I'll think about it.