https://bugs.kde.org/show_bug.cgi?id=505968
--- Comment #2 from [email protected] --- (In reply to tagwerk19 from comment #1) > ... It would be interesting to know... I'm testing this on a Neon Unstable system... What I tried was: $ echo 云鹤 > 云鹤.txt $ cat 云鹤.txt 云鹤 $ balooshow6 -x 云鹤.txt 140087ed0da2dd 3977093853 1310855 云鹤.txt [/home/test/Documents/云鹤.txt] Mtime: 1750624009 2025-06-22T22:26:49 Ctime: 1750624009 2025-06-22T22:26:49 Cached properties: Line Count: 1 Internal Info File Name Terms: Ftxt F云鹤 XAttr Terms: Plain Text Terms: 浜戦工 Property Terms: Mplain Mtext T5 T8 X20-1 lineCount: 1 What's interesting is that the filename terms and the plain text terms, the "file content", differ. A baloosearch finds the filename match but not the content match: $ baloosearch6 filename:云鹤 /home/test/Documents/云鹤.txt Elapsed: 0.32654 msecs $ baloosearch6 content:云鹤 Elapsed: 0.339796 msecs A content search for the term shown by balooshow, works: $ baloosearch6 content:浜戦工 /home/test/Documents/云鹤.txt I'm using the command line tools to make sure we are testing *just* the Baloo logic. So something is wrong, 云鹤 is being indexed as 浜戦工 (when indexing the file content). Sorry, I cannot say whether this makes any sort of sense. -- You are receiving this mail because: You are watching all bug changes.
