why doesn't kcharselect map all of unicode?
i've gotten obsessed with unicode over the past year, and kcharselect was at least partially a gateway for being such a good, accessible program to browse characters. i found out a while ago though that it doesn't have all of unicode mapped; just up to the codepoint of FFFF, while some select blocks of codepoints higher than that are mapped down for inclusion.
i also learnt that gnome's gucharmap seemingly does appear to have all of unicode mapped, so that confirms to me that it is at least technically feasible. i'm not crazy about the user interface of gucharmap though—or most gnome/gtk programs in general—so i still use kcharselect unless i want to browse characters outside of its purview.
i'm just wondering if there's a main reason for this. i'm sure it's a big undertaking with the sheer volume of characters in unicode, but from my perspective surely it'd only be a massive endeavour initially, and after that just an incremental process to keep up with unicode updates? i could see it as a matter of will, as in most of the characters of interest are covered and there's not really much desire for this to necessitate the work required, besides the occasional weird nerd like myself.
not meant to be a "why aren't devs doing more labour?" type post, i know absolutely nothing about programming and i'm just genuinely curious about this.