be expanded if people like it... this can be used to store and replay data,
making sprites a lot easier to implement client-side.

Allow setting a '0' for left/right margins to leave them unchanged.

Don't support CSI ! p anymore since RIS (ESC c) works correctly now.

bottom margin, you can now create a completely separate sub-window.

This command replaces CSI s to save the cursor position... since this
non-standard extension is very widely used, set left/right margin only
works when mode 69 is enabled using CSI ? 69 h.  The margins are retained
when CSI ? 69 l is sent, only the command to adjust them is disabled.

Fix "CSI ["

CSI Pn Y - Cursor Line Tabulation
CSI Pn SP c - Tab Stop Remove
CSI Pn k - Line Position Backward

CSI Pn b (Repeat previous char)
	Actually mildly useful... repeat any character.
CSI Ps d (Line position absolute)
	Moves to a specific row without changing column.
	Mildly useful.
CSI Pn a (Cursor forward)
	Identical to CSI Pn C
CSI Pn ` (Absolute position in line)
	Identical to CSI Pn G
ESC H (Add Tab Stop)
	ie: Break everything else that uses tabs this session.
CSI Pn g (Clear Tabs)
	ie: Break everything else that uses tabs this session.
CSI 2 $ w (Request Tab Report)
	So, maybe it can be fixed after you break it!  Yay!
ESC M (Reverse Line Feed)
	Basically up one line.  Not really useful since we have cursor up.
CSI Ps e (Line position relative)
	Identical to CSI Pn B

don't move the cursor position.

The biggest impact is in the cterm =1n query, which is retaining 0 for
success and now uses 1 for all failures.

It supports:
CSI 38 : 2 : Z : R : G : B m
CSI 38 : 2 : R : G : B m
CSI 38 ; 2 : Z : R : G : B m
CSI 38 ; 2 : R : G : B m
CSI 38 ; 2 ; R ; G ; B m

Where Z is an ignored colorspace identifier.  For compatability, I'll likely
add support for the colon-separated variants "soon", but for now just support
the semi-colon one.

1) XTerm using semicolons.  CSI 38/48 ; 2 ; 0 ; R ; G ; B m
2) PabloDraw/TundraDraw. CSI 0/1 ; R ; G ; B m

These use a temporary internal palette of 15840 entries to ensure what's
on the screen is correct.  Scrollback data may be incorrect however.

(that support DCS strings).  With this, CSI = Ps1 ; Ps2 { is deprecated and
should not be used when CTerm is newer than this commit (1.213).

Docuement CSI < c
Use the ECMS-48 style notation.

1) The colour values are expressed as a percentage, not a 0-255 value.
2) Implement CSI ? 80 h/l to set/reset the sixel scrolling mode (defaults to
   set).
3) Document sixel commands.
4) Combine the extended set/reset mode commands in the documentation now
   that multiple modes can be set or reset with a single sequence.

CTerm (and therefore SyncTERM 1.0) required an extra two ignored garbage
bytes in the font data.

ESC ] 104 ESC \ will reset all palette entries.
ESC ] 104;X;Y... ESC \ will reset specified palette entries only.

ie: perl -e 'print "\e]104;1;2\e\\"'
Will reset palette entries 1 and 2.

ESC ] <string> ESC \

Where string is in the format:
rgb:R/G/B
And the values of R, G, and B are one to four hex digits.  For example:
"\e]4;1;rgb:0/0/a8" will reset the blue entry to the default value.

These basically never worked as documented.  Now they should, but they can't
save/restore the doorway mode setting since it's not set/cleared using
CSI ? h/l.  If that's really needed (you need to know the doorway state
regardless, so it's more likely that a query doorway command is needed if
anything) it can be added as a separate command.

1) Use a functional default (1) for P1.
2) Respond with an empty P2 parameter if nothing is set.
3) Only respond if there is a single parameter.  If there is more than one,
   it's not a request.

While we're here, clean up the formatting of cterm.txt.
Tabs for indentation, spaces for alignment, don't wrap with 80-column
displays using 8-char tabs (default with more).  The ECMA-048 reference
will always wrap however.

the DA response, so I added 2 new requests: CSI=1n and CSI=2n which query
a state report from the terminal (for font state or video/emu mode), the same
information returned in the DA in the previous rev, but in a format more in
line with the corresponding CSI? N h/l requests (no bit checking required).

slot numbers that have been successfully set by the server.

- first available loadable-font slot number (e.g. 43)
- result of previous "select font" request (0 = success)
- current video mode flags (e.g. high-intensity background)
- current emulation mode flags (e.g. cursor visible, doorway mode)

These are to aid the server (BBS) in making better use of advanced features,
namely alternative/loadable fonts and high-intensity background colors (aka iCE
colors). Being able to detect when these features are supported and working as
intended is vital in providing a smooth/automated BBS experience which is
automatically enhanced, when possible (supported by the client) and does not
interfere with legacy (non-enhanced client) users.
Even better would be a command that tells the server:
if the server were to attempt a request 'X', it would likely work.
Instead, we have to try request 'X' and then query the device attributes to
find out if it actually worked, which is better than nothing (or asking the
poor user to tell the BBS whether it worked or not).

the high intensity attribute can.  Using CTerm, this is controlled via the
CSI [ ? 34 h/l commands.

Also add CSI [ ? 35 h which disables blinking (reversed by CSI [ ? 35 l)

all along.  Make 41 and 42 the standard versions of the font since anyone
who has set up BBS controlled font-switching shouldn't be punished because
I messed up.  :-(