Last modified: 2014-02-11 13:44:32 UTC
Sometimes we see weird results in the prefix search because Cirrus uses different matching rules then the jquery.suggestions library. For example, in English, Cirrus is flattens high ascii so searching for "resume" will return "résumé". Cirrus is quite capable of highlighting the result properly, but it has no way to tell the front end what the result should look like. I don't believe it would be practical to replicate Cirrus's logic on the front end because it can change and it is different for different wikis.
I don't care how you do this, but please do. I hate the core search suggestions module. Core could totally also output match indices from the opensearch API (that shouldn't be incompatible with anything, but I haven't checked), naively by default (we could just implement the same logic as the JS module has now), with a hook override for better search extensions. Then we could apply bolding in the UI trivially based on these indices.
I'm glad it has bothered someone else too.
