Looks like this is a regular expression problem. Relevanssi is using a regular expression to find the words to highlight, and that doesn’t work properly with Russian (or any other non-Latin alphabet).
I’ll have to see what I can do to fix this.
Yes, probably regex.
Here is some auto-generated russian text for you to test:
Мелькание мыслей, несмотря на внешние воздействия, притягивает полифонический роман, туда же попадает и еще недавно вызывавший безусловную симпатию гетевский Вертер. Лексика, чтобы уловить хореический ритм или аллитерацию на “л”, существенно осознаёт культурный строфоид, так как в данном случае роль наблюдателя опосредована ролью рассказчика. Поток сознания, на первый взгляд, разрушаем. Символ, если уловить хореический ритм или аллитерацию на “р”, традиционно вызывает музыкальный ритм, но языковая игра не приводит к активно-диалогическому пониманию.
Thank you!
Thanks for a new version! Now it works perfectly with Russian language!
Sorry to bother you again. I found another problem when using Russian language.
When I switch on relevanssi queries log, and then open the log, I see symbols like “пє instead of Russian queries 🙁
Check your database. The character set for the relevanssi_log table might be incorrect. The queries are put directly in the table and retrieved directly out of the table – so there should be no way to corrupt them in Relevanssi. It would seem the database is corrupting them, then.
The character set for the relevanssi_log table is the same as for other tables – utf8_general_ci. The entries in the tables are already corrupted. wp_relevanssi_excerpt_cache table has all the same settings, but it stores Russian characters normally. I will try to find the problem.
If I delete line 868 in relevanssi.php
$query = htmlentities($query, ENT_QUOTES);
it stores characters properly.
line $query = htmlentities($query, ENT_QUOTES, 'utf-8'); works fine for me.
Great! That crossed my mind, but I didn’t think it could be that. Well, I’ll have to fix it, then. Thanks for spotting this!
