[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| | Regards,
| | Roman--- src/kbsequence.C.orig Sun Dec 17 07:09:34 2000
| | +++ src/kbsequence.C Thu May 10 00:04:44 2001
| | @@ -261,6 +261,11 @@
| | char kb_sequence::getiso() const
| | {
| | int const c = getsym();
| | +
| | + // Check if the keysym is in ISO Latin-2, -3 or -9.
| | + int byte3 = c / 0x100;
| | + if (byte3 == 0x01 || byte3 == 0x02 || byte3 == 0x13)
| | + return static_cast<char>(c % 0x100);
| |
| | if (c > 0xff)
| | return '\0';
|
| I have put something similar to this into CVS, but note that by using
| this you will not be able to mix latin1 and latin2 (++)
|
| How ever... this is possible by binding to keys instead:
|
| \bind "Zacute" "accent-acute Z"
|
| This will make Zacute avaliable even if you are using a latin1 font.
I took this idea a bit further and created the patch below.
This actually also uses the lfun "self-insert" the way it was intended
from the beginning (some 3-4 years ago). This means that some special
casing can go away (or rather to generalized cases like the
all-in-one-wonder "-1" lyxfunc)
The patch above should not be
needed anymore (even if it is included in this patch). the
latinkeys.bind file is not finished, and might also need some more
support ( a new lfun "special-char") to be able to show chars like
Lstroke regardless of what font norm is used (latin).
Ok, it would be nice if people could try this patch, fiddle with it
and see if it can potentially solve most of the latin-X problems.
(I belive that it can)
Better support for latin fonts in LyX
--
Lgb
