Re: [opensuse-kde3] Missing writing accents
Hi Ray, Thanks for your reply. I tried out some of your advive but it doesn't solve it. The problem is not with the X server because Compose works in non-KDE3 applications like xterm or GTK applications like gvim. It fails only with KDE3 applications like konsole or kate. The problem lies with how KDE3 applications handle signals. As I wrote in my previous e-mail, if I `ssh localhost` and then start a new konsole (as if I was logging in remotely), then Compose works in that new konsole. This is a workaround for now, but I would like to understand what the difference is between a KDE3 app started directly and started after `ssh localhost`. It might have something to do with DCOP. What does DCOP do? If somebody with KDE3 development experience could please give me advice, it would be appreciated. Thanks, Gianluca On Tue, 10 Jul 2018, Ray Vine wrote:
This might be an option for you - it works for me in KDE3, but I don't use SuSE, so let's hope it will work on your build.
Assuming you're using a US keyboard layout, set this up in Control Center:
Layout: English (US) Keyboard model: Generic 101-key PC Layout variant: alt-intl
and you should see: Command: setxkbmap -model pc101 -layout us -variant alt-intl
Then, for example, where AC11 is the apostrophe/doublequote key:
é [e acute] is AC11 then e É [E acute] is AC11 then shift+e ü [u umlaut] is shift+AC11 then u Ü [U umlaut] is shift+AC11 then shift+u
The dead keys are shown in the /etc/X11/xkb/symbols/us file [from the xkeyboard-config package on my system]:
key <AC11> { [dead_acute, dead_diaeresis, apostrophe, quotedbl ] };
and the order is key shift+key AltGr+key AltGr+shift+key
Personally, I wouldn't like this and would rather have the dead keys on the AltGr key, leaving the AC11 key for it's usual function - apostrophe/doublequote. In which case, edit /etc/X11/xkb/symbols/us in the 'xkb_symbols "alt-intl"' section:
key <AC11> { [ apostrophe, quotedbl, dead_acute, dead_diaeresis ] };
and then: é [e acute] is AltGr+AC11 then e É [E acute] is AltGr+AC11 then shift+e ü [u umlaut] is AltGr+shift+AC11 then u Ü [U umlaut] is AltGr+shift+AC11 then shift+u
You'll probably have to restart X for the changes to take affect.
Another option you might prefer .. There's another section - xkb_symbols "intl" - in the 'us' symbols file with a greater range of key mappings like:
key <AD06> { [ y, Y, udiaeresis, Udiaeresis ] };
where 'u umlaut' is just AltGr+y
---------------
I think the best solution is setting up your own key mappings, perhaps using the Win and/or menu keys: key <LWIN> key <RWIN> key <MENU> - the one between AltGr and Ctrl.
Assuming you're using a US keyboard layout, set this up in Control Center:
Layout: English (US) Keyboard model: Generic 101-key PC Layout variant: basic
and you should see: Command: setxkbmap -model pc101 -layout us -variant basic
I haven't got RWIN key on my keyboard, so I've just tried LWIN and MENU keys.
In the first section [xkb_symbols "basic"] of the /etc/X11/xkb/symbols/us file, add
key <LWIN> { [ dead_acute, dead_grave ] }; key <MENU> { [ dead_diaeresis, dead_circumflex ] };
Then we get:
é [e acute] is LWIN then e è [e grave] is shift+LWIN then e ü [u umlaut] is MENU then u û [u circumflex] is shift+MENU then u Û [U circumflex] is shift+MENU then shift+u
Tested and works in konsole, kate, and LibreOffice.
If you need more accents, then add RWIN, or add AltGr to LWIN and MENU keys:
key <LWIN> { [ dead_acute, dead_grave, dead_**5**, dead_**6** ] }; key <MENU> { [ dead_diaeresis, dead_circumflex, dead_**7**, dead_**8** ] };
----- Reply to message ----- Subject: Re: [opensuse-kde3] Missing writing accents Date: 7 July 2018 at 07:15:29 From: Gianluca Interlandi <gianluca@u.washington.edu> I would appreciate any advice.
Thanks,
Gianluca
----------------------------------------------------- Gianluca Interlandi, PhD gianluca@u.washington.edu +1 (206) 685 4435 http://artemide.bioeng.washington.edu/ Research Assistant Professor at the Department of Bioengineering at the University of Washington, Seattle WA U.S.A. -----------------------------------------------------
Maybe try this - I use KDE3, but not in SuSE, and this works for me. Open up Keyboard Layout in Control Center and enable xkb options. Scroll about a quarter of the way down and under 'Compose Key Position' select the key you want to use - let's say 'Menu' [between AltGr and right Ctrl]. I don't need 'key Position of Compose Key' checked. Then é is Menu then e then ' [Menu then ' then e also works] Works in konsole, kate, and LibreOffice. And you might find this interesting reading https://forums.opensuse.org/showthread.php/501364-How-to-type-special-charac...
.. snip .. It fails only with KDE3 applications like konsole or kate.
-- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
Hi Ray, Thanks for the suggestion. I tried out different options in kcontrol, but none enables Compose in KDE3 applications. I wonder what causes it to be ignored and why only in KDE3 applications that are launched locally. Just a curiosity, what linux distribution are you running KDE3 on? Gianluca On Wed, 11 Jul 2018, Ray Vine wrote:
Maybe try this - I use KDE3, but not in SuSE, and this works for me.
Open up Keyboard Layout in Control Center and enable xkb options. Scroll about a quarter of the way down and under 'Compose Key Position' select the key you want to use - let's say 'Menu' [between AltGr and right Ctrl]. I don't need 'key Position of Compose Key' checked.
Then é is Menu then e then ' [Menu then ' then e also works]
Works in konsole, kate, and LibreOffice.
And you might find this interesting reading https://forums.opensuse.org/showthread.php/501364-How-to-type-special-charac...
.. snip .. It fails only with KDE3 applications like konsole or kate.
-- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
----------------------------------------------------- Gianluca Interlandi, PhD gianluca@u.washington.edu +1 (206) 685 4435 http://artemide.bioeng.washington.edu/ Research Assistant Professor at the Department of Bioengineering at the University of Washington, Seattle WA U.S.A. -----------------------------------------------------
Thanks for the suggestion. I tried out different options in kcontrol, but none enables Compose in KDE3 applications. I wonder what causes it to be ignored and why only in KDE3 applications that are launched locally.
I feel that the last option should work as it's set up from the Control Center. For a start, it's probably worth checking that the KDE configuration file is being updated. The change I suggested using the Menu key as the compose key changes: ~/.kde/share/config/kxkbrc from: [Layout] DisplayNames=, LayoutList=gb,us LayoutLoopCount=-1 Model=pc101 ResetOldOptions=false ShowFlag=true ShowLabel=false ShowLayoutIndicator=true ShowSingle=false SwitchMode=Global Use=true to: [Layout] DisplayNames= EnableXkbOptions=true IncludeGroups= LayoutList=gb,us LayoutLoopCount=-1 Model=pc101 Options=compose:menu ResetOldOptions=false ShowFlag=true ShowLabel=false ShowLayoutIndicator=true ShowSingle=false StickySwitching=false StickySwitchingDepth=2 SwitchMode=Global Use=true It also adds a +compose(menu) entry in the binary file /tmp/kde-root/gb..xkm: From: pc+gb+inet(evdev)+terminate(ctrl_alt_bksp) English (UK) To: pc+gb+inet(evdev)+compose(menu)+terminate(ctrl_alt_bksp) English (UK) Do you see similar changes? And I'm guessing that the compose:menu option refers to the 'xkb_symbols "menu"' entry in the /etc/X11/xkb/symbols/compose file, which should enable the Multi_key function for the Menu key. Do you have that file and entry?
Just a curiosity, what linux distribution are you running KDE3 on?
Slackware. It's an old build, but it still works. I joined this list when I found out that KDE3 was being updated for SuSE to find out what was being done. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
The file ~/.kde/share/config/kxkbrc does in fact get updated. For example, if I activate in kcontrol Xkb Options and select "rwin" for the Compose to, it changes from: [Layout] DisplayNames= EnableXkbOptions=true IncludeGroups= LayoutList=us Model=pc104 Options= ResetOldOptions=false ShowFlag=true ShowSingle=false StickySwitching=false StickySwitchingDepth=2 SwitchMode=Global Use=false to: [Layout] DisplayNames= EnableXkbOptions=true IncludeGroups= LayoutList=us Model=pc104 Options=compose:rwin ResetOldOptions=false ShowFlag=true ShowSingle=false StickySwitching=false StickySwitchingDepth=2 SwitchMode=Global Use=false However, it has no effect at all. On the other hand, if I type on the command line `setxkbmap -option compose=rwin`, then Compose still does not work in KDE3 applications, but if I open a xterm window, then I can use the right windows key as compose (in addition to "Shift+Ctrl"). Somehow, KDE3 in opensuse 13.x ignores any settings for Compose in KDE3 applications. I don't have the files /tmp/kde-root/gb..xkm or /etc/X11/xkb/symbols/compose in any of my opensuse systems. I have KDE3 running on opensuse 11.3 and there everything works as expected. However, staying with 11.3 is not an option in the long run because for example I can no longer upgrade firefox beyond version 45. Do you have any suggestion for a browser that works on older systems? Thanks, Gianluca On Thu, 12 Jul 2018, Ray Vine wrote:
Thanks for the suggestion. I tried out different options in kcontrol, but none enables Compose in KDE3 applications. I wonder what causes it to be ignored and why only in KDE3 applications that are launched locally.
I feel that the last option should work as it's set up from the Control Center. For a start, it's probably worth checking that the KDE configuration file is being updated.
The change I suggested using the Menu key as the compose key changes:
~/.kde/share/config/kxkbrc
from: [Layout] DisplayNames=, LayoutList=gb,us LayoutLoopCount=-1 Model=pc101 ResetOldOptions=false ShowFlag=true ShowLabel=false ShowLayoutIndicator=true ShowSingle=false SwitchMode=Global Use=true
to: [Layout] DisplayNames= EnableXkbOptions=true IncludeGroups= LayoutList=gb,us LayoutLoopCount=-1 Model=pc101 Options=compose:menu ResetOldOptions=false ShowFlag=true ShowLabel=false ShowLayoutIndicator=true ShowSingle=false StickySwitching=false StickySwitchingDepth=2 SwitchMode=Global Use=true
It also adds a +compose(menu) entry in the binary file /tmp/kde-root/gb..xkm: From: pc+gb+inet(evdev)+terminate(ctrl_alt_bksp) English (UK) To: pc+gb+inet(evdev)+compose(menu)+terminate(ctrl_alt_bksp) English (UK)
Do you see similar changes?
And I'm guessing that the compose:menu option refers to the 'xkb_symbols "menu"' entry in the /etc/X11/xkb/symbols/compose file, which should enable the Multi_key function for the Menu key.
Do you have that file and entry?
Just a curiosity, what linux distribution are you running KDE3 on?
Slackware. It's an old build, but it still works. I joined this list when I found out that KDE3 was being updated for SuSE to find out what was being done.
-- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
----------------------------------------------------- Gianluca Interlandi, PhD gianluca@u.washington.edu +1 (206) 685 4435 http://artemide.bioeng.washington.edu/ Research Assistant Professor at the Department of Bioengineering at the University of Washington, Seattle WA U.S.A. ----------------------------------------------------- -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
'setxkbmap -option compose=rwin' - was that a typo, it doesn't work for me? You must have used 'setxkbmap -option compose:rwin' for RWIN to work as the compose key in an xterm. Using that bypasses the KDE configuration files, and enables 'rwin' as the compose key, and works for me in konsole, kate, and LibreOffice as well as xterm. So it does look like a problem in 13.x/KDE3. It would be useful here to get some feedback from another list member on whether 'setxkbmap -option compose:rwin' sets RWIN as the compose key for them in 13.x, or any later version.
I don't have the files /tmp/kde-root/gb..xkm or /etc/X11/xkb/symbols/compose in any of my opensuse systems.
That would be /tmp/kde-xxx/us..xkm for you: pc+us+inet(evdev)+compose(rwin)+terminate(ctrl_alt_bksp)........English (US) and /usr/share/X11/xkb/symbols/compose ?
I can no longer upgrade firefox beyond version 45
If this is because 11.3 doesn't include gtk3, would gtk3 and it's dependencies from 11.4 be compatible? Start with libgtk-3-0-3.0.0 .... for example from http://ftp5.gwdg.de/pub/opensuse/discontinued/distribution/11.4/repo/oss/sus... You should then be able to run the current Firefox. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
Hi Ray, Yes, that was a typo, sorry. I did mean 'setxkbmap -option compose:rwin'. I agree, it is a problem with 13.x/KDE3. Not sure whether it was fixed in Leap and later versions. The interesting thing is that if I type ssh localhost konsole & then Compose works in the new konsole. It seems to have to do with the session and maybe how DCOP handles signals? I don't know enough about the inner workings of KDE3. Thanks for the tip about installing GTK3. I had thought about it a while ago. I will try it. GTK3 will solve one problem. Another problem is the old glibc. But I will first try installing GTK3. Best, Gianluca On Thu, 12 Jul 2018, Ray Vine wrote:
'setxkbmap -option compose=rwin' - was that a typo, it doesn't work for me? You must have used 'setxkbmap -option compose:rwin' for RWIN to work as the compose key in an xterm. Using that bypasses the KDE configuration files, and enables 'rwin' as the compose key, and works for me in konsole, kate, and LibreOffice as well as xterm. So it does look like a problem in 13.x/KDE3.
It would be useful here to get some feedback from another list member on whether 'setxkbmap -option compose:rwin' sets RWIN as the compose key for them in 13.x, or any later version.
I don't have the files /tmp/kde-root/gb..xkm or /etc/X11/xkb/symbols/compose in any of my opensuse systems.
That would be /tmp/kde-xxx/us..xkm for you: pc+us+inet(evdev)+compose(rwin)+terminate(ctrl_alt_bksp)........English (US)
and /usr/share/X11/xkb/symbols/compose ?
I can no longer upgrade firefox beyond version 45
If this is because 11.3 doesn't include gtk3, would gtk3 and it's dependencies from 11.4 be compatible? Start with libgtk-3-0-3.0.0 .... for example from http://ftp5.gwdg.de/pub/opensuse/discontinued/distribution/11.4/repo/oss/sus...
You should then be able to run the current Firefox.
-- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
----------------------------------------------------- Gianluca Interlandi, PhD gianluca@u.washington.edu +1 (206) 685 4435 http://artemide.bioeng.washington.edu/ Research Assistant Professor at the Department of Bioengineering at the University of Washington, Seattle WA U.S.A. ----------------------------------------------------- -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
Start with libgtk-3-0-3.0.0 .... I will first try installing GTK3.
Sorry, for Firefox 61.0 that version of libgtk gives an error: 'libxul.so: undefined symbol: gdk_screen_get_monitor_workarea' which afaik means that gtk3.22 minimum is required. The closest I found is libgtk-3-0-3.4.4-2.8.2.x86_64.rpm from 12.2 Surprisingly that's the only library I needed to add for Firefox to then run. As you've indicated, you'll probably need to update others. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
Hi Ray, What kernel are you running in your Slackware distribution and what is the glic version? Why do you say that gtk3.22 minimum is required? It seems that 3.4.4 from 12.2 works. Thanks, Gianluca On Thu, 12 Jul 2018, Ray Vine wrote:
Start with libgtk-3-0-3.0.0 .... I will first try installing GTK3.
Sorry, for Firefox 61.0 that version of libgtk gives an error: 'libxul.so: undefined symbol: gdk_screen_get_monitor_workarea' which afaik means that gtk3.22 minimum is required.
The closest I found is libgtk-3-0-3.4.4-2.8.2.x86_64.rpm from 12.2
Surprisingly that's the only library I needed to add for Firefox to then run. As you've indicated, you'll probably need to update others.
----------------------------------------------------- Gianluca Interlandi, PhD gianluca@u.washington.edu +1 (206) 685 4435 http://artemide.bioeng.washington.edu/ Research Assistant Professor at the Department of Bioengineering at the University of Washington, Seattle WA U.S.A. ----------------------------------------------------- -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
What kernel are you running in your Slackware distribution and what is the glic version?
4.4.133 and glibc-2.27
Why do you say that gtk3.22 minimum is required? It seems that 3.4.4 from 12.2 works.
My mistake. In my rush to stop you wasting your time with the earlier version, I misread some information on the error. Should read gtk+-3.3.6 at least required. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
Thanks Ray. I think that according to the firefox website you need at least gtk+-3.4 starting with version 46: https://www.mozilla.org/en-US/firefox/46.0.1/system-requirements/ I think we went off-topic within the general framework of how to maintain so called legacy software. It's good to hear alternative options, though. Gianluca On Fri, 13 Jul 2018, Ray Vine wrote:
What kernel are you running in your Slackware distribution and what is the glic version?
4.4.133 and glibc-2.27
Why do you say that gtk3.22 minimum is required? It seems that 3.4.4 from 12.2 works.
My mistake. In my rush to stop you wasting your time with the earlier version, I misread some information on the error. Should read gtk+-3.3.6 at least required.
-- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
----------------------------------------------------- Gianluca Interlandi, PhD gianluca@u.washington.edu +1 (206) 685 4435 http://artemide.bioeng.washington.edu/ Research Assistant Professor at the Department of Bioengineering at the University of Washington, Seattle WA U.S.A. ----------------------------------------------------- -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
Sorry for continuing on this "off topic" branch. I wonder whether it is easy to compile chromium with gtk2. I see that this was done for ArchLinux: https://aur.archlinux.org/packages/chromium-gtk2/ But I can't find any specific information. I will try downloading the git repository from the archlinux website. I have never used git before. I tried running the latest version of firefox 61 on my old 11.3 installation after copying all /lib64 and /usr/lib64 libraries from a 12.3 installation, but gtk-3.4 requires glibc-2.14. Gianluca On Fri, 13 Jul 2018, Ray Vine wrote:
What kernel are you running in your Slackware distribution and what is the glic version?
4.4.133 and glibc-2.27
Why do you say that gtk3.22 minimum is required? It seems that 3.4.4 from 12.2 works.
My mistake. In my rush to stop you wasting your time with the earlier version, I misread some information on the error. Should read gtk+-3.3.6 at least required.
-- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
----------------------------------------------------- Gianluca Interlandi, PhD gianluca@u.washington.edu +1 (206) 685 4435 http://artemide.bioeng.washington.edu/ Research Assistant Professor at the Department of Bioengineering at the University of Washington, Seattle WA U.S.A. ----------------------------------------------------- -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
Sorry for continuing on this "off topic" branch.
Better to start a new thread? But even then it may not be considered relevant to KDE3.
I wonder whether it is easy to compile chromium ..
In my experience, no. I used to do it, but it required installing and updating its own toolchain, and frequently each new version introduced new build errors and I got tired of chasing them down. I build my own version of Firefox, which has worked out OK till now, building version 52esr with gtk2, but it's eol in August. Gtk2 is no longer supported so I'll have to revise my build for 60esr with gtk3. I use the esr versions because I don't want all the bells and whistles that Mozilla keep introducing, but all the security patches are included. Why do you want to do a gtk2 build?
.. after copying all /lib64 and /usr/lib64 libraries from a 12.3 installation, but gtk-3.4 requires glibc-2.14
Why gtk-3.4/glibc-2.14? 12.3 has: libgtk-3-0-3.6.4-2.1.1.x86_64.rpm glibc-2.17-4.4.1.x86_64.rpm Why didn't you install gtk3 and install/update its deps from the rpms? Just curious though, why you're not upgrading to 15.0. → -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
Hi Ray,
I build my own version of Firefox, which has worked out OK till now, building version 52esr with gtk2, but it's eol in August.
Could you please make your build of Firefox 52esr with gtk2 available? It would be great!
Why gtk-3.4/glibc-2.14? 12.3 has: libgtk-3-0-3.6.4-2.1.1.x86_64.rpm glibc-2.17-4.4.1.x86_64.rpm
You are correct. I must have mistyped something.
Just curious though, why you're not upgrading to 15.0.
I have an old 11.3 installation with lots of stuff running. I am slowly migrating everything to a newer system. Just in the mean time, I needed a browser that works with openSUSE 11.3, i.e., with gtk2 and glibc-2.11. Thanks, Gianluca ----------------------------------------------------- Gianluca Interlandi, PhD gianluca@u.washington.edu +1 (206) 685 4435 http://artemide.bioeng.washington.edu/ Research Assistant Professor at the Department of Bioengineering at the University of Washington, Seattle WA U.S.A. ----------------------------------------------------- -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
That's one person's point of view. My view is that it's not that far off topic in that it derived from the original question. I've lost count of the number of times I've read a thread where some 'off topic' snippet has led me to an understanding of some long standing issue or an alternative solution - as here. The op wanted a particular question answered, but it looks like no-one here can provide an answer and an alternative may be acceptable. How is that a bad result? How do other list members feel about it? ----- Reply to message ----- Subject: Re: [opensuse-kde3] Missing writing accents Date: 12 July 2018 at 21:12:31 From: Kyrill Detinov <lazy.kent@opensuse.org> To: <opensuse-kde3@opensuse.org>
On Thu, 12 Jul 2018 20:35:45 +0100 Ray Vine wrote:
Sorry, for Firefox 61.0 that version of libgtk gives an error:
Can we follow the thread, please?
Missing writing accents
-- WBR Kyrill
-- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
I agree. I have also often learned from 'off topic' snippets from other mailing lists that had a lot more traffic. Gianluca On Thu, 12 Jul 2018, Ray Vine wrote:
That's one person's point of view.
My view is that it's not that far off topic in that it derived from the original question. I've lost count of the number of times I've read a thread where some 'off topic' snippet has led me to an understanding of some long standing issue or an alternative solution - as here.
The op wanted a particular question answered, but it looks like no-one here can provide an answer and an alternative may be acceptable. How is that a bad result?
How do other list members feel about it?
----- Reply to message ----- Subject: Re: [opensuse-kde3] Missing writing accents Date: 12 July 2018 at 21:12:31 From: Kyrill Detinov <lazy.kent@opensuse.org> To: <opensuse-kde3@opensuse.org>
On Thu, 12 Jul 2018 20:35:45 +0100 Ray Vine wrote:
Sorry, for Firefox 61.0 that version of libgtk gives an error:
Can we follow the thread, please?
Missing writing accents
-- WBR Kyrill
-- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
----------------------------------------------------- Gianluca Interlandi, PhD gianluca@u.washington.edu +1 (206) 685 4435 http://artemide.bioeng.washington.edu/ Research Assistant Professor at the Department of Bioengineering at the University of Washington, Seattle WA U.S.A. ----------------------------------------------------- -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
It looks as though SuSE 13.2 defaults to input method 'ibus' where kde3/qt3 needs 'xim'. Add 'export QT_IM_MODULE=xim' to your profile. I set this up in a live CD and using 'menu' as the single compose key: menu a ' produces á in konsole and kate. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
Hi Ray! Thank you sooo much! It works. I use tcsh, so I set in my .tcshrc setenv QT_IM_MODULE xim However, I wonder where the best place is to define it. Is it best to put it in the .login file or globally in /etc/csh.{cshrc,login}.local and /etc/{bash.bashrc,profile}.local for bash? Thanks, Gianluca On Mon, 16 Jul 2018, Ray Vine wrote:
It looks as though SuSE 13.2 defaults to input method 'ibus' where kde3/qt3 needs 'xim'.
Add 'export QT_IM_MODULE=xim' to your profile.
I set this up in a live CD and using 'menu' as the single compose key:
menu a ' produces á in konsole and kate.
----------------------------------------------------- Gianluca Interlandi, PhD gianluca@u.washington.edu +1 (206) 685 4435 http://artemide.bioeng.washington.edu/ Research Assistant Professor at the Department of Bioengineering at the University of Washington, Seattle WA U.S.A. -----------------------------------------------------
On 07/16/2018 05:42 PM, Gianluca Interlandi wrote:
Hi Ray!
Thank you sooo much! It works. I use tcsh, so I set in my .tcshrc
setenv QT_IM_MODULE xim
However, I wonder where the best place is to define it. Is it best to put it in the .login file or globally in /etc/csh.{cshrc,login}.local and /etc/{bash.bashrc,profile}.local for bash?
Thanks,
Gianluca
Gianluca, Glad you got it working! Ray -- thank you for your help. Other than a recollection about the issue, I had never stumbled far enough into the issue to be able to find a solution. Now if we can just use that same enthusiasm to get the KDE3 repo building on 15.0 and supported --- we would all be in good shape. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
I decided to set it globally for both tcsh and bash. I edited the files /etc/csh.login.local: if ($?QT_IM_MODULE) then setenv QT_IM_MODULE xim endif and /etc/profile.local: if test -n "$QT_IM_MODULE" ; then QT_IM_MODULE=xim export QT_IM_MODULE fi Gianluca On Tue, 17 Jul 2018, David C. Rankin wrote:
On 07/16/2018 05:42 PM, Gianluca Interlandi wrote:
Hi Ray!
Thank you sooo much! It works. I use tcsh, so I set in my .tcshrc
setenv QT_IM_MODULE xim
However, I wonder where the best place is to define it. Is it best to put it in the .login file or globally in /etc/csh.{cshrc,login}.local and /etc/{bash.bashrc,profile}.local for bash?
Thanks,
Gianluca
Gianluca,
Glad you got it working! Ray -- thank you for your help. Other than a recollection about the issue, I had never stumbled far enough into the issue to be able to find a solution.
Now if we can just use that same enthusiasm to get the KDE3 repo building on 15.0 and supported --- we would all be in good shape.
-- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org
----------------------------------------------------- Gianluca Interlandi, PhD gianluca@u.washington.edu +1 (206) 685 4435 http://artemide.bioeng.washington.edu/ Research Assistant Professor at the Department of Bioengineering at the University of Washington, Seattle WA U.S.A. -----------------------------------------------------
participants (4)
-
David C. Rankin -
Gianluca Interlandi -
Kyrill Detinov -
Ray Vine