diff --git a/INSTALL b/INSTALL
index d7bf93d..a1362ff 100644
--- a/INSTALL
+++ b/INSTALL
@@ -2,21 +2,21 @@
logkeys keylogger - instalation instructions
===============================================================================
-Provided your GNU/Linux distribution doesn't include logkeys package in its
-repositories, manual installation of logkeys from source is as easy as:
+Provided your GNU/Linux distribution doesn't include logkeys package
+in its repositories, manual installation of logkeys from source is as
+easy as cloning this repo or [downloading a zip of the
+source](https://github.com/kernc/logkeys/archive/master.zip),
+unzipping, and building:
- $ tar xvzf logkeys-0.1.1.tar.gz # to extract the logkeys archive
-
- $ cd logkeys-0.1.1/build # move to build directory to build there
- $ ../configure # invoke configure from parent directory
- $ make # make compiles what it needs to compile
- ( become superuser now ) # you need root to install in system dir
- # make install # installs binaries, manuals and scripts
+ $ unzip logkeys-master.zip
+ $ cd logkeys-master/build
+ $ ../configure
+ $ make
+ $ su # get root to install in system
+ $ make install # installs binaries, manuals and scripts
-That's it.
+To uninstall logkeys, remove accompanying scripts and manuals:
-To ever uninstall logkeys, remove accompanying scripts and manuals, issue
-
- # make uninstall # in the same logkeys-0.1.1/build dir from before
+ # make uninstall # in the same src dir
See README file for usage instructions, troubleshooting and other notes.
diff --git a/README b/README
deleted file mode 100644
index 7278859..0000000
--- a/README
+++ /dev/null
@@ -1,198 +0,0 @@
-===============================================================================
- logkeys - a GNU/Linux keylogger that works!
-===============================================================================
-
- 0. Licence
- 1. Description
- 2. Installation
- 3. Usage how-to
- 4. Troubleshooting
- 5. Further information
-
-===============================================================================
-
-
-+------------------------------------------------
- 0. Licence
-===============================================================================
-logkeys is dual licensed under the terms of either GNU GPLv3 or later, or
-WTFPLv2 or later. It is entirely your choice! See COPYING for further
-information about licensing.
-
-
-+------------------------------------------------
- 1. Description
-===============================================================================
-logkeys is a linux keylogger. It is no more advanced than other available linux
-keyloggers, notably lkl and uberkey, but is a bit newer, more up to date, it
-doesn't unreliably repeat keys and it shouldn't crash your X. All in all, it
-just seems to work. It relies on event interface of the Linux input subsystem.
-Once completely set, it logs all common character and function keys, while also
-being fully aware of Shift and AltGr key modifiers.
-
-
-+------------------------------------------------
- 2. Installation
-===============================================================================
-Provided your GNU/Linux distribution doesn't include logkeys package in its
-repositories, manual installation of logkeys from source is as easy as:
-
- $ tar xvzf logkeys-0.1.1.tar.gz # to extract the logkeys archive
-
- $ cd logkeys-0.1.1/build # move to build directory to build there
- $ ../configure # invoke configure from parent directory
- $ make # make compiles what it needs to compile
- ( become super↙user now ) # you need root to install in system dir
- # make install # installs binaries, manuals and scripts
-
-That's it.
-
-To ever uninstall logkeys, remove accompanying scripts and manuals, issue
-
- # make uninstall # in the same logkeys-0.1.1/build dir from before
-
-A copy of these instructions is in the accompanying INSTALL file.
-
-
-+------------------------------------------------
- 3. Usage how-to
-===============================================================================
-
-logkeys is simple. You can either invoke it directly, by typing full command
-line, or use the provided scripts. There are two helper programs in this
-package:
-
- bin/llk , which is intended to start the logkeys daemon, and
- bin/llkk , which is intended to kill it.
-
-bin/llk runs etc/logkeys-start.sh, and bin/llkk runs etc/logkeys-kill.sh.
-
-You can use these two setuid root programs (llk and llkk) for starting and
-stopping the keylogger quickly and covertly. You can modify the .sh scripts as
-you like. As the two programs are installed with setuid bit set, the root
-password need not be provided at their runtime.
-
-Default log file is /var/log/logkeys.log and is not readable by others.
-
-I suggest you first test the program manually with
-
- $ touch test.log
- $ logkeys --start --output test.log
-
-and in the other terminal follow it with
-
- $ tail --follow test.log
-
-and see if the pressed keys match to those noted. If you use a US keyboard
-layout, use -u switch. Make sure your terminal character locale is set to UTF-8
-
- $ locale
- LANG=xx_YY.UTF-8
- LC_CTYPE="xx_YY.UTF-8"
- ...
-
-or alternatively, you need en_US.UTF-8 locale available on your system
-
- $ locale -a
- ...
- en_US.UTF-8
- ...
-
-otherwise you may only see odd characters (like ꑶ etc.) when pressing character
-keys.
-
-logkeys acts as a daemon, and you stop the running logger process with
-
- $ logkeys --kill
-
-(or bin/llkk provided script).
-
-For more information about logkeys log file format, logkeys keymap format, and
-command line arguments, read the application manual,
-
- $ man logkeys
-
-or see the wiki at project website: http://code.google.com/p/logkeys/
-
-Abuse the output of this software wisely.
-
-
-+------------------------------------------------
- 4. Troubleshooting
-===============================================================================
-
-4.1 empty log file or 'Error opening input event device'
--------------------------------------------------
-After you run logkeys successfully, if you open the log file and see only the
-'Logging started...' and 'Logging stopped...' tag without any keypress
-"contents," it is very likely that logkeys got your device id wrong.
-
-This may also apply if you get the following error:
- Error opening input event device '/dev/input/event-1'
-
-The solution is to determine the correct event device id, and then run
-logkeys with --device (-d) switch, specifying that device manually.
-
-The procedure for manually learning the device id to use is as follows:
-
-As root, for each existing device eventX in /dev/input/, where X is a number
-between 0 and 31 inclusively, write:
-
- $ cat /dev/input/eventX
-
-then type some arbitrary characters. If you see any output, that is the device
-to be used. If you don't see any output, press Ctrl+C and continue with the
-next device.
-
-If this happened to be your issue, *please* submit a bug report, attaching
-your /proc/bus/input/devices file as well as and specifying which was the
-correct id.
-
-
-4.2 logkeys outputs wrong characters
--------------------------------------------------
-It is very likely that you will see only some characters recognized, without
-any hope for Shift and AltGr working even slightly correct, especially when
-starting logkeys in X. In that case it is better to switch to virtual
-terminal, e.g. tty4 (Ctrl+Alt+F4), and there execute:
-
- $ logkeys --export-keymap my_lang.keymap
-
-Then open my_lang.keymap in UTF-8 enabled text editor and manually repair any
-missing or incorrectly determined mappings. From then on, execute logkeys by
-
- $ logkeys --start --keymap my_lang.keymap
-
-Again, see if it now works correctly (character keys appear correct when you
-are viewing the log file in editor), and opt to modify bin/llk starter script.
-
-If you create full and completely valid keymap for your particular language,
-please upload it to website or send it to me by e-mail. Thanks.
-
-
-+------------------------------------------------
- 5. Further information
-===============================================================================
-
-Read the man page. Please read the whole man page. Thanks. :-)
-
-Refer to troubleshooting and FAQ sections on the project website,
-
- http://code.google.com/p/logkeys/ ,
-
-for currently known issues, ways to resolve them, and any other information.
-
-Report any bugs and request reasonable features on the issues list page
-
- http://code.google.com/p/logkeys/issues .
-
-When opening new issues, always provide descriptively keyworded summary and
-description.
-
-You are more than welcome to implement unreasonable features yourself, as well
-as hack the program to your liking.
-
-If you are a pr0, please answer the few questions I commented in the source.
-Thanks.
-
-~
diff --git a/README.md b/README.md
new file mode 100644
index 0000000..985c705
--- /dev/null
+++ b/README.md
@@ -0,0 +1,178 @@
+logkeys - a GNU/Linux keylogger
+===============================
+
+logkeys is a linux keylogger. It is no more advanced than other available linux
+keyloggers, notably lkl and uberkey, but is a bit newer, more up to date, it
+doesn't unreliably repeat keys and it shouldn't crash your X. All in all, it
+just seems to work. It relies on event interface of the Linux input subsystem.
+Once completely set, it logs all common character and function keys, while also
+being fully aware of Shift and AltGr key modifiers.
+
+
+Installation
+------------
+
+Provided your GNU/Linux distribution doesn't include logkeys package
+in its repositories, manual installation of logkeys from source is as
+easy as cloning this repo or [downloading a zip of the
+source](https://github.com/kernc/logkeys/archive/master.zip),
+unzipping, and building:
+
+ $ unzip logkeys-master.zip
+ $ cd logkeys-master/build
+ $ ../configure
+ $ make
+ $ su # get root to install in system
+ $ make install # installs binaries, manuals and scripts
+
+To uninstall logkeys, remove accompanying scripts and manuals:
+
+ $ make uninstall # in the same src dir
+
+A copy of these instructions is in the accompanying INSTALL file.
+
+
+Usage how-to
+------------
+
+Abuse the output of this software wisely.
+
+logkeys is simple. You can either invoke it directly, by typing full command
+line, or use the provided scripts. There are two helper programs in this
+package:
+
+- bin/llk, which is intended to start the logkeys daemon, and
+- bin/llkk, which is intended to kill it.
+
+bin/llk runs etc/logkeys-start.sh, and bin/llkk runs etc/logkeys-kill.sh.
+
+You can use these two setuid root programs (llk and llkk) for starting and
+stopping the keylogger quickly and covertly. You can modify the .sh scripts as
+you like. As the two programs are installed with setuid bit set, the root
+password need not be provided at their runtime.
+
+Default log file is `/var/log/logkeys.log` and is not readable by others.
+
+I suggest you first test the program manually with
+
+ $ touch test.log
+ $ logkeys --start --output test.log
+
+and in the other terminal follow it with
+
+ $ tail --follow test.log
+
+and see if the pressed keys match to those noted. If you use a US keyboard
+layout, use -u switch. Make sure your terminal character locale is set to UTF-8
+
+ $ locale
+ LANG=xx_YY.UTF-8
+ LC_CTYPE="xx_YY.UTF-8"
+ ...
+
+or alternatively, you need en_US.UTF-8 locale available on your system
+
+ $ locale -a
+ ...
+ en_US.UTF-8
+ ...
+
+otherwise you may only see odd characters (like ꑶ etc.) when pressing character
+keys.
+
+logkeys acts as a daemon, and you stop the running logger process with
+`$ logkeys --kill`, or use the `bin/llkk` script.
+
+Documentation
+-------------
+
+For more information about logkeys log file format, logkeys keymap
+format, and command line arguments, read the application manual, `$
+man logkeys`, or read [the documentation](./docs).
+
+Troubleshooting
+---------------
+
+### empty log file or 'Error opening input event device'
+
+After you run logkeys successfully, if you open the log file and see only the
+'Logging started...' and 'Logging stopped...' tag without any keypress
+"contents," it is very likely that logkeys got your device id wrong.
+
+This may also apply if you get the following error: `Error opening
+input event device '/dev/input/event-1'`
+
+The solution is to determine the correct event device id, and then run
+logkeys with --device (-d) switch, specifying that device manually.
+
+The procedure for manually learning the device id to use is as follows:
+
+As root, for each existing device eventX in /dev/input/, where X is a number
+between 0 and 31 inclusively, write:
+
+ $ cat /dev/input/eventX
+
+then type some arbitrary characters. If you see any output, that is the device
+to be used. If you don't see any output, press Ctrl+C and continue with the
+next device.
+
+If this happened to be your issue, *please* submit a bug report, attaching
+your `/proc/bus/input/devices` file as well as and specifying which was the
+correct id.
+
+
+### logkeys outputs wrong characters
+
+It is very likely that you will see only some characters recognized, without
+any hope for Shift and AltGr working even slightly correct, especially when
+starting logkeys in X. In that case it is better to switch to virtual
+terminal, e.g. tty4 (Ctrl+Alt+F4), and there execute:
+
+ $ logkeys --export-keymap my_lang.keymap
+
+Then open my_lang.keymap in UTF-8 enabled text editor and manually repair any
+missing or incorrectly determined mappings. From then on, execute logkeys by
+
+ $ logkeys --start --keymap my_lang.keymap
+
+Again, see if it now works correctly (character keys appear correct when you
+are viewing the log file in editor), and opt to modify bin/llk starter script.
+
+If you create full and completely valid keymap for your particular language,
+please attach it to a new issue.
+
+
+Further information
+-------------------
+
+Read the man page. Please read the whole man page. Thanks. :-)
+
+Refer to troubleshooting and FAQ sections in (the
+docs)[./docs/Documentation.md], for currently known issues, ways to
+resolve them, and any other information.
+
+Report any bugs and request reasonable features on the [issues
+list](https://github.com/kernc/logkeys/issues). When opening new
+issues, always provide a good summary and description.
+
+Contribute
+----------
+
+You are more than welcome to implement unreasonable features yourself, as well
+as hack the program to your liking.
+
+If you have suggestions, or are a pr0 and can answer any of the questions in the source, please contribute:
+
+1. Fork this project
+1. Create your feature branch (`git checkout -b my-new-feature`)
+1. Commit your changes (`git commit -am 'Add some feature'`)
+1. Push to the branch (`git push origin my-new-feature`)
+1. Create new Pull Request
+
+
+License
+-------
+
+logkeys is dual licensed under the terms of either GNU GPLv3 or later, or
+WTFPLv2 or later. It is entirely your choice! See COPYING for further
+information about licensing.
diff --git a/TODO b/TODO
index 241d1cb..1b8e73a 100644
--- a/TODO
+++ b/TODO
@@ -1,3 +1,6 @@
+-> Add automated testing scripts to verify behaviour and operation
+
+-> Clean up imported docs in "./docs", remove redundant docs
-> Add support for sending logs via mail
diff --git a/build/.gitignore b/build/.gitignore
new file mode 100644
index 0000000..1a5433b
--- /dev/null
+++ b/build/.gitignore
@@ -0,0 +1,7 @@
+# Ignore everything in this directory,
+# but this directory should be available on checkout.
+
+*
+
+# Don't ignore this file
+!.gitignore
\ No newline at end of file
diff --git a/docs/Documentation.md b/docs/Documentation.md
new file mode 100644
index 0000000..797f20d
--- /dev/null
+++ b/docs/Documentation.md
@@ -0,0 +1,173 @@
+![warning](./docs_warning.png)
+
+# License #
+logkeys is dual licensed under the terms of either [GNU GPLv3](http://www.gnu.org/licenses/gpl-3.0.html) or later (required by Google), or [WTFPLv2](http://sam.zoy.org/wtfpl/) or later. Pick whichever you prefer!
+
+# Installation #
+
+If you have ever installed a Linux program from source, then you should have no trouble installing logkeys.
+
+If you haven't installed from source yet, it is likely you are missing a C++ compiler installed.
+Before proceeding please ensure you have **g++** and "similarly trivial tools" ready.
+```
+$ sudo apt-get install g++ # to install g++ on a Debian-based OS
+```
+Proceed with
+```
+$ tar xvzf logkeys-0.1.1a.tar.gz # to extract the logkeys archive
+
+$ cd logkeys-0.1.1a/build # move to build directory to build there
+$ ../configure # invoke configure from parent directory
+$ make # make compiles what it needs to compile
+( become superuser now ) # you need root to install in system dir
+$ make install # installs binaries, manuals and scripts
+```
+If you run on any errors during configure stage, your machine must be in a very poor shape. Before installing please confirm that you have a 2.6 branch of Linux kernel, and standard command line utilities such as **ps**, **grep**, and especially **dumpkeys**.
+
+logkeys relies on **dumpkeys** to output at least half correct keysym bindings. For this to be true, you have to set your console keymap. If you have keyboard correctly set to your language in X, **verify that the same characters appear on a virtual terminal** (Ctrl+Alt+Fn) **also**.
+
+[How to set console keymap?](http://www.google.com/search?q=how+to+set+console+keymap)
+
+logkeys also relies on en\_US.UTF-8 locale being present on the system, or any other language using UTF-8. You can confirm you are using UTF-8 locale, if you say
+```bash
+
+$ locale -a
+C
+...
+en_US.utf8
+...
+$ locale
+LANG=en_US.UTF-8
+LC_CTYPE="en_US.UTF-8"
+...
+```
+If `locale -a` does not return among others the result en\_US.UTF-8 and if LC\_CTYPE environmental variable doesn't contain UTF-8, then logkeys may not work correctly.
+
+If that is the case use either `locale-gen` or install/reconfigure your distribution's locales package, and there include en\_US.UTF-8.
+```
+$ apropos locale
+```
+
+# Usage how-to #
+
+logkeys is simple. You can either invoke it directly, by typing full command line, or use the provided scripts. There are two helper programs in this package:
+
+ * bin/llk , which is intended to start the logkeys daemon, and
+ * bin/llkk , which is intended to kill it.
+
+bin/llk runs **_etc/logkeys-start.sh_**, and bin/llkk runs **_etc/logkeys-kill.sh_**.
+
+You can use these two **setuid root** programs (**llk** and **llkk**) for starting and stopping the keylogger quickly and covertly. You can modify the two .sh scripts as you like. As the programs are installed with setuid bit set, the root password need not be provided at their runtime.
+
+Default log file is /var/log/logkeys.log and is not readable by others.
+
+I suggest you first test the program manually with
+```
+ $ touch test.log
+ $ logkeys --start --output test.log
+```
+and in the other terminal follow it with
+```
+ $ tail --follow test.log
+```
+and see if the pressed keys match to those noted. If you use a US keyboard layout, use -u switch. Make sure your terminal character locale is set to UTF-8
+```
+ $ locale
+ LANG=xx_YY.UTF-8
+ LC_CTYPE="xx_YY.UTF-8"
+ ...
+```
+or alternatively, you need en\_US.UTF-8 locale available on your system
+```
+ $ locale -a
+ ...
+ en_US.UTF-8
+ ...
+```
+otherwise you may only see odd characters (like ꑶ etc.) when pressing character keys.
+
+logkeys acts as a daemon, and you stop the running logger process with
+```
+ $ logkeys --kill
+```
+(or bin/llkk provided script).
+
+Before using logkeys, please read the manual page first.
+```
+ $ man logkeys
+```
+
+## Autorun at system start ##
+If you want logkeys to autorun when your OS boots, you have several options.
+You can edit _/etc/rc.local_ (or _/etc/rc.d/rc.local_) file and add logkeys execution line before the final `exit 0` call, e.g.
+```
+#!/bin/sh -e
+#
+# rc.local
+#
+logkeys --start --keymap=/home/I/custom_key.map --output=/home/I/custom.log --device=event4
+exit 0
+```
+Alternatively, you can put your custom "logkeys execution line" into _etc/logkeys-start.sh_ file, and then use your desktop's "autorun manager" to run _llk_ program, which will then execute said _logkeys-start.sh_ script without prompting you for root/sudo password.
+
+logkeys will automatically terminate on shutdown.
+
+# Troubleshooting #
+
+## Empty log file or 'Couldn't determine keyboard device' error ##
+After you run logkeys successfully, if you open the log file and see only the 'Logging started...' and 'Logging stopped...' tag without any keypress "contents," it is very likely that logkeys got your device id wrong.
+
+This may also apply if you get the following error:
+```
+ logkeys: Couldn't determine keyboard device. :/
+```
+
+The solution is to determine the correct event device id, and then run logkeys with --device (-d) switch, specifying that device manually.
+
+The procedure for manually learning the device id to use is as follows:
+
+As root, for each existing device eventX in /dev/input/, where X is a number between 0 and 31 inclusively, write `$ cat /dev/input/eventX`, and then type some arbitrary characters. If you see any output, that is the device to be used. If you don't see any output, press Ctrl+C and continue with the next device.
+
+If this happened to be your issue, please checkout the latest version from the repository where keyboard recognition is relatively better implemented. If error persists, please [add an issue](https://github.com/kernc/logkeys/issues), attaching your /proc/bus/input/devices file as well as specifying the correct event id.
+
+
+## Logkeys outputs wrong characters ##
+
+It is very likely that you will see only some characters recognized, without any hope for Shift and AltGr working even slightly correct, especially when starting logkeys in X. In that case it is better to switch to virtual terminal, e.g. tty4 (Ctrl+Alt+F4), and there execute:
+
+```
+ $ logkeys --export-keymap=my_lang.map
+```
+
+Then open _my\_lang.map_ in UTF-8 enabled text editor and manually repair any missing or incorrectly determined mappings. Character keys are defined with two to three space-delimited characters per line (first without modifiers, second with shift, third with AltGr), and function keys are strings of **at most** 7 characters.
+
+Make sure your customized keymap follows the [logkeys keymap format specification](Keymaps.md#format).
+
+From then on, execute logkeys with **--keymap** switch, e.g.
+
+```
+ $ logkeys --start --keymap my_lang.map
+```
+
+Again, see if it now works correctly (and character keys appear correct when you are viewing the log file in editor), and opt to modify _bin/llk_ starter script.
+
+If you create full and completely valid keymap for your particular
+language, please [upload it as a new
+issue](https://github.com/kernc/logkeys/issues).
+
+Some languages may already have keymaps available; check the [keymaps directory](../keymaps/).
+
+# Known bugs and limitations #
+
+Please report all found bugs on the [issues tracking page](https://github.com/kernc/logkeys/issues).
+
+# Planned features (roadmap) #
+
+TODO file provided with release currently holds following requests:
+
+* Add support for sending logs via email.
+* Optionally log title of the focused window.
+* Capture clipboard contents.
+* Add support for mouse events (i.e. on mouse click the focus may have changed).
+
+If you have time on your hands and the required interest, you are welcome to hack at any of those or completely other features yourself, and submit a PR.
diff --git a/docs/Keymaps.md b/docs/Keymaps.md
new file mode 100644
index 0000000..f1b9865
--- /dev/null
+++ b/docs/Keymaps.md
@@ -0,0 +1,155 @@
+![warning](./docs_warning.png)
+
+# Keymaps
+
+If neither **--us-keymap** switch nor **--keymap** switch are used, then logkeys determines the keymap automatically with the help of **dumpkeys** command. For it to work even slightly reliably (mapping correct character), [console kernel keymap needs to be set](Documentation#Installation.md).
+
+If you are using US layout keyboard and need default US keymap, run logkeys with **--us-keymap** switch.
+
+## Existing keymaps
+
+Some keymaps have been committed in this repo. See the [keymaps directory](../keymaps).
+
+Be aware that using the keymap that matches your keyboard layout doesn't necessarily mean that all keys are covered or that the characters match to those that you type in – the keymap used by your system (loaded by **loadkeys** command for console, and **setxkbmap** command for X) may be set completely arbitrarily. In most cases, though, these should work fine.
+
+## Creating keymaps
+
+You can easily create keymaps for your layout by taking one example and then modifying it with the help of a keyboard layout tool (e.g., see the following [example layout tool from Microsoft](http://msdn.microsoft.com/en-us/goglobal/bb964651.aspx)). If you create a keymap, please upload it as a [new issue](https://github.com/kernc/logkeys/issues).
+
+## Format
+
+The keymap file is expected to be UTF-8 encoded.
+
+Each line of file represents either one character key or one function
+key. The format specifies at least two and up to three
+space-delimited characters on character key lines (first character
+without modifiers, second with Shift in action, optional third with
+AltGr in action), and up to 7 characters long string on function key
+lines.
+
+For example, Slovene or Croatian keymap would look like this (line
+numbers are added for convenience only):
+
+```
+ 1:
+ 2: 1 ! ~
+ 3: 2 " ˇ
+ 4: 3 # ^
+ 5: 4 $ ˘
+ 6: 5 % °
+ 7: 6 & ˛
+ 8: 7 / `
+ 9: 8 ( ˙
+ 10: 9 ) ´
+ 11: 0 = ˝
+ 12: ' ? ¨
+ 13: + * ¸
+ 14:
+ 15:
+ 16: q Q \
+ 17: w W |
+ 18: e E €
+ 19: r R
+ 20: t T
+ 21: z Z
+ 22: u U
+ 23: i I
+ 24: o O
+ 25: p P
+ 26: š Š ÷
+ 27: đ Đ ×
+ 28:
+ 29:
+ 30: a A
+ 31: s S
+ 32: d D
+ 33: f F [
+ 34: g G ]
+ 35: h H
+ 36: j J
+ 37: k K ł
+ 38: l L Ł
+ 39: č Č
+ 40: ć Ć ß
+ 41: ¸ ¨
+ 42:
+ 43: ž Ž ¤
+ 44: y Y
+ 45: x X
+ 46: c C
+ 47: v V @
+ 48: b B {
+ 49: n N }
+ 50: m M §
+ 51: , ; <
+ 52: . : >
+ 53: - _
+ 54:
+ 55:
+ 56:
+ 57:
+ 58:
+ 59:
+ 60:
+ 61:
+ 62:
+ 63:
+ 64:
+ 65:
+ 66:
+ 67:
+ 68:
+ 69:
+ 70:
+ 71:
+ 72:
+ 73:
+ 74:
+ 75:
+ 76:
+ 77:
+ 78:
+ 79:
+ 80:
+ 81:
+ 82:
+ 83:
+ 84: < >
+ 85:
+ 86:
+ 87:
+ 88:
+ 89:
+ 90:
+ 91:
+ 92:
+ 93:
+ 94:
+ 95:
+ 96:
+ 97:
+ 98:
+ 99:
+100:
+101:
+102:
+103:
+104:
+105:
+106: