Jürgen Spitzmüller wrote:
Jürgen Spitzmüller wrote:
If we allowed all unicode symbols, be it in utf8 inputenc or XeTeX
(which we do not support yet properly), this would ask for trouble,
since neither in inputenc nor with XeTeX you can just insert any
unicode char without further ado.
having written this, there is indeed something wrong: if you use
another than the default encoding for the document, we have to check
for that. The attached patch fixes this.
However, if you use utf8, you'll see two drawbacks:
1. the dialog becomes slow. This is mainly because of the expensive
category handling.
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.
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.
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.
- We should also try to change the font used as a function of the
selected category.
- Now is probably a very good time to look at the stix fonts for GUI
purpose.
Abdel.
