Re: Problem with dead keys
Jean-Marc,
I have found a quick dirty solution to the dead keys problem; I totally
deactivate the deadkey event check in sub 'isDeadEvent' in file lyxlookup.C;
I force a return value of 'false' in all cases.
This solves the problem by now waiting for a smarter solution!
Eventually it could be a configure directive or a preprocessor directive or
whatever you think is appropriate.
Bien amicalement
Jacques
Jean-Marc Lasgouttes wrote:
"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?
JMarc
--
Dr. Jacques B. Siboni mailto:[EMAIL PROTECTED]
8 pass. Charles Albert, F75018 Paris, France
Tel. Fax: 33 (0) 1 42 28 76 78
Home Page: http://www.lutecium.fr/jacsib/
Re: Problem with dead keys
Jean-Marc,
I have found a quick & dirty solution to the dead keys problem; I totally
deactivate the deadkey event check in sub 'isDeadEvent' in file lyxlookup.C;
I force a return value of 'false' in all cases.
This solves the problem by now waiting for a smarter solution!
Eventually it could be a configure directive or a preprocessor directive or
whatever you think is appropriate.
Bien amicalement
Jacques
Jean-Marc Lasgouttes wrote:
>
> > "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?
>
> JMarc
--
Dr. Jacques B. Siboni mailto:[EMAIL PROTECTED]
8 pass. Charles Albert, F75018 Paris, France
Tel. & Fax: 33 (0) 1 42 28 76 78
Home Page: http://www.lutecium.fr/jacsib/
Re: Problem with dead keys
"Lars" == Lars Gullik Bjønnes [EMAIL PROTECTED] writes:
Lars You, tell me. All this was added a lot later than my initial _X_
Lars dead_key support.
In fact, it is you who added this code in lyxlookup.C.
Lars Is this deadkey handling only wrong when a keymap is used? or
Lars always?
OK, there is code in lyxrc.C like:
bindKey("~C-~S-~M-dead_acute", LFUN_ACUTE);
We could maybe conditionize it to some lyxrc variable to select
whether LyX should take over the handling of dead keys. I think there
should be an option allowing dead keys to work like in any other X
app.
JMarc
Re: Problem with dead keys
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> You, tell me. All this was added a lot later than my initial _X_
Lars> dead_key support.
In fact, it is you who added this code in lyxlookup.C.
Lars> Is this deadkey handling only wrong when a keymap is used? or
Lars> always?
OK, there is code in lyxrc.C like:
bindKey("~C-~S-~M-dead_acute", LFUN_ACUTE);
We could maybe conditionize it to some lyxrc variable to select
whether LyX should take over the handling of dead keys. I think there
should be an option allowing dead keys to work like in any other X
app.
JMarc
Re: Problem with dead keys
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
Re: Problem with dead keys
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
Re: Problem with dead keys
"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?
JMarc
Re: Problem with dead keys
> "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?
JMarc
