Hi, 7 Apr 2026 20:30:01 +0200 Rodrigo Arias:
I don't think the matching algorithm would be trivial. For example, should "una" match both "una" and "uña" in Spanish? What about other languages?
That's fair. I would say that's the reason why it would have to be an optional filter, so users could disable it on those cases.
The current search algorithm matches bytes as-is. Trying to do something clever would require us to iterate by glyphs instead, which would be harder to implement and require more computational cost.
I would wait until we have strong evidence that this feature is needed and the cost of the implementation is worth it.
I agree. Thank you for considering it! For now, it's not so difficult to type the variations of words one want to find. Even for misspelled words: I can omit the accentuated character; on some cases, I may look for another related word, etc.
Thanks for testing! Be sure to use the latest commit of FLTK from their master branch in GitHub, as they contain recent fixes (few weeks ago) for font rendering.
I'll certainly check it out! I was using the Debian stable version: FLTK 1.4.3 Kind regards!