+Known Issues / Arbitrary Decisions
+----------------------------------
+
+Some arbitrary design decisions had to be made when either the
+obviously expected behavior did not happen or when a specification was
+ambiguous. This section describes such issues.
+
+ TTerminalWindow
+ ---------------
+
+ - TTerminalWindow will hang on input from the remote if the
+ TApplication is exited before the TTerminalWindow's process has
+ closed on its own. This is due to a Java limitation/interaction
+ between blocking reads (which is necessary to get UTF8 translation
+ correct) and file streams.
+
+ - See jexer.tterminal.ECMA48 for more specifics of terminal
+ emulation limitations.
+
+ - TTerminalWindow uses cmd.exe on Windows. Output will not be seen
+ until enter is pressed, due to cmd.exe's use of line-oriented
+ input (see the ENABLE_LINE_INPUT flag for GetConsoleMode() and
+ SetConsoleMode()).
+
+ ECMA48 Backend
+ --------------
+
+ - Mouse support for BackendType.ECMA48/XTERM currently requires UTF-8
+ coordinates (1005 mode). Terminals that support UTF-8 mouse coordinates
+ include xterm, rxvt-unicode, gnome-terminal, and konsole. Due to Java's
+ InputStreamReader requirement of a valid UTF-8 stream, one must assume
+ the terminal will always generate correct UTF-8 bytes. Mode 1006 (SGR)
+ will be supported in a future release.
+
+
+