Le 02/07/2011 22:24, Guenter Milde a écrit :
Frankly, inserting special characters is a nightmare to me. You look at
an endless list of unicode characters, and you only know whether they
render in the GUI main font. Then you insert it in the document, it
shows or not on your screen (depending on your screen font),
But this is a problem of every application, so I think it should not
prevent us from doing the right thing: using Unicode characters for
text symbols.
The goal is to use this character for documents we distribute. Internal
decisions are not relevant. The character shall display for most
reasonale screen fonts. Currently, the percentage of screen fonts with
the correct character is not high enough.
The situation might improve if we are able to use a glyph from TeX fonts
(which we do ship with LyX). Are we able to know whether a given glyph
is available in a font?
Finally, if it is an InsetSpace, we may give it properties related to
our line breaking algorithm (I am not sure which though).
The line-breaking algorithm should be able to work with Unicode characters,
too.
Is this information (nature of glyphs) available to us?
JMarc
