I worked a little on kiterm and produced a version that works alongside launchpad, instead of replacing it. This file can be installed by using launchpad installation (copy to /mnt/us/customupdates and press shift shift I), or directly by unzipping under /mnt/us.

Fonts use "hex" format. A perl script is included that converts bdf fonts to hex. Since the fonts do not include width/height information, this must be provided in the configuration file (/mnt/us/myts/myts.ini). Fonts of width at most 8 may be used.

An encoding file is simply a 512 bytes binary file where the nth 16 bit word is the unicode value of char n. A script to generate such files is included.

To enable the scroll back buffer, use the configuration file option ScrollbackLines to set the number of lines saved in the buffer. A value of 0 (default) disables scroll back. I the default configuration file, the right page scrolling keys are used for scrollback, but this is configurable.

Very nice, Matan. It's almost perfect.
I miss one feature though.
I always keep forgetting the keyboard mapping and it would be great to be able to quickly toggle displaying current mapping with a key stroke.

Good idea, it doesn't have to be /usr/bin/, I'd rather use /mnt/us/ as I have it in my PATH anyway.
When I think about it, it doesn't have to be a script, an alias seems to be more suitable.
It's still more a workaround then a solution. Often you need to display the mapping after typing long command. Maybe I could dedicate one terminal instance for displaying help.

Thanks Matan. I am convinced and I have now switched to original launchpad + your version 5 of myts.

Echoing Dsmid, I miss one feature too. I also always keep forgetting the keyboard mapping and since you have plenty of room to expand, I would like the Menu+Left< recently added help screen, to display in some way, more information.

Applying some corrections:
The F10, F11 and F12 are still displayed as FA, FB, FC on the help screen
The right tab, left tab --- back+z, shift+back+z are not obvious and currently show as an invalid character (white on black question mark) maybe would it be more explicit if depicted as => and <=.