Abdelrazak Younes wrote: > Or we could fill in all category once and for all at construction and > then filter the displayed category depending on the encoding used.
I'm just working on something like this. > Yes, using a View/Model is always better than using the convenience > Widget class that Qt is providing (like QListWidget). A follow-up project for someone. > I mean the font used in the symbolsLW list widget. Depending on the code > range we can choose this or that font for display using > QListWidgetItem::setFont(). Some fonts are appropriate for Latin1, some > others for Symbols, others for Arabic, etc. Of course this means that we > maintain a codepoint / font correspondence table somewhere like what we > do for the modern fonts for math. I thought Qt already looks for the glyph in different fonts. Actually, I get good results here. Only some glyphs seem to be unavailable in any font I have installed. > >> - Now is probably a very good time to look at the stix fonts for GUI > >> purpose. > > > > well, I believe that when I see it. > > I am not talking about LateX, only about GUI. Some project (matplotlib) > are already making use of the fonts with success. I am talking about > getting rid of the modern fonts (the Bakoma package). Sure. Just kidding. The stix project was announced for so long that some people already categorized it as vapourware. But obviously they're making progress. Jürgen
