Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| >>>>> "Jacques" == Jacques B Siboni <[EMAIL PROTECTED]> writes:
|
| Jacques> But presently the problem occurs with lyx editor: generation
| Jacques> of accented characters is ok 'e leads to é `e leads to è "e
| Jacques> leads to ë but generation of standard apostrophe, double
| Jacques> quote, caret (^), tilde and back quote are impossible. Lyx
| Jacques> refuses I get the accent that would be upon a character.
| Jacques> Generated LateX is \i \'{ } instead of '
|
| Hello,
|
| I can confirm this problem, which existed already in 1.0.3, as far as
| I can tell.
|
| Jacques> I believe it is a known problem.
|
| No, it was not. Thanks for reporting it. I have moved the discussion
| to lyx-devel so that a fix can be devised.
|
| Lars, I do not understand the use of the isDeadEvent() function in
| lyxlookup. I thought at the time that it was to avoid a clash with our
| own dead key handling. However, now that I think about it, LyX dead
| key handling is done mainly on plain characters. For example,
| \kmod ' acute aAcCeEiIjJlLnNoOsSuUzZ
| will act on a real ascii quote character, not on a ' dead key. So, why
| is it necessary to filter dead key events at all?
You, tell me. All this was added a lot later than my initial _X_
dead_key support.
Is this deadkey handling only wrong when a keymap is used? or always?
Lgb
