https://bugs.kde.org/show_bug.cgi?id=97420
--- Comment #10 from Ian <i...@zti.co.za> --- Hi I took a look at your proposal, thanks. I then realised what part of the problem is ... there are two different Use Cases for KCharSelect: 1. probably the original one, which probably dates all the way back to the similar program on Windows 3.1 ... you're typing something, need a ß character, and don't know the alt-xxxx/whatever code for it, so you fire up a Character Select program to find it, copy and paste. This use case predates Unicode. 2. Other use, (eg me) is to see which glyphs are in a font, and what they look like. This is to help in deciding which font to use for a particular job. In use case 1, you may be happy with QT/system substituting a glyph from a different font. In use case 2, you need to know exactly what's what. Use case 2 is actually "Font Browser" rather than Character Select, but the existing font browser on KDE is way underpowered for proper investigation of a font. (I guess it's also very old and possibly pre-unicode, where there were only a handful of glyphs in a font). So yes, your proposals will work for me, and are a definite improvement. My only issue is what is the default view, and that I suppose depends on whether you are targeting Use Case 1 or Use Case 2 .... I would prefer the greyed out as default, but I accept that those in Use Case 1 would prefer the other view. Thanks, Ian -- You are receiving this mail because: You are watching all bug changes.
