Привет. Там кодировка не только в плагине сломалась, а в некоторых местах тоже.
Hey. There the encoding is not only broken in the plugin, but in some places too.
What menu should be showing there? It could be that this menu is pulled from a plugin, so it is a plugin’s issue.
I do not remember what there should be. I deleted the plugin. Problem still exists.
You can temporarily change language to English and check what it shows then.
That’s weird. Can you show or lost what plugins you have installed?
That’s all, I figured it out. This problem with encoding is observed in the plugin “Search”
Search works fine for me in both Russian and English. Not sure what is happening. Maybe it’s your OS or region, don’t know.
I do not know. Problems with the encoding in the plug-ins “Search” and “Monitoring” appeared after the upgrade to the version of Openfire 4.2.2. The search plugin is not important to me, but I hope the monitoring plugin will fix it on this request [OF-1500] - Ignite Realtime Jira . Especially such a problem is observed not only in me
By the way, if you change the language to English, problems with the encoding in the “Monitoring” plug-in remain. I think it’s not a language
Actually it started with 4.2.1, but you probably skipped that version. For 4.2.1 one contributor has updated whole Russian translation (https://issues.igniterealtime.org/browse/OF-1452). Before that it was needed to replace every non-latin character in translation with unicode code like \u012e. So one developer has changed the encoding of some translation files, so it could be edited just in Russian https://issues.igniterealtime.org/browse/OF-1448. But only main translation files were encoded. All plugins stayed untouched, yet that contributor has translated them in Russian, so they show garbled now.
I have filed a ticket to encode all other files recently, but it haven’t get attention yet https://issues.igniterealtime.org/browse/OF-1517
Though it doesn’t explain why you still see them garbled when using English. That i don’t know why.
Hello.
I think reason in server environments or in browser. It detect russian settings and uses related translation file no matter which settings done in OF itself.
For me quick fix was to rename /opt/openfire/plugins/monitoring/i18n/monitoring_i18n_ru_RU.properties file.
This falled back to default translation for plugin. (I use English settings on OF web console).
This file looks like encoded correctly - in utf8.
So I think here two bugs:
1 - bug in detect env of server/browser and not using OF settings
2 - display russian translation in web console. maybe some reencoding while display translation… don’t know
PS
to get correct display we need to do “ISO-8859-1 > UTF-8” with text. Not with translation file content, but with that, what displayed in web console.
I use OF 4.2.3
Так что итоге что нужно сделать, чтобы кодировка отображалась нормально? Спасибо
I guess to wait for some of the developers to take a look at this.
Проблема решается следующим способом!
mv /usr/share/openfire/plugins/monitoring/i18n/monitoring_i18n_ru_RU.properties /usr/share/openfire/plugins/monitoring/i18n/monitoring_i18n_ru_RU.properties.bak
cp /usr/share/openfire/plugins/monitoring/i18n/monitoring_i18n.properties /usr/share/openfire/plugins/monitoring/i18n/monitoring_i18n_ru_RU.properties
service openfire restart
Well, in that case you will have English menus. It is better than unreadable characters, but not a proper solution. A workaround. One can also switch whole GUI to English language in the settings.
Даже если переключить графический интерфейс на английский проблема не уйдёт.
Плагин смотрит не на сервер OPENFIRE, а на саму операционную систему точнее её локализацию и пытается кривой кодировкой ISO-8859-1 что-то перевести на русский.