Search in Cyrillic

timur

I have used this app for a few days and this is what I have found: I cannot use the search function because I am typing my journal in the Cyrillic alphabet. When I start entering a word or a phrase, the app shows all the options as long as I enter 1 or 2 letters. But when I write the third or fourth letter, the search results cut down to 1 or 0 even when I am completely certain there are a lot more. For example, if a diary entry begins with "Выспался", entering "Вы" will highlight this word, but entering "Выс" will not show it in the search results.

Diarium version: 2.9.64
OS + version: Android 12

timo

I am unable to reproduce this problem using your example. I tried on both Windows and Android

Can you provide more infos on this?

timur

timo Updated the app, seems to be working for me, idk what that was about. However, I have found another related bug: search in cyrillics is now case sensetive for some reason. If the entry says "МОШ", and I type "мош", it doesn't find it, whereas with "МОШ" it does.

However, if I type "Мош", it will be found both with "мош" and "Мош". I think there is something weird gling on.

Same phone, Diarium 2.9.72

timo

Thanks for that example, I am able to reproduce it now.
The issue is indeed that the search term is differently cased than what is in the database. Diarium stores the text in HTML, which causes many characters to be HTML-encoded. This causes various problems when search for the text (another issue was described here). I don't know if or with how much computational effort it is possible to still find higher/lower cased characters that are encoded (normal ASCII-text is not encoded and therefore can be found easily).

Edit: Looking at it again, cyrillic characters actually aren't encoded. But the SQLite search engine still can't find characters that have a different case. I will dive deeper into this...

timo

Next update will have this issue fixed (at least for cryillic characters - there are still some small problems when searching for certain latin characters (like ü) but this will resolved with a later update as this requires a database migration).