>>>>> "peter" == peter pilgrim <[EMAIL PROTECTED]> writes:
peter> Juergen Kreilender wrote:
>> >>>>> peter pilgrim writes:
>>
>> > I have had an irritating long term low priority problem with
>> > applications built with a static Motif library. When application
>> > display a XmTextWidget, the [RETURN] does not work. Ie the default
>> > widget translation:
>>
>> > ~Alt ~Shift ~Ctrl <Key>Return newline()
>>
>> > does not seem to work at all on my environment. The translation
>> > seems to be ignore. I tried setting the action to `activate()', I
>> > have __not__ been playing with the X keymap and the `~/.motifbind'
>> > file that I have around seems to be quite correct. I tried setting
>> > an override translation in my ~/.Xdefaults file and then asking
>> > `xrdb' to reload the file. No it did not work. This strange
>> > behaviour happens in the JDK and in Netscape. It seems that the
>> > virtual motif bindings for ``osfActivate'' dont work for me. BTW: I
>> > am using `fvwm 2'
>>
>> > My only solution is to use Ctrl-J a la GNU Emacs to get around.
>>
>> > Does any one know the cure for this weird behaviour?
>>
>> Did you try the LD_PRELOAD=libBrokenLocale.so trick?
Without this trick umlauts in text components don't work for me (glibc
motif applications only, e.g. JDK, netscape, ...).
We had several bug reports about entering text (not only umlauts) in text
components, for most people preloading libBrokenLocale.so solved the
problem.
Juergen
--
Juergen Kreileder, Universitaet Dortmund, Lehrstuhl Informatik V
Baroper Strasse 301, D-44221 Dortmund, Germany
Phone: ++49 231/755-5806, Fax: ++49 231/755-5802
