SUMMARY After entering text containing 1 or more instances of the string "st" into a field, each instance is converted into the Unicode ligature character 'st' (U+FB06, decimal 64262, https://www.fileformat.info/info/unicode/char/fb06/index.htm). For example, after entering text containing "justice", it appears as "justice", and the element doesn't appear when filtering on "justice". STEPS TO REPRODUCE 1. Add a new element, or edit an existing element. 2. Enter the string "st" into any text field. 3. Click on a different tab, or click OK, or change the pulldown menu to "Source Code" and back to "Plain Text". OBSERVED RESULT Each "st" string appears as the Unicode ligature character 'st'. The element doesn't appear when filtering for "st". EXPECTED RESULT Each "st" string appears as "st". The element appears when filtering for "st". SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.54.0 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.3 ADDITIONAL INFORMATION If you enter "justice" into a text field, then change the dropdown from "Plain Text" to "Source Code", it appears as "{justice}". That is, there's no ligature. Possibly "st" is stored correctly, but displayed incorrectly? Although searching for "st" still fails.
Due to a refactoring of code, this problem does no longer exist in KBibTeX 0.9 (Git branch kbibtex/0.9) and current master branch. Please test yourself by using the quick run instructions: https://userbase.kde.org/KBibTeX/Development#Quick_Start_to_Run_KBibTeX_from_Git Run script run-kbibtex.sh with the following invocation: bash run-kbibtex.sh https://anongit.kde.org/kbibtex.git kbibtex/0.9
Confirmed, that new version works fine. Thanks -- will look forward to it.
*** Bug 406692 has been marked as a duplicate of this bug. ***