Thread View: gnu.epoch.misc
3 messages
3 total messages
Started by Jim.Rees
Fri, 07 May 1993 17:40
How to get a 'compose' key?
Author: Jim.Rees
Date: Fri, 07 May 1993 17:40
Date: Fri, 07 May 1993 17:40
8 lines
998 bytes
998 bytes
How can I get a compose key for entering international characters? The faq tells how to get 8-bit input from an 8-bit keyboard, but that doesn't help if you don't have an 8-bit keyboard. I can sort of see how to do it, but I wonder if anyone else has already gone to the trouble. I think the answer is to set up a bunch of bindings, so that, for example, if I use F5 for 'compose,' then F5-a-^ would be bound to (insert �).
Re: How to get a 'compose' key?
Author: Stephan Oepen
Date: Fri, 07 May 1993 21:17
Date: Fri, 07 May 1993 21:17
29 lines
2279 bytes
2279 bytes
> How can I get a compose key for entering international characters?
> I can sort of see how to do it, but I wonder if anyone else has
> already gone to the trouble. I think the answer is to set up a bunch
> of bindings, so that, for example, if I use F5 for 'compose,' then
> F5-a-^ would be bound to (insert �).
no need to do the compose key binding yourself in Epoch (as opposed to
lemacs that comes without knowledge of multi key sequences |:-{). if
your terminal does not provide you with a compose key you can use
xmodmap(1) to have some other key behave as compose; e.g. what i do on
my ncd X terminal is the following (from my `.Xmodmap' file)
keysym Control_R = Multi_key
thus mapping the key labelled `Alt Graph' on the right side of my
keyboard to `Multi_key'. xev(1) is useful in determining the keysym of
keys you want to rebind with xmodmap(1).
after this (global) rebinding your X server and the Epoch 8 bit input
model will take care of the rest (and bash 1.13 and other 8 bit clean
programs will eventually benefit from it as well |:-). make sure you
have fonts with iso 8859/1 encoding available.
cu - oe
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;; Stephan Oepen, Duerkheimer Str. 7, 66oo Saarbruecken, (o681) - 3o2 52 84
;;; - oe@dfki.uni-sb.de | oe@cs.tu-berlin.de | oe@gnu.ai.mit.edu -
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
Re: How to get a 'compose' key?
Author: Jamie Zawinski
Date: Sat, 08 May 1993 01:17
Date: Sat, 08 May 1993 01:17
23 lines
1838 bytes
1838 bytes
In gnu.epoch.misc Stephan Oepen <oe@disco-sol.dfki.uni-sb.de> wrote: > > if your terminal does not provide you with a compose key you can use > xmodmap(1) to have some other key behave as compose; e.g. what i do > on my ncd X terminal is the following (from my `.Xmodmap' file) > > keysym Control_R = Multi_key ... > after this (global) rebinding your X server and the Epoch 8 bit input > model will take care of the rest (and bash 1.13 and other 8 bit clean > programs will eventually benefit from it as well |:-). Unfortunately, it's not a property of the X server, it's a property of the version of libX11.a that you link with; so in your case, it depends on the machine that application in question was compiled / is being run on, not the fact that you have an NCD server. The OpenWindows Xlib, and those from DEC and HP (I think), and probably others, understand the Multi_key, so all you need to do for them is add that keysym to your keyboard, but the MIT R4 and R5 Xlibs do not. (But there's a patch for this on export.) -- Jamie
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads