Doc fixes

Add keymaps supplied in issues

Closes https://github.com/kernc/logkeys/issues/121
closes https://github.com/kernc/logkeys/issues/123
closes https://github.com/kernc/logkeys/issues/119
closes https://github.com/kernc/logkeys/issues/88

Per https://github.com/kernc/logkeys/issues/88, the existing
-u option didn't map correctly on Ubuntu 12.04.

source: https://github.com/kernc/logkeys/issues/119

source: https://github.com/kernc/logkeys/issues/121

source: https://github.com/kernc/logkeys/issues/123

Cleanup build

- not tracking autotools-generated files; people building
  from source should have autotools installed already
- added autogen.sh
- updated build notes

Documentation updates

- converted README to GitHub markup
- imported googlecode wiki pages into docs folder
- added build directory for out-of-tree builds
- updated TODOs

Ignore artifacts generated during configure.

Recognize Logitech

Closes #136, closes #134, closes #129, closes #120, closes #126, closes #90, closes #105, closes #116

Device name 'Eee PC WMI hotkeys' has EV=100013.  Tweaked regex to handle.

The usual keyboard event bitmask is 120013, but Logitech and some
other keyboards have 12001F.  Using both F and f as grep case-insensitivity
flag may vary across systems.

Code is clearer if the definition is placed where needed.

Added directory with all 19 existing keymap files.

git-svn-id: https://logkeys.googlecode.com/svn/trunk@102 c501e62c-e7d1-11de-a198-37193048d1ed

git-svn-id: https://logkeys.googlecode.com/svn/trunk@94 c501e62c-e7d1-11de-a198-37193048d1ed

git-svn-id: https://logkeys.googlecode.com/svn/trunk@93 c501e62c-e7d1-11de-a198-37193048d1ed

Hopefully fixes issue http://code.google.com/p/logkeys/issues/detail?id=42 (Couldn't determine keyboard device). We have a new heuristic! :D

git-svn-id: https://logkeys.googlecode.com/svn/trunk@92 c501e62c-e7d1-11de-a198-37193048d1ed

git-svn-id: https://logkeys.googlecode.com/svn/trunk@91 c501e62c-e7d1-11de-a198-37193048d1ed

git-svn-id: https://logkeys.googlecode.com/svn/trunk@77 c501e62c-e7d1-11de-a198-37193048d1ed

git-svn-id: https://logkeys.googlecode.com/svn/trunk@74 c501e62c-e7d1-11de-a198-37193048d1ed

git-svn-id: https://logkeys.googlecode.com/svn/trunk@73 c501e62c-e7d1-11de-a198-37193048d1ed

git-svn-id: https://logkeys.googlecode.com/svn/trunk@72 c501e62c-e7d1-11de-a198-37193048d1ed

git-svn-id: https://logkeys.googlecode.com/svn/trunk@71 c501e62c-e7d1-11de-a198-37193048d1ed

there was a serious "condition" error in set_utf8_locale(), which prevented "finding" UTF-8 even when it's there, now fixed

git-svn-id: https://logkeys.googlecode.com/svn/trunk@68 c501e62c-e7d1-11de-a198-37193048d1ed

updated args.cc so there are no 0bXXXX binary constants defined (replaced with hexadecimal 0xXXXX), because they seem to cause errors on older g++

git-svn-id: https://logkeys.googlecode.com/svn/trunk@67 c501e62c-e7d1-11de-a198-37193048d1ed

git-svn-id: https://logkeys.googlecode.com/svn/trunk@53 c501e62c-e7d1-11de-a198-37193048d1ed

git-svn-id: https://logkeys.googlecode.com/svn/trunk@49 c501e62c-e7d1-11de-a198-37193048d1ed

git-svn-id: https://logkeys.googlecode.com/svn/trunk@47 c501e62c-e7d1-11de-a198-37193048d1ed

git-svn-id: https://logkeys.googlecode.com/svn/trunk@46 c501e62c-e7d1-11de-a198-37193048d1ed

git-svn-id: https://logkeys.googlecode.com/svn/trunk@45 c501e62c-e7d1-11de-a198-37193048d1ed