"" is "greater"; "|" is "bar".
Instead of messing with xkb you can use xmodmap. You first need to dump the
current mapping of the keys into ~/.Xmodmap:
$ xmodmap -pke > ~/.Xmodmap
Then you must modify this file. In the first column, you have the key code
(bound to a physical key) and then, after the equal sign, what character
represents (first when the key is pressed without any modifier, then when
Shift is pressed at the time, etc.).
You can use the 'xev' command to discover what key code is bound to a
particular key. For a clearer out, we can filter the lines with "keycode":
$ xev | grep keycode
When the command is running, just press the key to discover its code.
With GNOME, I then had to explicitly add 'xmodmap ~/.Xmodmap' to the "Startup
applications". I believe you will not have this trouble with awesome.
