Hi Wolfgang, thanks for digging the issue. At the time you've posted the first message, I've quickly checked that it is related to parsing the NOT bits, but had little time for real debugging and testing (should've delegated to AI, though). Your fix is very close to what I'd consider a general fix, it's just better to require a "word boundary" instead of space after "not":
var reNot_Parenthesis = /\s*(\-|not\b)?(\s*\()?/gi;
Interestingly enough, it's not necessary to add the boundary before "not", "knot" and "knot of" are found correctly already.
I've added the fix to the new version of the plugin, currently only in the
source file (
demo page doesn't have the plugin synced with the source yet).
среда, 14 января 2026 г. в 10:24:15 UTC+3, Wolfgang: