Angus Leeming <[EMAIL PROTECTED]> writes:
| On Tuesday 05 June 2001 11:16, Lars Gullik Bjønnes wrote:
| > Angus Leeming <[EMAIL PROTECTED]> writes:
| >
| > | I haven't understood a great deal of this conversation. That's not
| because I
| > | don't want to, just that I'm not at all familiar with font-stuff.
| > |
| > | However, if I could return it to C++ for a minute. I attach a tiny C++
| > | program that takes input
| > | \"a
| > | and creates the appropriate output
| > | ä
| > | using a map<string, string> to do the conversion
| >
| > One problem is that as long as we are not using unicode(wide chars)
| > interanlly we can't know if the fontencoding we are using contains ä
| > at all, so what to do then. This is also one area were LyX needs a bit
| > work.
|
| ;-) Not now it doesn't. As Asger suggests in his reply "Re: future of LyX"
| there are more than enough of LyX's internals spread out on the operating
| table at the moment.
|
| However, given that my desire was to produce pretty labels in the GUI, not
| inside LyX itself, I shall continue as I have. Ie, if I can create a
| character using the compose key, then it goes in the array, otherwise it
| won't.
|
| Incidentally, is there a resource somewhere describing the compose key
| combinations? At the moment I use guess work!
we already have this array in the .cdef files.
compose key combinations is mentioned in:
/usr/X11R6/lib/X11/locale/iso8859-1/Compose
f.ex.
--
Lgb
