ANSI-BBS2 Reference List

References

This is a list of the source documentation for existing specifications and implementations.

Please feel free to comment on this item.

BANSI (BananaCom)

This is the documentation for BananaCom. They defined a wide number of incompatible extensions which shuoldn't be used. They did do a nice description of VT-102 and BBS imple,entations though.

Banana ANSI Documentation

Please feel free to comment on this item.

CTerm libary (used by SyncTERM)

This is the documentation for the library used by SyncTERM. It should be complatibe with this standard, so should be considered a reference for implementations, not a source document for this standard.

Current CTerm Document

Please feel free to comment on this item.

The ECMA-48 Standard

This standard is the successor to the original ANSI specification and defines the basics of the entire system. We should try to never violate this specification in any way, and any new functionality should be looked for in this existing spec first.

ECMA-48 Document (PDF)

Please feel free to comment on this item.

The Linux Console

The Linux console has a few custom sequences, but most importantly, any new sequences should be verified to be compatible with the Linux console. The majority of initial connections from Linux systems are from either a Linux console or from XTerm.

Current Linux Console Document Current Linux Console Implementation

Please feel free to comment on this item.

VT-102

The VT-102 is the most commonly emulated ANSI compatible terminal. If it can be done using VT-102 codes and can't be done via ECMA-48 codes, the VT-102 method should always be used.

VT-102 Documentation

Please feel free to comment on this item.

VT-220

The VT-220 is a more capable ANSI compatible terminal and is what XTerm emulates. If it can be done using VT-220 codes and can't be done via ECMA-48 codes or VT-102 codes, the VT-220 method should always be used.

VT-220 Documentation

Please feel free to comment on this item.

XTerm

XTerm has a great number of custom sequences and should be searched for available extensions before defining a new one. It is vital that any new sequences be verified to be compatible with XTerm. The majority of initial connections from Linux systems are from either a Linux console or from XTerm.

Current XTerm Document

Please feel free to comment on this item.