Abdelrazak Younes wrote: > To mitigate this problem I think we should only offer a view of the > symbols in current category. That's what MSWord and OO Writer do AFAIK.
We already have that. It doesn't help, though, since the categories need to be calculated nevertheless (the combo is still needed). What we can do is to unconditionally fill in all categories when we are using utf8. This should save some time. > > 2. lots of symbols are missing in the dialog. This is a general > > problem: if Qt cannot find a glyph in the font database, it inserts a > > white rectangle. I think we should insert something more remarkable > > (a red question mark or something), but I do not know how to check if > > a glyph is available. > > In the Qt doc, I see that they just use blank squares in the > CharacterWidget example: > > http://doc.trolltech.com/4.2/widgets-charactermap.html > > You could probably take inspiration from this example. Rather than this, we could use a QTableView. KCharSelect does this (but it involves proper model/view implementation, which is new land to me). > > If we had access to something like python's unicodedata in C++, we > > could also add nice tooltips displaying the name of the glyph. > > > > Ideas welcome. > > Ideas in no particular order: > - The information brought by QFontDatabase::writingSystem() seems > interesting to display. Hm, perhaps. Not sure. > - We should also try to change the font used as a function of the > selected category. I don't understand this. > - Now is probably a very good time to look at the stix fonts for GUI > purpose. well, I believe that when I see it. Jürgen
