herrage@ntpal.UUCP (Robert Herrage) (08/27/90)
I have some .bdf versions of some fonts that will display the "meta" key character whenever I run my application in X11R4 and twm from MIT. However, when I run "convertfont" on them, run "bldfamily", and then "xset" to include the font path, the "meta" key character doesn't show up when I run my application in OW 2.0. Any suggestions? Thanks, Robert
janssen@parc.xerox.com (Bill Janssen) (08/30/90)
In article <506@ntpal.UUCP> herrage@ntpal.UUCP (Robert Herrage) writes:
I have some .bdf versions of some fonts that will display the "meta"
key character whenever I run my application in X11R4 and twm from MIT.
However, when I run "convertfont" on them, run "bldfamily", and then
"xset" to include the font path, the "meta" key character doesn't show
up when I run my application in OW 2.0.
I have almost no idea of what you're really asking. What is "the" meta
key character? How does a "font" display a "character"?
However, on the off chance that you're having the same problem with
OW that we had: In OW 2.0, the Meta_L and Meta_R keysyms are not bound
to the Mod1 modifier, so they do not work as "meta" keys for applications
that look for the Mod1 modifier bit to be set. X11R4 seems to have this
binding as a default. To fix this for OpenWindows, put the following
lines in your .xmodmaprc, and execute xmodmap.
add Mod1 = Meta_L
add Mod1 = Meta_R
--
Bill Janssen janssen@parc.xerox.com (415) 494-4763
Xerox Palo Alto Research Center
3333 Coyote Hill Road, Palo Alto, California 94304